Support Article
Field values not localized
SA-94241
Summary
In Pega Platform 8.3, the following issues related to field value localization occurs:
- The 'Value cannot be blank' field value is not translated to Chinese despite adding the converted field value to the localized ruleset.
- The 'Select...' placeholder in the Category dropdown of the Data-WorkAttach-File!pzAttachFileBrowseMultiDD_P section, is not translated to Chinese. This occurs despite creating a field value for 'Select..' in the localized ruleset.
Error Messages
Not Applicable
Steps to Reproduce
Issue 1:
- Drag a text input and configure it as Required.
- Create a field value for 'Value can not be blank' in localized ruleset.
Issue 2:
Create a field value for 'Select..' (placeholder in the Category dropdown) in the localized ruleset
Root Cause
An issue in the custom application code or rules.
Since multiple localized ruleset versions were present, the field value was created in a lower ruleset version. As a result, the correct field value was not retrieved.
Resolution
Perform the following local-change: Issue 1:
- Create the field values in Highest localized ruleset version.
- Add the below script in the UserWorkForm.
<script>
var required_requiredMsgStr = "<pega:lookup property='pyWorkPage.pyMessageLabel' value='Value cannot be blank' mode='literal' />";
</script>
- Create a field value for 'Select..' for the pyCaption property type in the Data-WorkAttach ruleset.
- Save the field value in the highest ruleset version.
Published January 17, 2020 - Updated December 2, 2021
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.