Deployment of processes to production

Once the UAT phase has been accepted the process is ready to be deployed in the production environment. From this point, the process will work on 100% of the cases and can’t be amended without a formal Request for Change.

Deployment Checklist

A new or amended process that has followed the Delivery Methodology and which has a completed and authorised Deployment Request Form, may be migrated into the production environment.

The following steps should be taken during deployment:

  • Ensure any live processes or business objects changed by the deployment are not running.
  • As part of the Delivery Methodology, all processes with matching interdependencies to the new/amended process will have been regression tested. 
  • All interdependent processes and business object actions should be evaluated once again in the UAT environment to ensure none have changed since UAT was signed off (i.e. as part of a change to a different process).  If any related process or action has changed they must be regression tested prior to deployment, if this has not already been done.
  • Any required environmental changes should have been implemented. For example, new email profile and screen resolution changes.
  • Any process configuration changes required for use in production should be made such as configuring network directories to use or turning off any ‘test mode’ flags
  • Any resource dependencies should be installed such as new web services or internet security certificates.
  • Export the new/amended process(es) and related amended sub-processes/business objects from the UAT environment.
  • Import into the live environment.  For larger deployments the easiest way to do this may be via command line rather than the Blue Prism Export/Import functionality.  For any new sub-processes that have not been in the Production Environment before the /forceid command line switch will need to be used to ensure that the sub-process is called correctly from the parent process.
  • Post-production installation tests should be done to ensure the migration to the production environment has been successful. This should involve the running and close monitoring of any processes that may have been affected by the deployment.
  • Deployment Request - Approved
  • Implementation Plan - Approved 
  • Release Note - Approved
  • Deployment Control Policy
  • BAU Support Policy
  • Operational Handbook
  • Operational Contingency Document - Updated
  • Operational Process Control Document - Updated
  • Environment Description Document - Updated
Online Help

Visit Blue Prism Help online to find more information on the latest product features, troubleshooting advice and 'how to' guides.