This section applies to customers deploying Managed Package runtime components, regardless of whether they have an Omnistudio license. For these customers, the runtime components are added to a custom object. It also applies to customers who have an Omnistudio license and are using the standard runtime CPQ; in this case, the components are added to a standard object.
Before You Begin
-
Install or upgrade to Spring '22 or later releases. See CME Release Summary and Upgrade Guide for CME.
-
Install the Puppeteer module so that Omniscripts, Integration Procedures, and Flexcards are activated after migration. See Configure LWC Omniscript and Flexcard Activation and Compilation.
-
If you want to know which Omnistudio objects your Salesforce org is using, see Does Your Org Use Custom or Standard Objects?
Use these procedures for Spring '22 and later releases.
Both new installations and upgrades require completing these procedures. The LWC deployment can take one and a half hours or longer.
Industries CPQ in LWC doesn't support these features:
- Multi-Language Support
- Right-to-Left text
- The Collapsible Hierarchy setting. This setting is supported starting in Winter '23.
- Newport Design System
After you complete these deployment procedures, set up catalog categories and relationships so that you can use a hierarchy in the catalog for the Cart in LWC. See Create Sales Catalogs and Catalog Relationships. For multi-site, create UI containers for the group member types. See Add Multisite Custom Record Types to Industries CPQ in LWC.
- Install IDX Workbench.
- Copy Datapacks to Migrate.
- Migrate the Datapacks into Salesforce Org.
- Make the Discount Field Visible to Administrators.
- Make the Order Name and Opportunity fields Visible to Administrators.
- Turn Off Level-Based Cart Refreshing.
- Troubleshoot the Deployment for Industries CPQ in LWC.
For help with actions that don't work as expected, see Workaround for Non-Working Actions in Industries CPQ in LWC.
To create an Omnistudio component, such as an Omnistudio Data Mapper, Flexcard, Integration Procedure, or an Omniscript, see Omnistudio Naming Conventions.