Explanation:

When new product bundles are added to the Shared Catalog in Salesforce Industries CPQ, certain backend jobs must be executed to ensure the catalog is properly refreshed and the new products are visible and functional in the cart and configuration flows.

✅ B. Product Hierarchy Maintenance

This job rebuilds the product hierarchy tree, ensuring that parent-child relationships, bundles, and cardinalities are correctly structured.

It’s essential for enabling accurate product rendering and compatibility logic in the cart.

D. Refresh Platform Cache

This job updates the CPQPartition platform cache, which stores a streamlined version of the product hierarchy and attribute lists.

Running this ensures performance optimization and that the latest product data is available during configuration.

❌ Why the Other Options Are Incorrect:

A. Load API Metadata
This job is used to refresh API metadata definitions, not product catalog data.
It’s unrelated to bundle visibility or hierarchy updates.

C. EPCProductAttribJSONBatchJob
This job updates attribute metadata, but it’s not required every time a new bundle is added.
It’s typically used when attribute definitions or object types are modified.

Explanation:

The Line Item Cart pane in Vlocity Cart (Salesforce Industries CPQ) displays the key pricing and configuration details of each item added to the cart. By default, it shows:

Quantity – How many units of the product are selected.
Recurring Charge – The recurring price (e.g., monthly) of the product.
Recurring Total – Total recurring charge (e.g., quantity × recurring charge).
One Time Charge – Any one-time setup or activation fees.
One Time Total – Total one-time charge (e.g., quantity × one-time charge).

❌ Options B, C, and D are incorrect because:
B includes fields not part of the standard five (like Total Charges and Discount %).
C and D are not accurate—the cart fields are not dynamically defined per cpq-cart-setup or user preferences by default.

Explanation:

Attribute-based pricing in Vlocity CPQ (Salesforce Industries) allows pricing to be determined dynamically based on product attributes selected during configuration. The three core components involved are:

🔹 A. Pricing Plans
Define the structure and flow of how pricing is calculated.
They include steps such as loading price list entries, applying attribute-based rules, and adjustments.

🔹 B. Calculation Procedures
Used to process pricing logic, execute pricing plan steps, and return final prices.
Think of them as the engine that runs the pricing rules in real time.

🔹 D. Calculation Matrices
Store pricing values based on attribute combinations or ranges.
These are referenced in pricing plan steps to determine the correct price for given attributes.

❌ C. Overrides
Are used for manually setting prices or promotional pricing.
Not core to attribute-based pricing logic; more relevant for exception handling or promotions.

Explanation:

When a child product in a promotion has a discounted price, the explanation shown in the cart or UI comes from the:**

Display text set on the price adjustment or price override associated with that child product.

This display text communicates why a price has changed — for example, "Promo Discount" or "Special Offer Applied".

Why the others are incorrect:
A. Time policy display text relates to time-based pricing, not directly to promotions.
B. Base price display text shows standard pricing, not adjusted/discounted pricing.
D. Promotion description might appear elsewhere (e.g., marketing UI), but not directly tied to price explanation.
E. Promotion code is used for identification or entry, not explanation.

Explanation:

To ensure that the persistent cart (vlcCart) is created in the correct node within the data JSON structure, you need to properly define where it should reside during runtime. This is critical for maintaining cart state across Guided Selling flows and ensuring the cart behaves as expected.

✅ B. Specify “vlcPersistentComponent” in the Response JSON Node properly

This configuration tells the system where to place the vlcCart node in the JSON hierarchy.

By specifying "vlcPersistentComponent" correctly in the Response JSON Node, you ensure that the cart is persistently stored and accessible across OmniScript steps.

It’s the recommended and declarative approach for managing persistent cart placement.

❌ Why the Other Options Are Incorrect:

A. Check the Show Persistent Cart property
This controls visibility, not placement in the JSON structure.

C. Drag the vlcCart node manually in the JSON editor
While this might work temporarily, it’s not reliable or scalable. Manual edits can be overwritten or misaligned with runtime behavior.

D. Check the Render property
This affects UI rendering, not the data structure or persistence logic.