When scanning a custom Lobby or Lobby element for translatable text, should the component be set to 'No Module,' or is it better to create a dedicated new module just for custom lobby translations?

All FAQ questions / Platform, Aurena, and customization

Answer

Neither — lobbies are configurations, and translation scanning for lobby elements/pages defaults to (and should stay on) the 'CONFIG' component rather than 'No Module' or a purpose-built new module; there's no need to create a separate module just for this. Once translations are saved against CONFIG, they're stored in the same ordinary translation tables used for the rest of Enterprise Explorer, so the standard Translation Manager tool (Administration > Export/Import Language Files, selecting the CONFIG component under Foundation1 and the layer/languages needed) can export and import them the same way it does for any other translatable content, including moving them between environments.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Platform, Aurena, and customization questions