# Translations

***

### Step 1: Define Your Translations

You can define translations using one of two methods: manual configuration or importing pre-built templates.

#### Option A: Manual Configuration

If you want to create custom translations or support a language not provided by S-Docs:

1. Access the Translation Page:
   * S-Docs 4.381+: Open the App Launcher, search for S-Docs Setup, and click Go To S-Sign UI Translation Page in the "Translate UI" section.
   * Older Versions: Manually append `/apex/SDOC__SDConfig?translateSSign=true` to your Salesforce URL (e.g., `https://yourdomain.lightning.force.com/apex/SDOC__SDConfig?translateSSign=true`).

<figure><img src="/files/cswxqqBTnsQxEBaqOuXw" alt=""><figcaption></figcaption></figure>

1. Enter Translations:

   * Type the name of the language and click Define new translations for this language.
   * The English fields will appear on the left; enter your translated text in the boxes on the right.

   <figure><img src="/files/r1c1KyK9etaEj6EH3f52" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/myt9KJMWZAPl1uQyE6VH" alt=""><figcaption></figcaption></figure>

2. Save: Ensure you click Save once all fields are translated.

{% hint style="info" %}
Translations can be used for more than translating from one language to another. Try leveraging translations to alter the default wording from the managed package that is displayed in the Signer Interface.
{% endhint %}

#### Option B: Import Translation Templates

S-Docs provides pre-configured translation templates for several languages (Spanish, German, French, Polish, and Japanese).

1. Download: Obtain the `.zip` file for the desired language.
2. Import: Use the S-Docs Template Migrator to import the file into your Salesforce org.
3. Verify: The imported record will have "Available for Use" and "Initially Visible" unchecked, as it is a configuration record rather than a document template.

<figure><img src="/files/bpvLholaDCltQ4m0vJMa" alt=""><figcaption></figcaption></figure>

{% file src="/files/6tZEmoS9qTsEMVOfTqKZ" %}

{% file src="/files/UlSCnwGWm7FiVW4o1UJO" %}

{% file src="/files/9GOTUehJuWhESs6gx6VV" %}

{% file src="/files/TsUDsTAZ6s45aXfOJ48d" %}

{% file src="/files/MKqEN5tY9BsVSpxT47TB" %}

***

### Step 2: Activate the Translation

Once defined, you must tell S-Sign which language to use by modifying the S-Docs button on your object.

#### Modify the S-Docs Button

1. Navigate to Setup > Object Manager and select your object (e.g., Contact).
2. Go to Buttons, Links, and Actions.
3. Find your S-Docs button and click Edit.
4. Add the `ssignParams` parameter to the button URL.

Example URL Syntax:

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

Replace `Spanish` with the exact name of the language you defined in Step 1.

<figure><img src="/files/DwHjf7S8OpP8b8LYvrup" alt=""><figcaption></figcaption></figure>

***

### Advanced: Automation & S-Docs Jobs

If you are automating signature requests via Apex or Flow using the S-Docs Job object:

* Field to Set: `SSign Language`
* Effect: Setting this field on the S-Docs Job will automatically update the `SSIGN__Language__c` field on the resulting S-Sign Envelope Document.
* Real-time Updates: You can update the `SSIGN__Language__c` field on an active Envelope record to change the Signer UI language instantly.

***

#### Summary Checklist

| **Feature**        | **Action**                                          |
| ------------------ | --------------------------------------------------- |
| Custom Language    | Define manually in S-Sign UI Translation Page       |
| Pre-built Language | Import .zip template via Template Migrator          |
| Activation         | Add `ssignParams='language:LanguageName'` to button |
| Automation         | Set `SSign Language` field on S-Docs Job record     |


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.sdocs.com/s-sign/advanced-signer-scenarios/translations.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.