Multilingual Tokens

Utilizing Merge Tokens

The platform now allows users to utilize these tokens in reports, templates…etc in multiple languages. The field values are not only rendered in the user's default language but can also display content in any desired supported language by utilizing specific merge tokens combined with language codes.

Note: User can also use the help token without any loop.

Default Language Utilization

For utilizing the merge tokens in reports, templates, etc in the system's default language, use the standard merge token format:

{!lastName#value}

This token automatically renders the lastName field in the system’s default language.

Multilingual Utilization

For utilizing the merge tokens in a language other than the default, append a language code #langCode to the merge token. This ensures that the specified field value is rendered in the desired language.

{!lastName#value#langCode}

Replace langCode with the appropriate language code (e.g., fr for French). For example, to render the lastName field in French, the merge token should look like this:

{!lastName#value#fr}

Likewise, users can leverage various other merge tokens #label, #text and #help with #langCode to support multi-lingual report generations.

Object Help Merge Tokens

With the introduction of Object Help Merge Token {!#OBJ.<Object Integration Name>#help} support from Platform 6.10, users can expect enhanced readability and consistency across help documentation and implementations, as the format for all Object merge tokens is now standardized. This feature includes support for the new merge token and improved guidelines for using various Object tokens.

Supported Object Help Merge Tokens

The following merge tokens are now supported in addition to those previously available. It is recommended to use the tokens listed below for clarity and uniformity:

  • Object Id: {!#OBJ.<Object Integration Name>#id}

  • Object Label: {!#OBJ.<Object Integration Name>#label}

  • Object Description: {!#OBJ.<Object Integration Name>#description}

  • Object Help Description: {!#OBJ.<Object Integration Name>#help}

Note: In Platform version 6.9, the tokens {!#OBJ_DESCRIPTION.<Object Integration Name>} and {!#OBJ_LABEL.<Object Integration Name>#text} were introduced. These tokens are no longer supported from version 6.10. Users are advised to use {!#OBJ.<Object Integration Name>#description} and {!#OBJ.<Object Integration Name>#label} tokens to retrieve the object description and label, respectively.

Button Help Merge Token

In addition to Object merge tokens, a Help merge token for buttons is also implemented to allow integration of help descriptions specific to buttons using the format:

{!#BUTTON.<integrationName>#help#fr}.

Workflow Action Help Merge Token

A Help merge token for workflow actions is also implemented to allow integration of help descriptions specific to workflow using the format:

{!#WF_ACTION.<integrationName>#help#fr}.

Note: Integration names are mandatory for Object, Button and Workflow Help Merge Tokens