Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Application overview

Updated on January 22, 2021

Pega 1:1 Operations Manager is a new module of Pega Customer Decision Hub. Non-technical teams use Pega 1:1 Operations Manager to manage business-as-usual change requests and quickly deploy them to production.

As a best practice, the change management process in an organization involves the following types of changes:

Enterprise changes
Enterprise changes involve changing the application itself, for example, by modifying the user interface. Enterprise changes are done by developers in a Development SOR environment, and then pushed to other environments in the pipeline.
Business changes
Business changes involve business-as-usual operations such as the creation of new actions, treatments, customer segments, and so on. This type of change is triggered by business users in a BOE environment, and then pushed to other environments by using the Business Change pipeline, as in the following figure:

Pega 1:1 Operations Manager helps streamline the business change process by empowering business users to request changes in a dedicated, streamlined user interface.

Tip: The Pega 1:1 Operations Manager implementation application must be generated in its own implementation layer in your Development environment. You must then create a Pega Customer Decision Hub application overlay for holding your artifact changes.

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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