> For the complete documentation index, see [llms.txt](https://university.gonexa.fr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://university.gonexa.fr/doc/en/advanced-features/translation-template/prepare-translations-in-salesforce.md). # Prepare translations in Salesforce From Setup, go to "Translation Language Settings" and click the "Enable" button ## Enable translations in Salesforce * From Setup, go to "Translation Language Settings" and click the "Enable" button * Activate the source language, such as French, by clicking Edit and checking "Active" * Add your user to the list of Translators * Do the same for all the languages to translate, and save ## Translate the data in Salesforce * From Setup, go to "Translate" * Select the language to translate, such as English, and the setup component to translate, such as "Picklist Value" * In the translation column of the selected language, enter the matching label in the target language. Produit > Product * Do the same for the default language, with a similar mapping. Produit > Produit --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://university.gonexa.fr/doc/en/advanced-features/translation-template/prepare-translations-in-salesforce.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.