Skip to main content

 –

Managing update fixes with Deployment Manager

Suggest edit Updated on September 29, 2021

You can create pipelines in Deployment Manager version 4.8.2 or later to promote the latest application functionality to your production environment. By using Deployment Manager as a standard DevOps approach during updates, you can assess the effect of the latest Pega Platform capabilities and plan your new feature adoption strategy across your environments after you update to the latest version of Pega Infinity.

For more information about Deployment Manager, see Using Deployment Manager for model-driven DevOps.

  • Configuring your application and test packages

    When you configure an update pipeline, you provide an application product rule and a confidence test product rule in your update pipeline.

  • Configuring update pipelines in Deployment Manager

    Create an update pipeline for each application to promote the update fixes from the temporary production environment to production.

  • Syncing rules between the production environment and the updated, cloned, staging environment in Deployment Manager

    For each application, promote an application product rule, which includes a sample of the production data and rule configurations used to complete thorough regression testing of the application on the updated cloned, staging environment. Use ad hoc tasks in Deployment Manager promote the rules. Ad hoc tasks are available in Deployment Manager 4.8.2 and later.

  • Migrating update fixes to production

    When you are ready to migrate your update fixes, deploy your changes first to the ephemeral stage and then to production. Promoting your application and updating to production ensures that your application is updated with the latest features and capabilities after an update. On Pega Cloud Services, you perform these steps after entering your 60-minute validation window.

  • Understanding confidence testing

    Before a production system update, you perform confidence testing on the temporary production environment to validate that the production environment is ready for a Pega Infinity update. For Pega Cloud Services updates, confidence testing occurs within a 60-minute window. Before performing confidence testing, you should create a test plan to run smoke tests to ensure that the run-time behavior is correct. You should also perform a preliminary run of the test plan on the temporary production environment.

  • Migrating application update changes to non-production environments

    After completing the update on non-production environments, migrate the application update changes to your non-production environments. By migrating your update fixes to your non-production environment, you ensure that your application is updated with the latest features and capabilities after an update.

Did you find this content helpful? YesNo

100% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us