Ok, so Surveys, Assessments etc require their translations in specific translation tables,
As a recap, UI translations in the platform leverage the following tables:
- sys_documentation - field labels
- sys_choice - drop down choices
- sys_ui_message - scripted messages
- sys_translated - translatable strings
- sys_translated_text - translated text
If you'd like a far more in-depth overview of how it all works check out our training course on NowLearning here,
With that being said, you'll need to follow the following concept:
- The name / description of the Assessment / Survey - asmt_metric_type.name > sys_translated_text (the "document" field will be the sys_id of your source Survey)
Like this:
- The name of the Category of questions in the Survey - asmt_metric_category.name > sys_translated_text (the "document" field will be the sys_id of the source Category's sys_id which is related to your Survey)
Like this:
- Per question - asmt_metric.question > sys_translated_text (the "document" field will be the sys_id of the question in your survey)
- If you have a Description - asmt_metric.description > sys_translated_text (the "document" field will also be the same sys_id of the source question, make sure you populate the element with the right source field correctly)
Like this:
- Per Choice Choices (if you have any for your questions) - asmt_metric_definition.display > sys_translated_text (the "document" field will be the sys_id of the English source in the asmt_metric_definition table)
Like this:
If you are on Quebec+ and you have the "Localization Framework", it is also absolutely possible to make a custom "artifact" to identify these elements, where you can then request translations from the English source survey. Instructions on how to do that are available on Docs here,
Many thanks,
Kind regards
