Explanation:

To hide products based on a Configuration Attribute (like "Perpetual"), you need a Product Rule. The Error Condition checks the Product Family on Product Options, and the Product Action uses the Filter Field to hide products that match that condition (e.g., Product Family = Software).

Explanation:

Calculation Breakdown:

Given:
List Price (per unit): $100
Quantity: 5
Discount Schedule Type: Slab (tiered discount)
Discount Unit: Percent

Assumption:

Explanation:

Salesforce CPQ follows a specific hierarchy for applying Discount Schedules to a Quote Line. This precedence ensures that the most specific discount is applied, overriding more general ones. The hierarchy is as follows, from highest precedence to lowest:

Contracted Price: A discount schedule linked to a Contracted Price record on the account is the highest priority. It applies a negotiated, account-specific discount.
Price Dimension (MDQ): This applies to multi-dimensional products.
Product Option: A discount schedule linked to a specific Product Option in a bundle takes precedence.
Product Feature: A discount schedule linked to a Product Feature within a bundle.
Product: A discount schedule on the base Product record has the lowest precedence.

Therefore, both a Contracted Price and a Product Option can have a Discount Schedule that takes precedence over one identified in a Product Feature.

Explanation:

Scenario:

Universal Containers wants to update the Quantity of a Product in the Line Editor with a Price Rule. The rule should apply only for this one specific Product.

Key concept:

Price Rules don’t directly “belong” to a single product. Instead:
Price Rules operate on Quote Lines.
To target only a specific product, you need to define conditions that uniquely identify it.

✅ How To Target A Single Product

The correct way to ensure the Price Rule fires only for one specific product:

Create a Price Condition that:
1. Object → Quote Line
2. Tested Field → Product Code or Product Name or ProductId (or any field uniquely identifying the product)
3. Operator → Equals
4. Filter Value → unique value identifying the product

Example:

Object: Quote Line
Tested Field: SBQQ__ProductCode__c
Operator: Equals
Filter Type: Value
Filter Value: YOUR_UNIQUE_PRODUCT_CODE

This ensures the Price Rule only applies to lines referencing that product.

Why Not The Other Options?

B. Create an Error Condition…
🚫 Wrong. Error Conditions are for Validation Rules to prevent certain behavior, not to trigger a Price Rule’s action.

C. Fill in the Product field on the Price Rule with the Product.
🚫 Wrong. The Price Rule object has no standard “Product” field for scoping a rule to a specific product. It’s not how Price Rules work.

D. Fill in the Lookup Object field on the Price Rule with the Product.
🚫 Wrong. The Lookup Object field on Price Rule indicates what object the rule is updating (e.g. Quote Line), not which Product it applies to.

Explanation:

Scenario Breakdown:

Users want to preview approval routing (who will approve the Quote) before submitting it.
This is a standard feature in Advanced Approvals (not native Salesforce approvals).

Why Option B is Correct?

Advanced Approvals provides a Preview Approval button that:
1. Displays the full approval chain (approvers, steps, conditions).
2. Requires no code (just add the button to the Quote page layout).