HI Alireza,
Thanks for the response.
Let me brief you with the issue we are facing.
Current UAT version-10.0.22,Prod-10.0.20
We upgrade UAT with version 10.0.22(service update) on 24th Dec. Before applying service upgrade to UAT we had deployed a customized package to UAT(This package is not approved to move to Prod).After all testing in UAT post version upgrade we planned to upgrade Prod with the same version as UAT. When we tried to mark the service upgrade as "Release Candidate" there's a pop-up which says a package(which should not be moved to Prod) will also be applied to Prod along with service update.
We are not able to mark service upgrade package as "release candidate" cause it's taking the previous UAT package which was deployed before applying service upgrade to UAT.
How can we apply the service upgrade to Prod now as we are not able to mark the service upgrade package as "release candidate" because of the above scenario.
We have a scenario where we have a prod deployment in the upcoming weeks. Before deploying the package to Prod we first deploy the same package to UAT(currently in 10.0.22).After the testing is done in UAT we mark that package as "release candidate" and schedule that package to Prod.
As UAT is in 10.0.22 so the package that we schedule to Prod will also be of the same version as UAT right? Then if we schedule this package to Prod, will Prod get upgraded to 10.0.22 after the package gets deployed?
Regards,
Pavan