Skip to main content

 –

Working on a change request

Suggest edit Updated on March 16, 2021

In the Build phase, a user in the NBASpecialist access group makes the changes required to complete the change request.

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.
  1. To view all your pending change requests, log in as a user in the <your implementation application>:NBASpecialist access group.

  2. In the To do section of the Pega 1:1 Operations Manager Home page, click Go by the request that you want to review.

  3. Review the request details and the required Build tasks.

  4. In the Design treatment task, configure the requested treatment.

    Note: By default, the system generates treatment names according to the following schema: ActionName + treatment name + number of treatments. You can modify the name as required, as long as the name that you specify for the treatment is unique.
  5. In the Configure engagement policy task, configure the eligibility, applicability, and suitability criteria, as well as the contact policy details.

  6. After specifying eligibility details, on the Prepare validation tab, select the persona to perform unit testing for the eligibility criteria.

    You can select from existing personas based on how well they match the criteria you configure, or define a new persona for the test.
  7. On the Run validation tab, for each selected persona, specify the desired outcome of the action in the Desired outcome column, as in the following figure:

  8. Click the Run icon above the list of personas.

    Result: The validation runs. If the desired outcome for a persona matches the actual outcome, the validation for that persona is successful. Otherwise, the validation is marked as Failed. For each persona, you can view the validation details. Failed validation criteria are marked in red.
  9. On the Peer review tab, enter notes for the peer reviewer, and then complete the task.

Result: The system sends the request to the peer reviewer. The peer reviewer can approve or reject the changes. If the request passes peer review, it is sent back to the team lead to approve the changes for deployment. For more information, see Verifying and deploying a change request.
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