Could not see this covered anywhere else.
Why is it that when a copy is taken of the OOTB Service Portal index page (using the Clone Page UI action), when previewed and the language is changed, a lot of the widgets do not translate.
E.g Taking a clone of index, and setting the language to French (I did add language picker to make it easier):
As you can see, the header has translated but the 'Homepage search' widget has not, not has the catalog, knowledge, incident record producer etc links
However with the OOTB page, they do:
Using the same widgets, cant see any messages on the sys_ui_messages table about the homepage search widget that require adjusting.
Seems a bit strange, as if its a copy I thought it would just use the same translated text/messages etc.
Regards
James
Hi Chuck,
Thanks for the reply ctomasi
Unfortunately it is not related to the preview, this was happening with the normal URL.
But fortunately I worked around this earlier today.
Steps below for anyone who finds this thread and has the same issue:
1. Changing my own language preference (as admin about to make some changes) to the desired one, in this case Polish.
2. Opening Service Portal > Service Portal Configuration > Portal Designer > page with the non translated widgets (mostly by button memory, as I do not speak Polish )
3. Selecting the widget to translate, using the amendment (pencil) on the widget and changing the title and description from English to the translated version.
Example screenshot below of the 'Get Help' icon link about to be translated, when language preference was French:
4. Once saved the amended widget(s) will show the translated version to users where their language preference is Polish (or whichever language mine/yours was at the time the change was made), but leave the original version as English (or whatever the default was).
What it is actually doing in the background from this action is creating records on the Translated Text [sys_translated_text] table, so if a lot are required they could be generated/imported directly there. Obligatory screenshot:
5. As an addition, I noticed the 'typeahead search' in the 'How can we help?' search field had also not translated and the entry on the sys_translated_text table was not being used as...to cut a longer story short...the widget's code was not setup to read it. However by putting {title: '${How can we help?}', size: 'lg', color:'default'} in the typeahead field of the widget, it finds the translated text (careful with the spacing/syntax):
The confusing part for me was why the above was not required for the OOTB widgets, as I could see no entries on the tables but assume this must be as the cloned version is using an instance of the widget perhaps as oppose to OOTB being the original.
Anyway, hope this is of help to someone.
Regards
James
Hi Chuck,
Thanks for the reply ctomasi
Unfortunately it is not related to the preview, this was happening with the normal URL.
But fortunately I worked around this earlier today.
Steps below for anyone who finds this thread and has the same issue:
1. Changing my own language preference (as admin about to make some changes) to the desired one, in this case Polish.
2. Opening Service Portal > Service Portal Configuration > Portal Designer > page with the non translated widgets (mostly by button memory, as I do not speak Polish )
3. Selecting the widget to translate, using the amendment (pencil) on the widget and changing the title and description from English to the translated version.
Example screenshot below of the 'Get Help' icon link about to be translated, when language preference was French:
4. Once saved the amended widget(s) will show the translated version to users where their language preference is Polish (or whichever language mine/yours was at the time the change was made), but leave the original version as English (or whatever the default was).
What it is actually doing in the background from this action is creating records on the Translated Text [sys_translated_text] table, so if a lot are required they could be generated/imported directly there. Obligatory screenshot:
5. As an addition, I noticed the 'typeahead search' in the 'How can we help?' search field had also not translated and the entry on the sys_translated_text table was not being used as...to cut a longer story short...the widget's code was not setup to read it. However by putting {title: '${How can we help?}', size: 'lg', color:'default'} in the typeahead field of the widget, it finds the translated text (careful with the spacing/syntax):
The confusing part for me was why the above was not required for the OOTB widgets, as I could see no entries on the tables but assume this must be as the cloned version is using an instance of the widget perhaps as oppose to OOTB being the original.
Anyway, hope this is of help to someone.
Regards
James
