Multinational companies with employees and customers based around the globe need to do business in a variety of different languages. S-Docs provides a number of language translation options that you can leverage to give your users and customers a seamless experience, whether they're using S-Docs internally or viewing generated documents. This article will go over key points of consideration and provide you with the necessary resources for translating S-Docs based on your requirements.
The two main aspects of S-Docs that can be translated are:
- The S-Docs user interface that admins and business users interact with inside of Salesforce
- The content of your generated documents that customers and internal stakeholders view
This article will explain how to ensure that both of these aspects are translated based on the languages of your Salesforce users, customers, or both.
Translate the S-Docs UI for Salesforce Users
If your business has multinational employees that need to generate documents, translating the S-Docs user experience can be imperative to allowing them to work as efficiently and seamlessly as possible. S-Docs allows you to translate the entire document generation experience, from selecting templates to sending emails. There are two options for translating the S-Docs UI.
S-Docs provides preconfigured translations for several languages.
Translating the user experience using our preconfigured translations is a simple matter of downloading the desired translation template and adding the translation parameter to your S-Docs button. Once this is completed, the S-Docs user experience will be translated for users that click this button.
Click here for detailed instructions on downloading translation templates and adding the translate parameter to your S-Docs button.
Define Your Own Translations
You can also translate the S-Docs UI yourself by navigating to the S-Docs translation page and translating each field manually.
Click here for detailed instructions on defining your own translations.
Translate Document Content
For companies that do business with customers around the globe, sending documents in your customers' native language can be vital to delivering great customer experiences.
You can create data translation maps to translate any field data in your documents by manually adding values to translate.
Click here for detailed instructions on creating and using data translation maps.
S-Docs can also leverage the Salesforce Translation Workbench to allow you to translate any Salesforce field label and any Salesforce picklist field data.
Ensuring that your documents are generated with translated field labels and picklist field data from Translation Workbench is a simple process:
- Define translations in the Salesforce Translation Workbench
- Add the translate parameter to your S-Docs button (or set the language at the template level)
- Add the translate attribute to your merge fields
Click here for detailed instructions on translating field labels and field data.
Related list data can also be translated using the toLabel() function within a direct soql query.
Click here for more information on translating related lists and lookup fields.
Formatting International Characters
If your template contains international characters such as Japanese or Hebrew, there are a few steps you can take to make sure the text in your output documents are formatted correctly.
If your template contains international characters, you should check the Template contains international characters (Unicode fonts) box under the Document Options tab. If your international characters still don't render correctly, you can set the Unicode Enforcement Level to Strict under the same tab. This will override any font settings being applied to merge fields.
If your documents are written in a right-to-left language like Arabic or Hebrew, you can do one of the following:
- Use the rtl merge field attribute to transform merge field data to be right-to-left. This will not transform static text.
- Use <rtl> tags in the template source to transform both merge field data and static text to be right-to-left.
Click here for more information on transforming right-to-left languages.