We are trying to localize our application in multiple languages in Constellation 25.1.2 via App studio.
We faced few issues during our journey which are mentioned below:
For example, I have a data type whose records are displayed in the UI across multiple scenarios. I want to understand if it’s possible to localize this data, considering that the Excel (ZIP) does not include these values for localization.
If we do localize the data and display it in the UI, will the Pega server still correctly interpret the selected value when a user chooses an option (for example, from a dropdown or another control)?
Can banner messages can be localized? These values are set in pre processing of flow actions in multiple places.
Since have multiple languages being used - how do we tackle override bundle in this scenario? Should we create override bundle for each language as base bundle is created for each language in a separate ruleset.
Is support available for Swahili language in constellation 25.1.2 ? as the language pack was not available.
HFIX‑D837 - We saw this hotfix is needed for retranslate all layers in one of the forums, also, Genai for translation is not working as the exported excel has translated column blank though Genai is enabled.
We are still working ways to figure out these things, if we get some solutions, work arounds for the same, it will be great for us.
For data type and banner text missing from the localization Excel, add those values as Additional Text against the Data page property, then re-sync and re-download the pack to bring in the translations. The server still reads the stored key behind each option, so the user’s dropdown choice is interpreted correctly no matter the display language. Since each language sits in its own base ruleset, create one override ruleset per language rather than sharing one. Swahili has no ready-made Pega language pack, so build your own through App Studio’s Localization settings instead of waiting for one. For the retranslate-all-layers failure and the blank GenAI column, log both with support and request HFIX-D837, since the equivalent fix built for 25.1.1 cannot be installed on 25.1.2.
@Sairohith Thanks for the inputs,
Swahili has no ready-made Pega language pack, so build your own through App Studio’s Localization settings instead of waiting for one. → can you please provide me the steps if possible for this
I have an additional query along with this. Lets say we have a read-only view in which we are showing some fields. There is a field called Branch Code - which has value B0001. Now, wherever I see this B001 as a value on screen, I need to replace it with value based on locale like ‘Main’ in English, ‘Mein’ in Dutch etc… For this in Theme Cosmos, we just created field value pyCaption in @baseclass so that wherever this value appears on the screen it replaces it. Now, how to do it in Constellation?
Branch should be a data reference, you can then show additional details about that data reference. So I would expect the “Branch Name” to be Main - you would then localize the value Main for “Mein” in Dutch? I don’t think you want to go down the path of trying to localize every code and value…
There is an implementation called Code Table in PegaIns framework. This table has various codes and their respective locale values present in it. Along with this, field values are created automatically when there are new records entered into this table. So, as of now, client uses a separate global system to add codes and their respective translations. They will be received into Pega and automatically got localized due to creation of field values. So, on almost all screens, various properties actually contain the code and the view for end user has the translated value of that code. Now, we are modernizing this application to Constellation, but we see codes everywhere as field value does not work. If it is just one language, we can manage it somehow for many fields like dropdowns, by selecting display value as this label and storage value as code. Now, it is again a multi-language application. Just looking for best solution for this challenge.
The process would be enable CRUD on data, to add the ID and base language name (e.g. English) and then update your localizations for the new site name. I haven’t seen any other way of doing this but will see if we can get some expert comments on this.