Multilanguage Support

Pipeliner Admins can add their own language translations to system and custom fields as well as validated lists such as dropdowns

Updated over a week ago


Pipeliner Administrators now have the option to add additional multi language translations directly in the Admin Module via Fields & Forms or the Translations tab which is activated when the Multilanguage Support Add-on is enabled.

Field Names, Form Field Labels, Form Field Descriptions and items from validated lists - dropdown values, multi-select checkbox lists and radio button entries - can all be translated. ⤵

What Languages are currently supported?

As of version 5.3 (February 2024), English, German, Portuguese (Brazilian) and Spanish are supported languages.

How to enable the Multilanguage Support add-on

Multilanguage Support is enabled from the Automation Hub in the Admin Module. ⤵

Multilanguage Support is available to Unlimited and Enterprise Tier customers. For Business and Starter customers, this is a paid-for Add-on. Please contact your Account Manager to discuss adding to your subscription.

Adding Translations

Once the Multilanguage Support add-on is enabled, Pipeliner Admins can use 2 options to add translations:

Contextual translation - translations are added in the Fields & Forms menu. Admins can add translations directly via the Fields tab or on the Form. The Translation icon identifies every value that can be translated ⤵

Bulk translation - from the Translations menu in the Admin Module, Admins can access all translation markers (even virtual fields can be translated like Last Contacted Date, Account Type etc…). This screen offers a uniform overview of translation markers. Using the Filter option, an Admin can easily filter all occurrences of the Field and translate them all at once ⤵

When a translation has been added to a Field Name or any values in a list, the Translations icon will display next to the value in a darker colour so it’s easy to identify where Translations have already been added ⤵

All translations are saved in draft until Published so Admins can work on translations over time and then Publish them all to the application. However, translations are tied to Field or Form changes so if other changes are made that require an Admin to Publish them, all draft translations will also be published at the same time ⤵

There are three terms used when adding translations:

Original value - This is the value that is available and visible only in Admin, this value cannot be translated. The original value is, for example, the Field Name or Field Label.

In the example below, the Original Value is “Contract Type” as shown in the “Field label in this form” field ⤵

Display value - These are the values entered by the Admin and that are then visible within the CRM app. Users will see the corresponding Display Value depending on their language selection in their User Account Settings.

In this example, the User has selected German as their language in the User Account Settings and so sees the German Display Values

Fallback value - where no Display Value has been added, the Fallback Value will always be displayed. The. Original Value is always used as the Fallback Value

Using the same example, fields where no German Display Value has been added still display in English (the Fallback Values) ⤵

NOTE: when Multilanguage Support is initially enabled via the Automation Hub, users within the CRM application will not be impacted as they will continue to see the original values (Fallback value) until additional translations are added and published.

NOTE: Importantly, you need to be aware that only the Original Value is EVER used when exporting data or using the Pipeliner API.

How does a User change their Language?

User Account Settings are accessed from the User Avatar icon and by then clicking on the gear icon ⤵

Select from English or German in the Languages dropdown and then scroll down to click on “Save” to apply the selection ⤵

Additional Resources/Next Steps

Did this answer your question?