LinkedIn
Copied!

Table of Contents

Launching a revision change request

Version:

Only available versions of this content are shown in the dropdown

As a revision manager, launch a change request by first creating a new revision, and then adding an associated change request within that revision.

For operations change requests launched by business users through Pega 1:1 Operations Manager, the corresponding revision is created automatically. As a revision manager, you do not need to manually create it.
  1. Log in to the Pega Customer Decision Hub portal as an operator with the RevisionManager access role.

  2. In the left navigation panel, click Revision Management.

  3. On the Revision Management landing page, click New revision.

  4. On the Set up new revision screen, select Create new revision option is selected.

  5. Enter the name of the revision, for example, Set the Apple iPhone price to 200.

  6. Define the revision objective, for example, Modify product pricing info.

  7. Define the priority of the revision by modifying the Urgency setting.

    The lower the urgency value, the more priority is assigned to the revision.
  8. Assign the deadline for completing the revision by configuring the Due by setting.

  9. Click Continue.

  10. Select the rules that you want to include in the revision, or specify the type of rule that you want to create.

  11. In the Change request section, click Edit.

  12. In the Edit Change Request Details window, in the Assign to section, select Operator.

  13. From the drop-down menu, select the operator that you want to assign to the change request.

  14. Provide the name of the change request, for example, Update the Apple iPhone price to 200.

  15. Optional:

    To associate this change request with an objective that is different than the revision objective, modify the Associate an objective field.

  16. Optional:

    In the Description field, provide additional details, for example, Modify the Price property.

  17. Optional:

    Define the change request priority in the Urgency field.

  18. Optional:

    Define the completion deadline for this change request in the Due by field.

    The default value is seven days.
  19. Click Submit.

  20. In the Refine selection section, include the propositions whose configuration you want to update.

  21. Click Submit.

The change request advances to the Open stage. A strategy designer who has the necessary access rights to work on the tasks required to complete the request may now start working to build the necessary changes. For more information, see Completing change requests.
  • Completing change requests

    As a strategy designer, complete the change request by performing the required changes and submitting your work for approval.

  • Resolving revisions

    As a revision manager, assess whether the rule updates are satisfactory. If you approve of the changes, you can submit the revision for deployment. Before you can submit a revision, you must approve all change requests that comprise that revision.

  • Launching fast-track change requests

    Address high-priority business needs efficiently through fast-track change requests. This type of change request provides a mechanism to quickly deploy urgent changes, without disrupting revisions that are in progress.

  • Deploying revisions with Deployment Manager

    As a best practice, you should use Deployment Manager 4.8 or newer to automate your business change management process, run CI/CD pipelines to merge a revision package to the development system of record (SOR), and subsequently deploy that package through to your production environment by using a deployment pipeline.

  • Optional: Managing revisions manually

    If you do not use Deployment Manager 4.8 to automate your business change management process, you can manually import, activate, discard, or roll back revisions in the production environment.

  • Supported rule types for revision management

    The revision management functionality provides business users with means to request, make, audit, and test changes to enterprise applications. The following table presents the rules that are available in revision management.

  • Stages of the Revision case type

    The primary purpose of the Revision case type is to initiate the process of changing business rules in your application. This case type covers all aspects of the revision life cycle. A revision can have one or more change requests associated with it. You can modify the stages, steps, processes, or assignments that are part of the Revision case type to make it simpler or more complex, depending on the business needs.

  • Stages of the Change Request case type

    By default, the Change Request case type is the subcase that is created in the first stage of the Revision case type life cycle.

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.