A company has two telesales teams: one that does business in Russian and another that does business in English. The developer decides to enable the…

For Vlocity's multi-language product catalog feature to function correctly, three core configurations must be in place. First, the system identifies the required language from the end-user's Locale setting on their Salesforce User record. Second, the desired language (Russian, in this case) must be enabled for use within Vlocity by activating it in the Vlocity Locale Code picklist. Finally, the actual translated text for the product catalog items must exist as records within the Vlocity-specific StringTranslationc object, which is linked to the corresponding product records. A failure in any of these three areas will result in the default language being displayed instead of the translation.

1. Salesforce Help

Industries CPQ

Enable and Configure Multi-Language Support for Industries CPQ: This document outlines the setup process

stating

"The language displayed in the cart is based on the user's locale setting... Before you can add translations for a language

you must activate the language in the Vlocity Locale Code picklist." This supports options A and C.

2. Salesforce Industries Communications

Media

and Energy (CME) Administrator Guide

Multi-Language Support for Product

Price

and Rule Data: This guide details the data model

specifying that "Product

price

and rule data translations are stored in the String Translation object (StringTranslationc)." This directly supports option B.

3. Salesforce Help

Industries CPQ Developer Guide

Industries CPQ Data Model for Products and Pricing: The data model reference confirms that Product2 records are linked to StringTranslationc for translatable fields and that the display logic is driven by the user's session locale

not their UI language setting. This reinforces the correctness of A and B over E.