BIX - History- .pyMessageKey not localized
Hi,
I am running BIX extract to export work history for work object but pyMessageKey and pyMemo fields are not coming as they are displayed on UI. I noticed they were localized before displayed in listview - is there any way to localize it before or after BIX extract?
Thanks
Haroon
***Updated by moderator: Lochan to add Categories***
Northbridge
CA
Before displaying in UI, Pega usually calls getLocalizedTextForString()/getLocalizedText() functions to get the LocalizedText for the String/Property respectively.
BIX extract would definitely not export the localized values. BIX is used to extract property values from BLOB to external sources like CSV, excel or DB.
If it is necessary to export localized values, you may create a new column/property to store the localized values in the work- class. This new column(an overhead) will not be used anywhere else except for extract.
SAP NS2
US
Thanks for the reply. Those localize functions don't work when used in activity to covert MessageKey to new property. Upon more research in Pega control - they are displayed as literal (DisplayAsLiteral) on UI. Is it different from localize ? Is there any function available to concert as literal in activity?
Thanks
Haroon
Northbridge
CA
In Pega Help it is mentioned Mode Literal/ displayAsLiteral control is used when we have to mask the property from HTML processing.
Literal mode is quite different from localization. If you're using getLocalizedText() in an activity, it shouldn't matter which control the property uses.
In the first Java step of the activity pzGetWorkHistoryPostProcessing, the pyMessageKey is being localised. Could you please refer it and use it accordingly in your scenario.
PEGA HELP---
Mode Literal: Causes the value of the property to be masked from HTML processing. Use this if the value may contain angle bracket characters or other HTML elements that are not to be interpreted.
When you save a stream rule that includes a reference tag with this mode, you may receive a security warning message:
In Pega Help it is mentioned Mode Literal/ displayAsLiteral control is used when we have to mask the property from HTML processing.
Literal mode is quite different from localization. If you're using getLocalizedText() in an activity, it shouldn't matter which control the property uses.
In the first Java step of the activity pzGetWorkHistoryPostProcessing, the pyMessageKey is being localised. Could you please refer it and use it accordingly in your scenario.
PEGA HELP---
Mode Literal: Causes the value of the property to be masked from HTML processing. Use this if the value may contain angle bracket characters or other HTML elements that are not to be interpreted.
When you save a stream rule that includes a reference tag with this mode, you may receive a security warning message:
>>Warning>> Using mode=literal can expose the system to cross-site scripting attacks - use with caution.
Caution: For maximum security, do not use mode="literal" anywhere in the HTML code that formats a property value for a property that is an input value. For example, assume that a <textarea >on a non-autogenerated flow action form allows input of arbitrary text (including angle bracket characters) that is submitted to PRPC and returned to the browser in literal mode (not encoded). A malicious user could "inject" harmful JavaScript source code into the browser, a tactic loosely termed "cross-site scripting" or XSS.
Consider richtext mode as a more secure alternative.
In all modes other than literal, the angle brackets are converted to HTML entities (<, >), invalidating the JavaScript code.
In rare situations, your application may require mode="literal" in stream rules. For example, the JavaScript target of a button, executed with the onClick= attribute, may be dynamic. Design and test such cases with extreme care.
------------------