Skip to main content


Implementing a change management requirement in the BOE

2 Topics

20 mins

Pega Customer Decision Hub 8.7
Visible to all users
Beginner Pega Customer Decision Hub 8.7 Pega Customer Decision Hub 8.6 English

Business requirements change rapidly and typically have a different release cycle compared to the enterprise release cycle.

To ensure a logical separation facilitates change management, changes that do not fall into the technical domain are done in the business operations environment (BOE) according to the business requirements. Two types of changes are typically done in the BOE. High-volume day-to-day business tasks, such as updating, creating, editing action, treatment details, and low-volume tasks changes like taxonomy, arbitration, and Next best action designer configurations.

From the 1:1 Operations Manager, the change requests currently supported create an action and update existing actions.

For any other change that needs to be done in the BOE environment, you can do them from the Revision Manager. Learn how to make changes from the BOE environment.

After completing this module, you should be able to:

Describe the change management process
Initiate a change management request in the BOE
Implement a change request as an NBA Designer
Approve and deploy the changes as a revision manager to all environments by using the business change pipeline

Practice what you learned in the following Challenge:

Adding a group-level engagement policy

Available in the following mission:

Business Agility in 1:1 Customer Engagement

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

Pega Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice