Question
Skandiabanken
SE
Last activity: 26 Nov 2018 16:46 EST
Localizing - Case Process Menu (Navigation rule pzStartProcessMenu)
Hi all,
I want to localize the navigation rules. I tried to use field values in the label field. I used field values with field name as pyLabel, pyActionPrompt, pyCaption and with custom field name as well.
Nothing worked.
I also created a property to use in labels and created corresponding field value. It also did not work.
I also want to localize the tooltip displayed on the menu.
So please provide me suggestions to localize the navigation rule.
Pega Version :7.3.1
***Edited by Moderator Marissa to update platform capability tags****
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
Skandiabanken
SE
Found work around .
Instead of referring the Property for displaying the Label in navigation rule, Refer the Field value and mentioned the {.pyLabel LocalizeValueCaption} in field value . Created the field values (pyCaption) for the list of possible values comes on menu.
Let me know if any better work around?
Pegasystems Inc.
US
To use Field Values in a Navigation Rule for the caption (pyCaption):
1. Select Field Value from the dropdown that says Text by default. This dropdown is immediately to the right of the word, Label on the General tab of the navigation rule form. It is the pyLabelType property (us Live UI to confirm if you are unsure).
2. Select an existing field value rule or click on the cross hairs to the right of the pyCaptionPrompt property (again, Live UI is your friend).
Once you have done this, the field value referenced here will be exported as part of the localization process. it will appear in the Excel worksheet as part of the export process.
Hope this helps!
Skandiabanken
SE
As i mentioned earlier .Label value is not static to refer the field value and it's configured with property for "Item List". Can you please just verify the pzStartProcessMenu
Attached the screen shot .
Pegasystems Inc.
US
Because pyLabel is a text property with no assigned Field Value list, you will need to create the Field Value rules for both the base language and the localized language. Therefore, I believe what you have done by using the LocalizeValueCaption is the best approach. You have to create the FieldValues that you want to have displayed. pyCaption is the proper property to use for this.
I am assuming you have checked the checkbox labeled "Localize labels, tooltips and descriptions" as you did not mention it. Can you confirm this? If you have done so, then I would think that simply creating the pyCaption based Field Values properly should enable localization to work.
Skandiabanken
SE
I tried to make generic Field value rule which can take the param value from all sources like Navigation, etc and display the respective localized value But i'm unable to make it .
I tried to refer the below code in Navigation rule where the following pycaption field value could configure .
"DisplayLocalizeLabel\t"+.pyLabel
In DisplayLocalizeLabel field value rule , Added Parameter to it and referring like {1 LocalizeValueCaption} .
Navigation rule is not saving .
Pegasystems Inc.
US
Try doing the following in your DisplayLocalizeLabel field value rule and see if that works:
{.pyLabel}
Remove passing the "pyLabel" property from nav rule since you field value should have access to that property. Your nav rule(pzStartProcessMenu) with "Label" selection of "Field value" should only have DisplayLocalizeLabel (without quotes)
You could find similar examples in pzCreateCaseViewInfo which has the following:
Add mapped fields to '{.pyLabel}' view (in '{.pyClassLabel}' case type)
If this works you could do similarly for tooltip.
Skandiabanken
SE
Any work around to make it generalize field value to support all localization look up.
Skandiabanken
SE
Whenever FieldValue is configured to refer the control Like {.pyLabel LocalizeValueCaption} and try to refer it from Navigation rule ( in Item List context) then Fieldvalue is not opening at all and server is getting down ..