Skip to main content
Version: 18

Translations

On this page, it is possible to manage (create/update/delete) white label translations. It's also possible to import/export them.

White label translations can override default product translations if they have the same code. This allows white labels to customize text in the application.

Import / export​

JSON​

The normal import/export will use a json format, and should be used for archival purposes. It's a technical data format and is designed to be easily machine processed.

CSV​

The CSV import/export is designed for handing over translations to third parties, as this format can easily be modified using tools as Excel. Note that all columns in the export must be preserved on import so no translations get removed.

Email translations​

The CSV import/export format does not support EMAIL_ translations. Due to their hierarchical structure they are maintained with specific and complex Excel sheets which contain scripts to export to the JSON format which can then be imported.

Adding white label translations​

If you want to add a white label translation, you need the identifier of the label you want to override. There's two ways to find out the identifier:

  1. Navigate to Runtime > Caches & utilities and click the button Toggle translation mode
  2. Add ?translationMode=enabled and subsequently ?translationMode=disabled at the end of your web address.

Both methods will enable translation mode, which will expose every label identifier. However, if you have requested a new field or configured a new error message which does not have a label yet, no usable identifier will be exposed.

Most white label identifiers follow the following format:

  • BACK_END.FIELDS.XXX.label
  • FRONT_END.VALUE.XXX
  • FRONT_END.ERROR.BE.GENERAL.XXX

Front end identifiers are not supported in the profile PDF. Therefore, make sure the back end translation is available if this is your goal.

Variables​

Depending on the context, white label translations also support variables.

Information Exchange​

  • {{dossierName}}
  • {{dossierNumber}}
  • {{fspName}}
  • {{clientName}}
  • {{partyName}} (only in party flow steps)