Configure localization settings to generate documents with translated content and
locale-specific formatting. Control localization at the document generation request level and
refine behavior at the field level.
Required Editions
Available in: Lightning Experience
Available in: Professional, Enterprise, Unlimited, and
Developer Editions
User Permissions Needed
To configure localization for document generation:
Configure the translations tab to translate your data.
Open the record you want to translate.
Click the Translations tab, and then click Add
Translations.
Select a language.
Enter the translated values for the supported fields.
Save your changes.
To turn on localization for contract flows.
From Setup, in the Quick Find box, enter Contract Type Config, and
then select Contract Type Config.
Set the LocalizedEnabled field to Yes.
Save your changes.
To control field-level localization.
Open a context definition.
Select the field that you want to configure.
Select Keep Localization to use translated values for the field,
or clear it to use the original org value.
Save your changes.
To turn on localization for direct document generation.
Create or update the Document Generation Process record.
Set the Localized Enabled field to true in the request.
Run document generation.
To turn on localization in Omniscript.
In the document generation step, add an element value to
SetGenerationServiceInputParams.
Enter IsLocalizationEnabled as the parameter name and True as the
value.
This parameter isn’t available in the UI. Configure it in the request.
Løste denne artikel dit problem?
Giv os besked, så vi kan forbedre os!
Indlæser
Salesforce Help | Article
Cookie Consent Manager
Cookie Consent Manager
General Information
Required Cookies
Functional Cookies
Advertising Cookies
General Information
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.