Explanation:

In Salesforce Industries CPQ, the Recurring Total and One Time Total prices shown in the Cart Line Items pane are dynamically calculated based on:

Base Price from the Price List Entry
Active Pricing Rules (e.g., attribute-based pricing, context rules)
Promotions and Discounts (manual or automated)
Bundle roll-ups (for child products)
Quantity multipliers

These totals reflect the final computed price after all applicable adjustments have been applied. The system uses the Price Waterfall model to layer pricing logic, ensuring transparency and traceability.

Explanation:

In Vlocity Enterprise Product Catalog (EPC), Picklist Entities are designed to be globally reusable across products and attributes. They can be managed in two ways:

Vlocity Product Console:
Admin-friendly UI for creating/modifying picklists (e.g., for colors, sizes).
Path: Product Console > Picklist Entities.

Salesforce Setup:
Standard Salesforce picklist management (e.g., Setup > Object Manager > Picklist Value Sets).

Key Benefits of Global Reusability:
Ensures consistency (e.g., "Small/Medium/Large" options standardized across all products).
Reduces duplicate picklist creation.

Why Option B is Incorrect?
The statement is true because picklist entities are centralized and editable in both interfaces.

Explanation:

To dynamically include or exclude picklist values for a product attribute based on the value of another attribute, developers use Product Configuration Procedures in Salesforce Industries CPQ. This functionality is part of the Modify Attributes action type within advanced rules.

✅ C. Product configuration procedures
These allow developers to define attribute constraints using JSON-based action parameters.
You can specify which picklist values to include or exclude based on conditions tied to other attributes.
The procedure generates the JSON needed to modify the attribute behavior, which is then used in a product relationship and linked to an advanced rule.

📌 Example: If a customer selects a product like Business Video Service, and it requires a high-speed connection, you can use a configuration procedure to exclude lower-speed options (e.g., 10 Mbps, 55 Mbps) from the Download Speed attribute of the Broadband Cable Service product.

❌ Why the other options are incorrect:

A. Attribute metadata: Controls static attribute behavior (e.g., data type, default values), not dynamic filtering.
B. Object types: Define structural relationships, not attribute-level logic.
D. Context rules framework: Used for broader eligibility and qualification logic, not fine-grained picklist value control.

Explanation:

In Salesforce Industries CPQ (Vlocity), when the Base Price checkbox is selected on a Price List Entry (PLE), it means:

🔹 That price will be used as the starting (initial) price when the product is added to the cart.

✅ Details:
Base Price is the foundational price before any discounts, adjustments, or overrides.
It is what the system uses to:

Calculate discounts or promotional pricing
Display default pricing in the Cart
Feed pricing logic (like adjustments or penalties)

❌ Why the other options are incorrect:

A. The display text...
🔸 The display text comes from the product's settings and context, not just the base price flag.

C. No context rules can be associated...
🔸 Context rules can still apply to products with base pricing; this setting does not prevent rule application.
D. Used to determine the cost basis

🔸 Cost basis is a different pricing concept (usually used for margin calculations), and not the same as base price.

Explanation:

In Salesforce Industries CPQ, the linkage between a Document Template and objects like Opportunity, Quote, or Order is controlled via the Applicable Objects setting within the Template Settings section of the Document Template record.

✅ B. Applicable Objects in Template Settings
This field defines which Salesforce standard or custom objects the template can be used with.
Common values include:

Opportunity
Quote
Order

When generating a document, the system checks this field to determine whether the template is valid for the current object context.

❌ Why the other options are incorrect:

A. PDF Document Template custom setting
This is not a standard mechanism for linking templates to objects.
Custom settings may control behavior or defaults, but not object applicability.

C. Applicable Item Types in Template Settings
This controls which line item types (e.g., products, services) the template supports — not the parent object like Opportunity or Quote.

D. Document Template object picklist
There is no picklist on the Document Template object that directly links it to Opportunity, Quote, or Order.

Object applicability is managed through the Applicable Objects field.