Skip to main content

Understanding business change pipelines

Suggest edit
Updated on December 13, 2021

Business change pipelines are used to support everyday, business-as-usual changes to your Customer Decision Hub (CDH) application. This pipeline type allows users to respond to changing requirements by modifying and deploying application rules in a controlled manner.

Business change pipelines offer CDH business users the means to deploy and test changes implemented to their applications outside the enterprise release cycles. This pipeline type enables a seamless experience from merging changes to the development system of record, versioning the application and generating a release artifact. Deployment Manager then deploys the artifacts to each environment. Within the production environment, you are able to select a subset of users to test the modifications in a production environment and roll out the changes to all users when the test results are acceptable.

Note: The business change pipeline feature in Deployment Manager 5.x is supported with customers on Pega Platform 8.5.1 or later. Customers are not recommended to update to Deployment Manager 4.8.4, as the suggested update path from Deployment Manager 4.8.3 is to 5.1.

The business change cycle enables business users to respond quickly to changes in the external and internal factors that influence their business. Responses might include introducing new actions or propositions, imposing eligibility criteria, or modifying existing business strategies.

Business change pipelines are an application pipeline type within Deployment Manager. To get started and create a business change pipeline, see Creating a business change pipeline.

If you are new to Deployment Manager, see Installing or upgrading Deployment Manager 5.x to get started.

Did you find this content helpful? YesNo

Have a question? Get answers now.

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

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