Skip to main content

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

Approving and ranking a change request

Updated on June 29, 2022

As a team leader, review and approve change requests to ensure that they are in line with the requirements of your organization.

Note: This procedure does not apply to the Change prediction request type, which is used to deploy changes to models that are used in predictions. For more information, see Understanding the change request flow.
Pega 1:1 Operations Manager Documentation Center
  1. Log in to Pega 1:1 Operations Manager 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 next to the request which you want to review.
  3. Review the request details in the panel on the left.
  4. In the Rank field, enter a positive numerical value.
    Use the rank value to prioritize actions. Rank 1 indicates the highest priority. To help you rank the request, you can compare it to other change requests currently open in the system.
  5. In the Stakeholders section in the panel on the right, select one or more peer reviewers (for example, other members of the NBA Specialists team) who will review the changes done for this change request, as in the following figure:
    Tip: The Stakeholders list automatically includes the operator who created the change request as the approver. You can also specify additional approvers, if required.
  6. Optional: To get the next task from your work list, click Get next.
Result: If the request is approved, it is moved to the Plan stage, and sent back to the user who created it.
  • Previous topic Creating a fast-track change request in Pega 1:1 Operations Manager
  • Next topic Create a new bundle in 1:1 Operations Manager

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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us