Issue
In Pega Platform™ with Constellation UI, refreshing the browser while viewing a Case returns an HTTP 400 (Bad Request) error. The error affects only specific Case Types — those whose Case Type Label (pyLabel) contains special characters such as parentheses.
Symptoms and Impact
- Refreshing the browser while a Constellation Case is open returns an HTTP 400 Bad Request error.
- The error occurs only for specific Case Types, not all Cases in the application.
- Regenerating the routing table does not resolve the error.
- The affected Case Type's technical class name does not contain special characters, but a browser network trace shows parentheses in the URL path segment for that Case Type.
Steps to Reproduce
Prerequisites: The application uses Constellation UI. At least one Case Type has a Label field (pyLabel) that contains or previously contained parentheses, for example, "Maintenance (DAP)".
- In Dev Studio, open the affected Case Type and note the value in the Label field on the Settings tab.
- Open the Constellation portal and create a new Case of the affected type.
- With the Case open, press F5 or refresh the browser.
- Result: The browser returns an HTTP 400 Bad Request error. The Case does not reload.
- Open the browser developer tools, select the Network tab, and examine the failed request URL.
- Result: The URL path contains parentheses derived from the Case Type label, for example, /maintenance-(dap)s/CASE-001.
Root Cause
Product feature gap related to handling special characters in Case labels used for semantic URL generation.
Constellation generates semantic URLs from the Case Type Label field (pyLabel), not from the Case Type class name. When a label contains parentheses, the routing engine creates a routing table entry that includes those characters in the URL path segment, for example, "Maintenance (DAP)".
When the server receives a request containing parentheses in the URL path, it rejects the request with HTTP 400 because parentheses are treated as invalid characters in that position by the platform's XSS URL-mapping protection.
The problem persists even after the label is corrected, and the routing table is regenerated because regeneration adds a new clean entry but does not remove the stale entry containing the parentheses. Both entries exist simultaneously in the routing table with identical payloads. On a browser refresh, client-side routing resolves to the first matching entry, which may be the stale one containing the invalid characters, producing the HTTP 400.
Solution
A permanent fix to ensure stale routing entries are automatically purged during routing table regeneration is targeted for a future release.
Until the fix is available, apply the following workaround.
Local Change (Workaround)
- In Dev Studio, open the affected Case Type.
- On the Settings tab, verify that the Label field does not contain special characters such as parentheses. If it does, remove them and save the Case Type rule.
- Navigate to and open the application rule.
- Unlock at least one ruleset in the application. The button is disabled when all rulesets are locked.
- Navigate to , select a ruleset belonging to the application, and check it out.
- Return to the application rule, click the Advanced tab, and click . Wait for the process to complete.
- Save the application rule.
- Navigate to the Advanced tab and use to confirm that no entries for the affected Case Type contain parentheses. If stale entries with parentheses are still present, manually remove them from the routing table and save.
- Clear the browser cache and local storage, then close and reopen the browser.
- Open the affected Case Type and refresh the browser to confirm the HTTP 400 error no longer occurs.