Skip to main content

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

Resolving fast-track change requests

Updated on May 3, 2021

Address high priority or emergency rule changes through fast-track change requests. This type of change request provides the mechanism for making urgent business rule changes in a separate context, without the need to disrupt a revision that is in progress.

Note: Initiate fast-track change requests with caution. For changes that do not require immediate deployment, create standard change requests instead.

Enabling fast-track changes

As a system architect, enable fast-track change requests in your application by assigning business users with the following access groups:

  • <overlay_name>:FastTrackRevisionManager
    This operator can create and approve fast-track change requests.
  • <overlay_name>:FastTrackStrategyDesigner 
    This operator can amend the rules directly in the context of an enterprise application and submit the changes for approval.

These access groups are available by default when you create an application overlay for revision management, as shown in the following example:

Access groups that enable fast-track change requests

For more information, see Creating application overlays.

Initiating business changes outside of the standard revision management process

As a revision manager, you can start fast-track change requests directly on the Revision Management landing page. In addition, you can convert an approved standard change request to a fast-track change request. 

Creating a fast-track change request

  1. In the Change Request Type section, select Fast track.
  2. Select the checkbox next to each rule that you want to include in the change request.
  3. Click Change <X> rules, where X is the number of rules that you included in the change request. For reference, see the following example:

    Initiating a fast-track change request

Converting standard change requests to fast-track change requests

You can increase the priority of business changes by converting standard change requests to fast-track change requests.

  1. On the Revision Management landing page, open a revision that is in progress.
  2. Open a standard change request that has been approved.
  3. In the top-right corner, click Change to fast track, as in the following example:

    Converting a standard change request to a fast-track change request

  4. Review the change request contents and click Submit.
If the changes in a fast-track change request conflict with any standard change request, the following error message is displayed:
Resolve potential conflicts by manually propagating the rule changes to the standard change request or by withdrawing the conflicting rules from the standard change request. Otherwise, the changes that you introduced in the standard change request overwrite any changes that you made in advance.

Completing a fast-track change request

As a strategy designer, you can work on a fast-track change request by switching the context to the fast-track application to ensure that your work is isolated from the other changes. By using this solution, you can safely release fast-track changes in advance of standard revision work.

Before you begin

Ensure that the list of your access groups includes the <overlay_name>:FastTrackStrategyDesigner access group.

  1. Log on to Pega Marketing™ or Customer Decision Hub™ portal.
  2. Switch the application context to the fast-track application by performing the following actions:
    1. Click on your operator icon.
    2. From the Switch apps menu, select the fast-track application.

      The fast-track application is always the enterprise application on top of which you built the revision management overlay. This application has all the previous revisions that were deployed and contains no revisions that are in progress. This separate context isolates urgent business rule changes from the standard revision management process.
  3. In the My Work section, access the change request and perform rule changes according to the change request description.
  4. Submit your changes for the revision manager's approval.

Resolving a fast-track change request

As a revision manager, you can review and approve fast-track change requests similarly to standard change requests. After you approve a fast-track change request, that request is automatically packaged in a new revision for download or direct deployment. In addition, a new revision ruleset version is created. 

Perform the following actions to resolve a fast-track change request:

  1. Switch the application context to the fast-track application.
  2. On the Revision Management page, in the My work section, open the fast-track change request that you want to approve.
  3. Review the changes, and then click Approve.


You resolved the change request. That change request is now packaged and ready to deploy as part of a separate revision, as shown in the following example:

A fast-track change request that has been resolved and approved


  • Previous topic Release urgent business rule updates through fast-track change requests (8.3)
  • Next topic Increase the accuracy of text analytics models with imported feedback data (8.3)

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