Skip to main content

Verifying and deploying a change request

Suggest edit
Updated on June 20, 2022

Once the changes are completed, as a team leader, review the list of changes and submit them to a revision manager, who can deploy them to production.

Pega 1:1 Operations Manager Documentation Center
  1. To view all your pending change requests, log in as a user with the <your overlay application>:TeamLead access group.
  2. In the To do section of the 1:1 Operations Manager Home page, click Go by the request which you want to review.
  3. Optional: If the Action or Treatment rule form, or the engagement policy criteria configured for the action, contain any properties that are enabled for compliance checks, the change request will contain a Compliance check for action task. Perform a compliance audit by reviewing the output of the audited fields, and click Approve or Reject.
  4. Review the list of rules which were created or edited for the change request.
  5. Approve or reject the changes, and click Submit.
    • To return the request to NBA Specialist, for example, because the request was not implemented correctly, click ActionsReturn to build or Return to test.
    • To return the request to the team member who submitted it, for example, because the request details were unclear, click ActionsReturn to plan.
    Note: Approve and reject options are not available for Change prediction requests, which are automatically resolved and associated with revisions.
Result: If approved, the revision with the change request can now be deployed to production according to the standard Revision Management process.
The change request is resolved. To view it, click Change requests in the left navigation pane of Pega 1:1 Operations Manager, and then click Closed.
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