Explanation:

In the Vlocity Product Console (part of Salesforce Industries CPQ), the "Object" entity is pre-defined and managed by the package, which means:

You can search and edit existing EPC metadata objects.
But you cannot create new custom EPC objects from within the Product Console.

As stated in the official documentation:

“There is no new icon next to Object because the Vlocity Product Console does not allow the creation of custom EPC or CPQ objects. The objects in Vlocity Product Console are created during installation and are part of the managed package.”

So the statement:
"Vlocity Product Console does not support the creation of custom EPC objects."

is indeed True.
Let me know if you'd like guidance on customizing layouts or metadata via supported methods!

Explanation:
To allow users to modify an attribute in the Cart’s configuration window, the developer must enable the Run-time Configurable property on that attribute. This setting ensures the attribute appears in the cart interface and is editable during runtime.

When enabled:
- The attribute becomes visible and interactive
- Users can change its value during cart configuration
- It supports dynamic logic like pricing updates and rule triggers

Why other options are incorrect:
Active property: Indicates whether the attribute is active in the system but doesn’t control cart visibility or editability.
Not Hidden property: Affects visibility but doesn’t guarantee the attribute can be modified—it may still be read-only.
Filterable property: Applies to Guided Selling filters and product searches, not cart attribute configuration.

Explanation:

In the Industries CPQ Cart (formerly Vlocity Cart), when there’s a configuration error or missing required information on a product in the cart, the UI provides a “Take Me There” icon or link.

When clicked:
It jumps directly to the Line Item Detail modal for that product.
It highlights missing fields or required attributes that need the user’s attention.
This helps users quickly locate and fix configuration errors without manually searching through all cart items.

This behavior ensures a smooth user experience and helps users achieve a Perfect Order.

Why not the other options?
A. Returns the user to the Order Detail page to correct configuration errors
→ Incorrect. The icon is about fixing items inside the cart, not navigating to the order record.

C. Takes the user to the Product Catalog
→ Incorrect. That’s unrelated to the error resolution flow.

D. Opens the Price List associated with the cart line items
→ Incorrect. The price list is not opened by the “Take Me There” icon.

Explanation:

Role of Rules in Salesforce CPQ/Vlocity:

Validation Rules: Prevent users from submitting orders with:
Missing required attributes (e.g., "Warranty not selected").
Invalid configurations (e.g., incompatible products).
Pricing errors (e.g., discounts exceeding limits).

Eligibility/Compatibility Rules: Ensure only valid products are added to the cart.

Why "True"?

Rules act as guardrails by:
Blocking submission until errors are fixed.
Displaying error messages (e.g., "Select a service tier before submitting").

Reference: Salesforce CPQ Validation Rules

Example:
A rule might enforce: "If Product A requires Product B, reject the order if B is missing."

Key Takeaway:
Rules automatically enforce accuracy in orders.

Explanation:

In Salesforce Industries CPQ (formerly Vlocity), the Submit Order button in the Cart does not directly run the CPQ APIs by itself. Instead, it:

Invokes an OmniScript.

That OmniScript:

1.Calls CPQ APIs
To create order and order line items
To generate asset records based on the products in the order
To activate the order (change status to Activated)

2.Performs additional custom logic if needed, such as:
Billing info collection
Payment processing
Generating order confirmations

3.Handles navigation
Typically redirects the user to the Account, Order Detail page, or a confirmation page

This architecture allows Salesforce Industries CPQ to remain flexible and customizable for different customers’ order management flows.

Why not the other options?
A. Invokes the CPQ API directly
→ Incorrect. The Cart does not directly call APIs. Instead, it triggers an OmniScript.

C. Invokes a Flow
→ Incorrect. Standard Flows are not the default method for order submission in Industries CPQ—it’s handled through OmniScripts.

D. Invokes an OmniScript to complete the order process and collect billing information
→ Partially correct because OmniScript might collect billing info—but the core piece missing here is that it also calls CPQ APIs to create assets and activate the order. Option B is the full and precise answer.

Explanation:

1.Adjustments in Salesforce CPQ/Vlocity:

Adjustments are dynamic modifications to pricing, including:
Discounts (e.g., "$50 off" or "20% off").
Temporary promotions (e.g., "20% off for 3 months").
Markups or surcharges.

2.Why Options B & C?
B. $50 off: A fixed-amount discount (classic adjustment).
C. 20% off for 3 months: A time-bound percentage discount (common for promotions).

Reference: Salesforce CPQ Price Adjustments

Why Not A & D?
A. $12 price on employee price list: A fixed price override (set in a price list, not a runtime adjustment).

D. $35 recurring monthly price for B2C: A segmented price (defined in price lists or contracts).

Key Takeaway:
Adjustments = Dynamic price changes (discounts/promos). Fixed prices = Predefined in price lists or contracts.

Explanation:

In Salesforce Industries CPQ (Vlocity), you can assign multiple context rule sets to a single promotion. This flexibility allows developers to layer different qualification criteria—such as geography, account type, or product eligibility—into a promotion’s logic.

Each rule set can contain one or more context rules, and promotions can evaluate all assigned rule sets during runtime to determine whether the promotion should be qualified or disqualified for a given customer.

This modular approach makes it easier to:
Reuse rule sets across multiple promotions
Combine eligibility logic from different business domains
Maintain cleaner and more scalable rule configurations

Explanation:

In Vlocity (Salesforce Industries CPQ), context mappings link context dimensions (like “Country,” “Segment,” or “Sales Channel”) to the actual fields on Salesforce objects (such as Quote, Order, Account, etc.) that hold the real data used in context rule evaluation.

You can configure context mappings from either of two places:

✅ From the Context Dimension
You can open the dimension (e.g., “Country”) and define which objects and fields it maps to.

Example:
Dimension: Country
Maps to: Quote.Country__c

✅ From the Context Scope
You can open a context scope (e.g., Quote) and define which context dimensions it includes and how they map to fields.

Example:
Scope: Quote
Dimension mapping:
Country → Quote.Country__c
Segment → Quote.Segment__c

So the statement:
“Context mappings can be configured from the context dimension or the context scope.”
is True.

Explanation:

When the Cost & Margin feature is enabled in Salesforce Industries CPQ, the upper and lower margin bounds are stored in a calculation matrix. This matrix is referenced by a calculation procedure, which evaluates whether the margin on a cart line item falls within the acceptable range.

If the margin is outside the defined bounds, the CPQ Cart can trigger an error or warning, helping enforce pricing governance and profitability controls.

For example:
If the lower bound is set to 5%, and a product is priced with a 4% margin, the cart will flag it as invalid.

These bounds are defined as variables in the matrix and can be tailored per product, usage type, or customer segment.

❌ Why the other options are incorrect:
B. Margin attribute: Attributes are used for configuration and display, not for storing margin thresholds.
C. Cost price list entry: Cost entries define base cost, not margin bounds.
D. Price list: Price lists define base and recurring prices, not margin enforcement logic.

Explanation:

In Salesforce Industries CPQ:
The Guided Selling cart is powered by APIs that read, write, and update data in the cart.
To update items already in the cart (e.g. quantity, attributes, selections), you must send data back to the server so it can persist the changes.

That’s precisely what the putCartsItems API does:
putCartsItems → Used to update existing items in the cart.
Updates quantities
Changes attribute values
Modifies selections

Without calling putCartsItems, the changes remain only in the client session and will not persist.

Why not the other options?
A. done
Not a valid API name.

B. vlcCart
This is a front-end object, not an API call to update data.

C. CpqAppHandler
It’s an Apex class, not the specific cart update call.

D. createCart
Creates a new cart—not for updating items.

E. getCartsItems
Reads data from the cart but does not update it.

F. getCartsProducts
Fetches available products, not updating items.

H. postCartsItems
Typically used for adding new items rather than updating existing ones.

I. checkout
Used at the end of the process to finalize the order.

J. submit
Submits the order—not used for in-session updates of items.

Explanation:

Price Details Window in Salesforce CPQ/Vlocity:

This window shows a breakdown of how a line item’s price is calculated, including:
Base Price: Original price from the price list.
Adjustments: Discounts, markups, or promotions (e.g., "$50 off").
Overrides: Manual price changes (e.g., sales rep edits).

Why Options B & C?
B. Pricing Adjustment:
Explicitly lists discounts/promotions (e.g., "20% Summer Sale").

C. Pricing Override:
Shows manual price changes (e.g., "Overridden Price: $90").

Reference: Salesforce CPQ Price Details

Why Not Other Options?
A (Base Price): Doesn’t reflect adjustments (it’s the pre-discount price).
D (Product Description): Unrelated to pricing logic.
E (Price List): Only shows the source, not applied adjustments.

Explanation:

In Salesforce Industries CPQ (formerly Vlocity):

Price Lists are the primary mechanism for storing prices for products.
Each Price List can define a base price for the same product, but potentially for:

Different customer segments
Different sales channels
Different regions or geographies
Different contract terms

This allows you to assign multiple base prices to the same product by placing it in multiple price lists. For example:

Employee Price List → $15 for Product X
Retail Price List → $25 for Product X
Wholesale Price List → $10 for Product X

Hence, statement A is correct.

Why not the other options?
B. You don’t need the Salesforce price book.
❌ Incorrect. While Salesforce Industries CPQ uses its own price lists in the EPC (Enterprise Product Catalog), integration with the Salesforce price book is still often required for Order Management and other core Salesforce objects. The price book isn’t simply “not needed.”

C. You can ignore affectivity time frames.
❌ Incorrect. Affectivity (valid-from and valid-to dates) remains critical even when using multiple price lists. It controls:

When a price is valid
Seasonal or promotional pricing

You cannot ignore affectivity—it’s fundamental to pricing logic.