Hi
I am hoping someone can answer my Version Control queries. The LCM document is limited in its detail on VM.
I am currently testing the BO LCM 3.1 and while it appears very easy to use especially for promotion, the Version Control Manager seems to be lacking in controls and a clear promotion path from dev to test to uat to prod.
We have set up 2 identical environments for UAT and PROD.
And using the Version Control part of LCM creating version control for a universe.
Logged into VM in UAT
We have selected a universe
Added it to VM
Made a change to the universe in Designer
Exported it
Then Checked it in
Can now see 2 versions in the history and the VMS Version. All good
I then click on swap system and log into PROD
The VM history is also there in PROD
I have a number of concerns and questions and can't seem to find the solution to them anywhere.
1. VM seems to be lacking a controlled process from all the environments. Basically we want to deploy following this path;
Dev - Test - UAT - PROD
There does not seem to be any controls or security which would stop you from GET VERSION from the DEV environment and putting that straight into PROD. Obviously we would not want that to happen.
We would only want to GET VERSION from UAT
Similarly for UAT We would only want to GET VERSION from TEST
And for TEST We would only want to GET VERSION from DEV.
Granted, we currently only have 2 identical environments.
But Is there controls that would stop you when in PROD from getting versions from any other system other than UAT?
Also is there any reason why no promotion is required when using VM.
This seems to negate the Promotion Function of the LCM
Any advise would be greatly appreciated with this.
Many thanks
Eilish
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.