Hello Subham,
Hopefully the leadership in your organisation has a Trusted Advisor or Delivery Enablement Manager from Blue Prism or one of our partners to discuss release migration strategies with you.
The Blue Prism methodology and ROM has a number of things that should be part of your solution migration policies:
** An solution design that includes all parts of your solution that need to be migrated
** A logical access model that prevents developers from importing their solution into higher UAT or Production environments without the required security sign offs being in place
** If you are talking about dev to UAT, a Peer review checklist which should be completed by an accredited lead developer to ensure your solution adheres to your best practices
** You should be following design best practices so that your objects are very small rather than very large - massively decreasing the risk of moving a changed object into production.
** In the ROM area of the Portal there are 'Process Release Acceptance' and other documents around signing off and controling your release
** If we are talking about going from UAT to Production I would expect to see UAT sign off documents, where the business agrees the solution works as expected.
** Finally, release manager enables you to package up your releases so that they can be migrated into the higher environment. There is also a feature within the Product to look up references (see where an object is being used)
If any of this is new to you and your team then I would suggest the manager of your team sets up a meeting with an experienced Blue Prism Project Manager or ROM Architect to discss this in more detail.
