Skip to main content

Pega 1:1 Operations Manager User Guide

Suggest edit
Updated on December 3, 2021

Pega 1:1 Operations Manager is a module of Pega Customer Decision Hub. Use Pega 1:1 Operations Manager in conjunction with Revision Management to push business changes into production.

Pega 1:1 Operations Manager Documentation Center

In Pega Customer Decision Hub 8.7, Pega 1:1 Operations Manager provides the options to view related change requests, withdraw the change requests from the current revision, defer the change requests from the revision, and add the deferred change request back to the active revision. For more information, see Pega 1:1 Operations Manager enhancements.

Pega 1:1 Operations Manager supports rules such as actions, treatments, and associated engagement policies, which are essential to manage business-as-usual changes. Decision tables, and other rules that tend to create product usage patterns that deviate from Pega's guidance for using our technology for 1:1 customer engagement, are deliberately left out of Pega 1:1 Operations Manager.

Pega 1:1 Operations Manager requires an overlay application. The application is not intended to be deployed to production. For more information, see Configuring Pega 1:1 Operations Manager in the Business Operations Environment.

Understanding the relationship between Pega 1:1 Operations Manager and Revision Management

Pega 1:1 Operations Manager extends the standard Revision Management capabilities of Pega Customer Decision Hub by providing a simple process where a business change request is triggered by non-technical team members. To create or update an action, users can create change requests in Pega 1:1 Operations Manager. To replace models in predictions, users can trigger Pega 1:1 Operations Manager change requests from Prediction Studio. In this way, Pega 1:1 Operations Manager makes it possible to quickly record and process standard, high-volume change requests related to actions and models.

Pega 1:1 Operations Manager uses the same flows and activities as standard Revision Management. Because of that, it seamlessly integrates with Revision Management and complements normal Revision Management operations. For example, if a change request is withdrawn or rejected in Pega 1:1 Operations Manager, the status also changes in Revision Manager. If a revision is withdrawn or rejected in Revision Manager, the status change is reflected in Pega 1:1 Operations Manager.

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