Skip to main content

Celonis Product Documentation

Translating Studio Apps

Analysts can enable App Translations and provide a translation Map for user-generated content like Knowledge Models, Views, etc. This feature is a Package setting, and changes are available when published.

Translation maps can be imported/exported to .CSV to facilitate translation on third-party platforms. Supported languages include Dutch, English, French, German, Italian, Japanese, Portuguese, Russian, and Spanish.Translation.

Enable translations

To enable translations in your App, follow these steps:

  1. Go to your Package "Settings" and click the "Translations" tab.

  2. Click "Enable Translations" to activate the feature.

    studio_settings_translations.png
  3. Select the "default language," typically the language your App is built on, and acts as a fallback for missing translations. Click "Confirm" to proceed.

    studio_choose_default_language.png

    Once enabled, access the "Translations" tab to manage the languages you want to provide translations for. Currently, we support nine languages.

    Use the "Active" column to toggle the availability of a language to business users after publishing. Click "Edit" to manage each specific language.

    studio_package_translations.png
Editing languages

While editing a specific language, you'll find two main features:

  1. Name Mappings from File: Export your translations to a .csv file, work with them outside Celonis, and upload them back to the system. The .csv file should have three columns: the translation key, the default language value, and the target language.

  2. Manual Name Mappings: Make quick changes and create new translation keys directly in Studio.

    studio_english_4.png

    For supported Assets (Knowledge Model & Views only), a new option is now available in the toolbar. This option captures all attributes in the asset that aren't translated.

    Studio_ta2.png

    The tool scrapes all strings from the YAML configuration and adds them to the translation map.

    studio_update_translation.png

    For each value, a translation key is created on the translation maps, and the string in YAML is replaced with the corresponding translation key using the following syntax.

    studio_display_name.png

    If you have a value with variables, these variables are passed within the translation key and can subsequently be utilized in key values.

    Studio_ta3.png

    This is how the keys will appear once they are created.

    Studio_ta4.png

    Each variable is converted into a parameterized variable. The order in which the variables are passed to the key is important. So, {0} represents the first variable passed to the key, {1} represents the second, and so forth.

    Studio_ta5.png

    Users can preview the Asset in different languages using the translation button once the Asset is translated.

    studio_language_preview.png

You must publish the package to make the translation available to business users in Apps. Changes to translation maps are displayed as "Package" settings

Once published, the App will be served to the Business user in the language set on their profile in the EMS.

studio_publish_new_version9.png