If we were to update our build place to 25R1, or any other future release version, and the impact analysis raises issues we would not have the bandwidth to resolve timely, would be able to revert our buildplace back to our current version?
This would allow us to identify and review the potential impacts of performing an upgrade and make an informed business decision on whether or not to move forward with an install, based on the current business state
+9Hi
As I understood correctly the question is if you’re in the middle of applying release update and you want to ignore current process but in the future again you wanted to start the relase update from the begining what ever the latest update at that time. YES, it’s not a problem. You can stop the current process since you’re not complete the release update and then in future you can start it again from the begining.
Thanks & Regards,
Asanka.
Hi
We are concerned that if we start an upgrade in our buildplace that we won’t be able to revert back and it would hang us up from deploying other configuration changes.
+9Hi
Release update process is a separate process from the buildplace. It’s handling through release update studio. If you have done the impact analysis that’s on release update studio that’s not impact for your curent build place. When you’re completing all the steps of release update process only your changes will apply to the buildplace.
Thanks & Regards,
Asanka.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
