Translate The S-Sign UI

Introduction

You can translate the S-Sign end-user signer experience in just a few easy steps. Watch the video below or follow the written instructions to get started with S-Sign translation.

Tutorial Video

Step 1: Define Translations

Step 1 is to define translations for your language. This can be done in two different ways.

Option A: Define Your Own Translations

If you want to define your own translations, you can do so on the S-Sign translation page. If you are using S-Docs 4.381+, navigate to this page by clicking the App Launcher, typing in "S-Docs Setup," and clicking S-Docs Setup in the dropdown menu. From there, scroll down to the Translate UI section and click Go To S-Sign UI Translation Page.

If you are using a version of S-Docs below 4.381, the S-Sign Translation page can be accessed by adding the following URL after "salesforce.com" in your browser:

/apex/SDOC__SDConfig?translateSSign=true

The S-Sign Translation page appears as follows:

If you've defined translations for a language on this page before, you'll be able to [1] choose a language and [2] edit the translations for that language. If you haven't accessed this page before, you'll need to [3] enter the name of a language and then [4] click Define new translations for this language to bring up a list of available S-Sign fields that you can translate.

[1] The English version of each S-Sign field that can be translated appears on the left. You can translate the text in the text box on the right. Make sure to [2] click Save when you are done entering your translations.

After defining your translations, you must add the translate parameter to your S-Docs button.

Option B: Import S-Docs Translation Templates

S-Docs provides a number of templates that you can download to translate the S-Sign UI immediately. To use the translations we provide, begin by importing one of the following templates. Click the link to download the template .zip file and use the template migrator to import it into your org. For more detailed instructions on importing a template into your org, please click here.

When your translation template is downloaded, the template record should look similar to this.

Notice that Available for Use and Initially Visible have been unchecked, since this isn't a template that can be used for document generation; it's simply providing the translation for the S-Sign user experience.

After downloading a translation template, you must add the translate parameter to your S-Docs button.

Step 2: Add The Translation Parameter To Your S-Docs Button

Note: The S-Docs button comes prepackaged for the following standard objects: Contract, Opportunity, Account, Contact, Lead, Task, and Event. Because of this, the button will be managed and therefore unable to be edited for these objects. You will need to create a new S-Docs button (and replace the old button on the object's page layout) to make edits.

Add the following parameter to the S-Docs button you will be using with S-Sign (replace Spanish with the name of your language):

ssignParams='language:Spanish'

In this example, we'll add it to the S-Docs button for the Contact object. Navigate to Setup by clicking the cog in the upper right of your screen, then go to the Object Manager tab. Click your object.

Then, navigate to the Buttons, Links, and Actions tab. Find your S-Docs button and click Edit.

Add the parameter to your button.

{!URLFOR('/apex/SDOC__SDCreate1', null,[id=Contact.Id, Object='Contact', ssignParams='language:Spanish'])}

Click Save, and you're all set! The S-Sign user experience will now be translated.

Setting Language on a Per-Document-Envelope Basis

You can also set the S-Sign language for individual document envelopes through the SSIGN__Language__c field. When building automation using the S-Docs Job object in conjunction with Salesforce Process Builder or Apex, set the S-Doc Job field SSign Language to your chosen language. This will cause the S-Doc Job record to set the S-Sign Envelope Document field SSIGN__Language__c to that language.

Tags:

Was this helpful?