You are here:
Multi-language Support for Shared Catalog
When communications service providers sell products in different regions, it’s important that you translate significant product details into multiple languages. Translation helps sales agents find the things they need easily by making all the relevant details, such as properties, cross-sell, or upsell suggestions, available to them in their preferred language.
A UI-driven translation of Vlocity shared product catalog data in different locales enables sales agents and applications to view product data in local languages. The shared product catalog renders translated text for products, promotions, and properties in more than 18 different locales in CPQ, based on the user profile. You can also search and sort products and promotions by translated names in CPQ.
System administrators can use the multi-language support feature to configure a default language for a specific user or one or more languages that the user can choose from as a preferred language. The user can also change the default language in the user profile. The default language appears on the UI with language-specific field labels, as well as with translated metadata and business data.
At runtime in CPQ, the customer-preferred language has higher precedence than the default user-language. Similarly, if a language code is provided as part of a URL, as in eCom, then it has a higher precedence than the default user-language.
As an example, a customer initiates an order in French, through eCom, and completes the order by contacting a call center where a CSR has English as the default language. The CSR would see the Order data in French, provided the CSR locale/language is configured for French.
CPQ and Assets display products, promotions, and properties in the base language when translations aren’t found.
With multi-language support, you can also enable users to configure the Shared Catalog objects and fields for translation. Users can determine the product data for translation based on the configured multi-language support object fields and languages. Users can then search and view the data for translation.
Vlocity supports the migration of translated product catalog data across Salesforce organizations.
You can also disable multi-language support at the organization level. After multi-language support is disabled, there’s no translation in CPQ or Asset pages.
To set up multi-language support, complete the following tasks.
Task |
Topic |
|---|---|
Enable multi-language support in Vlocity CMT Administration. |
|
Activate and deactivate the languages that you need. |
|
Set the default user language. |
|
Configure the object fields for multi-language support. |
|
Run the Create Translation job to extract product data (base language) for translation. |
|
View the extracted untranslated product data. |
|
Translate the product data. |
|
Run the Create Cache Translation Data job. |
- Configuring Multi-Language Support for Shared Catalog
You can configure the catalog to support over 25 different languages. Before applying these languages, you must configure the multi-language support feature for your shared catalog: - Modify String Translations in Vlocity Product Console
Product administrators who are responsible for product catalog administration and life cycle or contract generation configure the base language and can modify the translated strings in the Vlocity Product Console. - Set String Translations in Product Designer
Create translated text for names and descriptions for catalog entities, such as attributes, picklists, and products. The translated text is shown in the cart for the appropriate locale. You can modify the translated strings in the Vlocity Product Designer. - Translating Freeform Text Attributes
As an administrator, you can use this feature to configure freeform text attributes as either translatable or not-translatable. This enables you to specify what product attributes are translated into other languages. In previous releases, all product attributes (string data-type attributes) were translated, regardless of whether they were freeform or picklist-enabled. As of Winter '19 release, you can configure freeform string attributes to specify if the string is translatable. For example, you might not want to translate email addresses, locations, or comments in freeform string attributes. - Multi-Language Support for All Catalog Elements in CPQ
Multi-language support for Vlocity Product Catalog enables CPQ to render information in various languages. Within CPQ, the following are translated: - Migrating Translation Data Across Salesforce Orgs
CPQ can identify Vlocity and Salesforce objects and their fields used by the Shared Catalog (EPC) for values that can be translated using the UI. - Translating the Industries Cart UI
You can translate the field labels, headers, and other UI elements of the Industries Cart using a custom language file.
