Skip to main content

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

Simplify access with an Application URL alias (8.4)

Updated on August 5, 2021

The URL of your Pega application is the starting point for your users. Pega Platform now supports a configurable application URL alias that provides a URL that allows the use of multiple applications simultaneously in the same browser.

Pega applications built prior to Pega Platform 8.4 have a text application identifier appended to the URL for compatibility reasons. These applications can continue to use the application identifier in the URL, or you can configure an application URL alias. If you configure an application URL alias, the old application identifier still launches the application.

Automated tests that follow URL redirects do not require updates. Some automated tests may notice the URL redirect and report a performance impact. Non-auto generated UI rules that manipulate URLs do require updates.

"The application definition with the Change URL alias window open"
Add a URL alias in the application definition.


To add a URL alias, open the application definition and click the Change URL alias button. The text added in the Change URL alias text box is appended to the end of the application URL. Share this URL with your application users, and they can bookmark the new URL.

For more information, see Application URL patterns for various authentication service types.

Upgrade considerations

Non-autogenerated UI rules that manipulate URLs will require updates. These non-auto-generated UI rules need to be updated according to the new URL format with application URL alias. In addition to the URL, the system properties (pxRequestor.pxReqServletNameReal) that describes the components of the URL are also updated. Applications using these properties must be updated.

For more information, refer to the section, Guidelines for any required changes in your application URL aliasing, in the latest on-premises Pega Platform Upgrade Guide at Stay current with Pega

After upgrading, you also need to update your JMeter test scripts. For more information, see Updating JMeter test scripts after migrating to Pega 8.4.

  • Previous topic Expanded options for signing and encrypting JSON Web Tokens (8.4)
  • Next topic Configure token credentials authentication services (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