Version Management is not used in the same way as you use a VMS with development. If you think that, then you're using the tool the wrong way. Yes, you can version objects which allows you to revert back to a previous version of an object if the change that was made was the incorrect one, but because the objects are actually inserted into VMS via an LCMBIAR file, then there really isn't a way of doing the other things you can do with VMS.
You cannot use it for branching, tagging, and so on. However, using VMS is a great way of making sure that the promotion job that you are sending to your QA system contains the same objects (and the same version of the object) that you want to push to Production.
The proper workflow for Promotion Management jobs is to go from Dev, to QA and then from Dev to Production once you have accepted that the objects in that job are working correctly and do what you want them to do. If they don't, you'd have to go back to Dev to fix it, then promote to QA once again. Notice that I said you make the changes in Dev! Once you are happy, you just run the SAME promotion job which you have versioned, to your new target: production
Anyway, the fact that version management is NOT like you'd expect when doing development, it also means that you can't have multiple users check things in and check them out to work on them concurrently. What one person checks out, will affect everyone trying to use that object.
One thing that you can do is use the Visual Difference tool to view the promotion job you have checked in and compare with with another promotion job in an LCM BIAR file or an existing promotion job.
--
Patrick
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.