Translation

Translation

It is possible to add multi-language support to components using translation files. Create a new translation file for each language you want to support under the resources tab of the advanced editor. These files (like media files) are saved in the workflow, not the component. This means that all translations can be used in all components.

You can access translations using ${ ... }.

Here is an example:

exceptions.keyword.pause=Pause Workflow <expression><![CDATA[#{event:command} == toUpperCase('${exceptions.keyword.pause}') ]]></expression> 

It is also possible to access translations from the JavaScript context. However, JavaScript uses the ${} notation for template literals (template strings)

Functioning example: ?{ var string = value + ${translation.value};  }? Not functioning example: ?{ var string = `${value} ${translation.value}`}? 

JavaScript can also be used to determine the translation key to access:

${label.?{ // code that returns a string with the key}?.title} 

No assignment this time, but feel free to try it out!

Congratulations! You have finished the first part of the Creator Developer Training and you should now be able to create your components. 

We have created a cheat sheet that summarizes the most important aspects of workflow development.

If you have suggestions on how to improve this training and have questions that were not covered, please give us feedback via your channel account manager. You may also reach out to us by posting questions on our Support forum.