It should be, at least it is for Markdown Text in the ServiceEngApp MWO Client File:

If you’ve purely added the content from Page Designer though, I don’t know if that creates the text translation entry. There might be a step in between to make it accepted as a translatable text entry.

With Customizations you have to generate the translation file and import it with Scan Translatable code, but I don’t know if you have a similar capability if the entry is added through the config layer in page designer directly.

Hi ​@SimonTestard,

Thank you for your feedback.
Yes, indeed, there are existing entries for standard elements (such as the markdown message in the context mapping screen).
However, no lines are created for elements added with the Page Designer.
I imagine this is a limitation.

Théo

It should be available to translate in Translatable Text under the CONFIG Module, at least it is for me (The Context Config added entry in page designer probably needs to be published obviously).

https://docs.ifs.com/techdocs/22r2/040_tailoring/225_configuration/200_client_configurations/350_translations_in_configurations/

That's right! I missed that... thank you!