Skip to main content

Implementing Pega 1:1 Operations Manager

Suggest edit Updated on September 21, 2021

Pega 1:1 Operations Manager is a module of Pega Customer Decision Hub that non-technical teams use in the Business Operations Environment (BOE) to manage business change requests and quickly deploy them to production.

Pega 1:1 Operations Manager facilitates the business change process by empowering business users to request changes in a dedicated, user-friendly application. To learn more about requesting and deploying business changes through Pega 1:1 Operations Manager, see Business operations use cases.

Deployment architecture

To make business changes to a live system with Pega Customer Decision Hub, you need the Pega 1:1 Operations Manager application in the BOE environment, in which business users can access Pega 1:1 Operations Manager and request business changes.

Pega Customer Decision Hub and Pega 1:1 Operations Manager are first implemented in the Development environment. Then, both applications are packaged and migrated to the Staging, BOE, and Production environments.

For more information about the four environments and the data pipelines that are required for a system with Pega Customer Decision Hub, see Deployment architecture for Pega Customer Decision Hub.

Pega Customer Decision Hub deployment architecture
Diagram shows four environments: development, staging, Business Operations, and
            production.

Understanding the Pega 1:1 Operations Manager implementation process

At a high level, implementing Pega 1:1 Operations Manager consists of the following stages:

  1. Setting up Pega 1:1 Operations Manager in the Development environment:
    1. Creating the Pega 1:1 Operations Manager implementation application in its own implementation layer.
    2. Creating an overlay application for holding your artifact changes.
    3. Extending and customizing the Pega 1:1 Operations Manager implementation application to meet your requirements, for example, by extending the approval process.
  2. Migrating the Pega 1:1 Operations Manager application to the Staging, BOE, and Production environments.

To set up Pega 1:1 Operations Manager, perform the following procedures:

  1. Prerequisites for Pega 1:1 Operations Manager

    Before you start your Pega 1:1 Operations Manager implementation, complete the following tasks.

  2. Creating the Pega 1:1 Operations Manager implementation application

    In your development environment, run the New Application wizard to create your application.

  3. Creating the overlay application for Pega 1:1 Operations Manager

    Create an application overlay to hold the business-as-usual changes requested by business users through the Pega 1:1 Operations Manager.

  4. Creating users in Pega 1:1 Operations Manager

    Review the list of available user roles and access groups, and create operator accounts for your users.

  5. Configuring a team in Pega 1:1 Operations Manager

    After you create the operator accounts, an operator in the TeamLead access group must log in to the Pega 1:1 Operations Manager portal and create the teams, or work groups, for the users.

  6. Updating the PegaMKT-Work-Ops email account

    Edit the PegaMKT-Work-Ops email account, which Pega 1:1 Operations Manager uses to send out notifications.

  7. Verifying Pega 1:1 Operations Manager implementation

    To verify that your Pega 1:1 Operations Manager is correctly implemented, validate the application stack, confirm that you can access the Pega 1:1 Operations Manager portal, and test the change request creation.

  8. Building features

    The implementation team enables or extends features to meet your business requirements.

Did you find this content helpful? YesNo

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