Issue

When using the Localization Wizard to translate the application, not all UI strings are translated when viewed in Pega Constellation. 

Symptoms and Impact

From Pega Infinity™ ‘25 onward, localized rule sets do not need to appear in the App Studio localization wizard and are instead resolved automatically at runtime based on the user’s locale. A successful migration should result in a single consolidated localization bundle within a ruleset suffixed with a locale code, which is sufficient for your localization.  

In some scenarios users find that dynamic text in Paragraphs is not displaying the localized value despite being available in the new bundle and being present on the view definition. 

Prerequisites that cause these scenarios:   

• Use an open ruleset or enable branching during localization work. 

• Verify the top-most ruleset in the application stack exists and is available. 

• Ensure language rulesets are added to the application ruleset stack for runtime resolution. 

• For built-on applications, use Re-translate all layers = true when generating translations from the top-most application. 

Steps to Reproduce

1. Update the Constellation rules using our documented steps in Updating Constellation rules in an application. 

2. Run the activity pxMigrateToLocalizationV2 for each existing localization to merge its localization Rules into a single bundle based on the locale code.  To do this: 

   1. Navigate to Dev Studio and open activity Rule-UI-Localization.pxMigrateToLocalizationV2. 
   2. Click Actions > Run, enter the locale code in ISO format (e.g., fr-FR), execute for each language requiring migration, and validate the success message from the activity output. Note that this creates language rulesets using underscore convention (e.g., ruleset_fr). 

3. In the navigation pane of App Studio, click Settings > Localization. 

4. On the Localization landing page, on the Translation packs tab, select Language and click Download and then select the format of the translation package. 

5. The ZIP package includes the paragraph\base file that contains the source for paragraph Rule text. You can localize the paragraph Rules by updating the text in the files in the paragraph\translated folder. 

6. Localize phrases that use dynamic values to replace a placeholder value by following steps in Localizing dynamic values.  

7. Export and Import the package. 

8. Switch to App Studio and preview the translation in a Paragraph rule: Expected: the new translation package includes phrases with dynamic values. Actual: values are missing.   

Root Cause

The issue is caused by a defect in the Constellation static assets delivered with the base 25.1.2 patch version where Dynamic text localization functionality is faulty.   

In Pega Infinity ‘25, we switched from having individual locale files for every View, Case Type, and component in the application to a unified bundle of translated strings for the entire application.  

The old singleton store (a centralized data storage mechanism designed so that only one instance of that data store exists across the entire application lifecycle) uses a single, globally shared localization object (localeUtils) that is fragmented across individual locale files — one per View, Case Type, and component. Multiple fetches are required per session, which often causes gaps (untranslated strings showing up) and slower load times. 

Solution

Update to 25.1.3 or 26.1 where paragraph related code will properly display the localization functionality for paragraphs. 

 The latest releases have updated the handling for the dynamic text localization functionality to replace localeUtils import and usage functionality with getLocaleUtils(). 

Recommended Next Steps 

Please take the following actions: 

• Update the ConstellationPegaStaticURL Dynamic System Setting to point to the latest available Constellation hotfix CDN for the affected version (here 25.1.2): 

https://release.constellation.pega.com/cs/25.1.2-HFIX-20260716100946&nb…;

• Perform a hard browser refresh of the user portal after applying the change. 

• Open browser Developer Tools → Network tab. 

• Check that Constellation JavaScript and localization requests are being served from the updated hotfix URL 

• Verify if translated labels display correctly when the operator locale is set to your target language. 

References

What's new in Constellation UI   

Localization on Constellation fails after update to Pega Infinity '25 

Overriding Localization Bundles in Infinity 25  

Updating Constellation rules in an application