Question

4
Replies
2414
Views
Michael Tan (tanm1)
PEGA
Sr. System Architect
Pegasystems Inc.
JP
tanm1 Member since 2016 39 posts
PEGA
Posted: May 23, 2018
Last activity: May 25, 2018
Posted: 23 May 2018 3:06 EDT
Last activity: 25 May 2018 4:43 EDT
Closed

pyStatusWork field value not selected as display value of work status

In order to set the display value for our work status "Open-HyojunHizukeShutoku" we created a field value pyStatusWork with the desired label (see 1.png).
However, on screen it displays the key, and not the translated "To" value from the field value (see 2.png).

Similar to our phenomenon I found the following articles.
  https://pdn.pega.com/support-articles/localized-value-pystatuswork-not-picked-during-display
  → https://pdn.pega.com/support-articles/localized-value-pystatuswork-not-picked-during-display
  → https://pdn.pega.com/community/pega-product-support/question/pega-719-localize-values-are-not-reflected
  https://pdn.pega.com/sites/pdn.pega.com/files/help_v731/procomhelpmain.htm#tools/localization/ui-localized-properties-ref.htm

But there are some key differences:
・ my own Live UI found that the property pyStatusWork (is on section pyCaseAssets and) uses the control "Formatted text", not "pyWorkAssignmentStatus" as the above articles suggest. "Formatted text" is auto-generated so I can't see its HTML to determine what field value it is attempting to access;
・ I created a field value pyStatusLabel identical to pyStatusWork above as suggested in the first article but it had no effect;
・ I created a field value pyCaption identical to pyStatusWork and it worked: the translate "To" value of the pyCaption was used.

So here are the questions:
1. pyCaption is the most generic field value: surely this is not the recommended way to translate pyStatusWork?
2. Why is the translation in the field value pyStatusWork not used?
3.
Show More
In order to set the display value for our work status "Open-HyojunHizukeShutoku" we created a field value pyStatusWork with the desired label (see 1.png).
However, on screen it displays the key, and not the translated "To" value from the field value (see 2.png).

Similar to our phenomenon I found the following articles.
  https://pdn.pega.com/support-articles/localized-value-pystatuswork-not-picked-during-display
  → https://pdn.pega.com/support-articles/localized-value-pystatuswork-not-picked-during-display
  → https://pdn.pega.com/community/pega-product-support/question/pega-719-localize-values-are-not-reflected
  https://pdn.pega.com/sites/pdn.pega.com/files/help_v731/procomhelpmain.htm#tools/localization/ui-localized-properties-ref.htm

But there are some key differences:
・ my own Live UI found that the property pyStatusWork (is on section pyCaseAssets and) uses the control "Formatted text", not "pyWorkAssignmentStatus" as the above articles suggest. "Formatted text" is auto-generated so I can't see its HTML to determine what field value it is attempting to access;
・ I created a field value pyStatusLabel identical to pyStatusWork above as suggested in the first article but it had no effect;
・ I created a field value pyCaption identical to pyStatusWork and it worked: the translate "To" value of the pyCaption was used.

So here are the questions:
1. pyCaption is the most generic field value: surely this is not the recommended way to translate pyStatusWork?
2. Why is the translation in the field value pyStatusWork not used?
3. If pyCaption (or pyStatusLabel, or any other field value) is the correct location for the translation, why do we still need a pyStatusWork field value?

Show Less
Low-Code App Development Data Integration
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.