Problem description: The Pega Platform currently only supports one single URL for each of the Constellation services, which are set through Dynamic System Settings (DSS). This poses a problem for client environments, where Pega is being accessed through two or more different URLs in different network domains (e.g. pega.corpdomain1.com and pega.corpdomain2.com), which are strictly separated.

While the Pega Platform itself does support access through multiple different URLs, the configuration of the Constellation services introduced a regression here.

Proposed solution: Establish a solution, where the Constellation URLs can be configured based on certain criteria, e.g. through a decision table. Those criteria could involve the network domain of the user’s client computer, the geographic location of the user, etc.

This would have the following benefit:

1. Allow configuring different Constellation URLs for users coming from separate network domains.

2. Allow ‘local’ Constellation services to allow for better performance for geographically distributed users.

Benefit:

1. Higher flexibility in the configurability of the network access to the Pega Platform

2. Better performance for geographically distributed organizations