Explanation:

In Salesforce Industries CPQ with Order Management (OM), when a user cancels an existing order (especially in Asset-Based Ordering (ABO) flows), a Supplemental Order is created automatically by the Order Management (OM) system.

This supplemental order is used to track adjustments made to the original order — such as cancellations, partial deletions, or changes to services or products.

The purpose of a supplemental order is to mirror the structure of the original order but reflect the delta (what’s being canceled or changed).

🔁 Key Process Flow:
A customer or user triggers a cancellation or change on an existing order.
OM recognizes this change and:

Automatically generates a Supplemental Order
Sets the Order Type to Supplemental
Initiates corresponding decomposition, fulfillment, and rollback logic if required

❌ Why other options are incorrect:

A. The same way any other order is created
🔸 No — supplemental orders are system-generated, not created manually through standard quoting.

B. Similar to a New Order, but Order Type = "Supplemental"
🔸 Misleading — you don’t set this manually; it’s automatically set by OM.

C. Automatically by CPQ when an order is canceled
🔸 Incorrect — CPQ prepares the quote/order, but OM handles cancellations and supplemental order creation.

Explanation:

Why Option B is Correct?
To discount child products within a bundle in Salesforce Industries CPQ (Vlocity CPQ), you configure discounts at the bundle’s product structure level:

Navigate to Product Workspace > Select the Parent Bundle.
Open its Product Structure (hierarchy view).
Select each child product and:
Set a percentage or fixed discount (e.g., "10% off").
Define pricing rules (e.g., "Discount applies when bundled").
This ensures discounts are automatically applied when the bundle is added to a cart.

Why Other Options Are Incorrect?

A. Price list entry → Modifies base prices, not bundle-specific child discounts.
C. Open cart → Discounts here are manual/one-time, not reusable for the bundle.
D. Order for the bundle → Orders reflect finalized prices; discounts must be set earlier.

Explanation:

In Vlocity Cart (Salesforce Industries CPQ), to change the configuration of a line item, such as modifying its:

Attributes
Pricing adjustments
Time plan
Optional add-ons or bundles
—you should use the "Configure" option available in the Actions menu for the specific cart line item.

✅ Steps:
Open the Cart (Quote Line Editor).
Find the product line item you want to modify.
Click the Actions (⋮ or dropdown) menu for that line.
Select "Configure".

This reopens the configuration UI for that specific product, allowing you to change attributes, selections, etc.

❌ Why other options are incorrect:

A. Delete and re-add the product
🔸 This works but is inefficient and not required. You can reconfigure without deleting.

C. Update the product’s attribute in Vlocity Product Console
🔸 That changes the product definition, not the individual line item instance.

D. Invoke Field Mapper
🔸 Field Mapper is used for mapping field data, not for reconfiguring cart line items.

Explanation:

In Salesforce Industries CPQ, a sales catalog defines a curated set of products and promotions that are available for selection during the quoting or ordering process. It acts as a filtering mechanism to ensure that only relevant offerings are presented to users based on context, such as customer type, market segment, or business unit.

Key characteristics:

It includes commercial products, promotions, and bundles that are actively marketed or sold.
It helps streamline the user experience by narrowing down choices to what's applicable for a given scenario.
It works in tandem with context rules to dynamically qualify or disqualify items in the cart.

Why the other options don’t apply:

A. A catalog of prices: That’s handled by price lists, not the sales catalog.
C. A catalog of technical and commercial products: That’s more aligned with the Enterprise Product Catalog (EPC), which underpins the full product model.
D. Relies On dependencies: These are part of product relationships, not catalog definitions.

Explanation:

Why Option B is Correct?

In Vlocity (Salesforce Industries) Context Rules, a rule set is a container for one or more rules, but it does not require multiple rules to be valid. Key points:

A rule set can function with just one rule.

Example: A rule set named "Premium Customer Discount" might contain only one rule checking if Account.Type = "Premium".

Adding more rules is optional (e.g., to handle additional conditions like product categories or date ranges).

Why Option A is Incorrect?

While rule sets can hold multiple rules (e.g., for complex logic), it’s not mandatory.
The system does not enforce a minimum rule count.