Skip to main content

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

Launching fast-track change requests

Updated on May 17, 2024

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.

Before you begin: As a system architect, enable fast-track change requests in your application by assigning business users with the following access groups:
Initiates and resolves fast-track change requests.
Amends or creates business rules as part of a fast-track change request, in the context of a production application and in isolation from standard revision management process.

For more information, see Creating application overlays.

To complete a fast-track change request, strategy designers can address high priority changes within the context of the enterprise application, isolated from the regular revision process. Upon approval, such change requests are immediately ready for deployment as part of a new, automatically created revision.

As a revision manager, you can create a fast-track change request in the following ways:

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

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