Skip to main content

Translate objects

Object names, summaries, and purposes can exist in every language the repository supports. Maintain the translations directly in a grid, or export them to Excel for translators and import the result.

Prerequisites​

  • The repository supports more than one language — a repository administrator configures the languages.
  • Imports apply with your permissions: objects you can't modify are skipped.

Steps​

Edit translations in the grid​

  1. Open the user menu (your avatar) and select View Languages.
  2. Pick an item in the tree. The grid shows one column per repository language and the item's translatable text.
  3. Select Edit and fill in the translations — or double-click any cell to edit just that one, without selecting Edit first. Text without a translation falls back to the repository's main language, then to the text's original language.

The View Languages grid with object names in each repository language.

You can also translate a single field where you edit it, through the flag beside it — see the language flag on a text field, which also covers why an object's name can't be emptied in its source language.

Export for translation​

  1. In the View Languages view, select the item whose subtree you want translated.
  2. Click Export. The export covers the selected item and all its children — the dialog tells you how many items. It produces an Excel 2003 XML file with one row per translatable text (name, summary, purpose) and one column per language. Empty summaries and purposes don't create rows.

Import translations​

  1. Have the translations filled into the exported file — the format must stay Excel 2003 XML, and the file must come from the same repository (imports are matched by object ID, not by name).
  2. In View Languages, click Import and choose the file.

The import runs as you, skipping objects you lack permission for. For versioned items — diagrams, IGX documents, external files, reports — the import creates a new version and can't apply while the item is checked out. A name omitted in the original language keeps its existing value.

Through the REST API​

Object name translations are also reachable through the REST API, under Localization in the API documentation:

EndpointWhat it does
POST /api/localize/{repository}/translations/getGet object translations — send the object IDs and the languages you want, and the response gives each object's name per language, or null where there's no translation.
PUT /api/localize/{repository}/translations/setSet object translations — deprecated, though still present. Each language you send must be an enabled additional language of the repository.

Both endpoints cover object names only; summaries and purposes go through the grid or the Excel round trip above. Both require the Manage Repository Configuration repository permission, and both have existed since 17.3.0.

Limitations​

  • The export and import don't cover dashboardDashboard A configurable view in Process360 Live that aggregates KPIs, charts, and filters across one or more processes for stakeholders to monitor performance. gadget names or Rich Text gadget content.
  • Excel doesn't support bullets, so the round trip doesn't support bulleted text.