CPQ-Specialist Salesforce Certified CPQ Specialist (WI25) Question and Answers

ï‚· Requirement:

Users must view and select product options by scrolling on a single page.

ï‚· Solution Details:

Setting the Option Layout to Sections groups options into expandable/collapsible sections.

This creates a scrollable view without navigating multiple pages.

ï‚· Steps to Update:

Go to the parent Product Record.

Update the Option Layout field to Sections.

 Validation:Test the configuration in the Quote Line Editor. Options should now appear grouped by sections​​.

ï‚· Requirement Overview:

A product must be priced as 10% of the total fixed-priced products on the Quote.

ï‚· Solution Details:

Option A:

Setting the Pricing Method to Percent of Total ensures the price is calculated as a percentage of the total value of other products.

The Subscription Pricing is left blank since it is not a subscription product.

Option D:

Set the Pricing Method to List and Subscription Pricing to Percent of Total to achieve the same result with flexibility for subscription-based products.

ï‚· Requirement Overview:

Admin needs to enable Additional Discounts at both the Quote and Group levels in the Line Editor.

ï‚· Solution Steps:

For the Quote Object:

Navigate to Setup > Object Manager > Quote.

Locate the Line Editor Field Set.

Add the Additional Disc. (%) field to the field set.

For the Quote Line Group Object:

Navigate to Setup > Object Manager > Quote Line Group.

Locate the Line Editor Field Set.

Add the Additional Disc. (%) field to the field set.

ï‚· Testing:

Open the Quote Line Editor and confirm the visibility of the Additional Discount fields at both levels.

Background Context:When amending a contract in Salesforce CPQ, issues with net pricing arise if the amendment impacts existing subscription products. Subscription products often rely on Discount Schedules for calculating discounts, especially when quantity changes. The "Cross Order" field on Discount Schedules ensures discounts account for cumulative quantities across multiple orders or contracts.

Problem Analysis:

The reported issue involves incorrect net pricing specifically when the quantity of existing products is adjusted during contract amendments.

This aligns with the functionality of Discount Schedules, where the total quantity determines the discount applied. Without "Cross Order" enabled, Salesforce CPQ considers only the current order's quantities rather than aggregating across orders.

Root Cause Identification:

Discount Schedule and Cross Order:If the Discount Schedule associated with these products does not have "Cross Order" enabled, any amendments won't consider cumulative quantities. Instead, the system recalculates based on only the new or adjusted quantities, leading to incorrect net pricing.

Supporting Evidence:

Salesforce documentation highlights that Cross Order must be selected in the Discount Schedule for accurate discount calculations across multiple orders or contracts. Otherwise, amendments operate in isolation​​.

The feature ensures that ongoing contracts retain accurate pricing based on total historical quantities.

Recommended Resolution:

Navigate to the Discount Schedule associated with the affected products.

Verify and enable the Cross Order checkbox:

Go to Setup > Discount Schedules.

Locate the relevant Discount Schedule.

Edit the schedule and enable Cross Order.

Test the functionality by amending the contract and verifying the net pricing calculations.

Preventative Actions:

For all subscription-based products relying on Discount Schedules, ensure Cross Order is enabled during initial configuration.

Provide training to Salesforce CPQ admins to understand the implications of Discount Schedule settings on pricing.

By following these steps and verifying the Discount Schedule configuration, the issue can be resolved, ensuring consistent and accurate net pricing during contract amendments.

ï‚· Requirement:

Ensure the Support SKU is available only in USD and EUR.

ï‚· Expected Behavior:

USD: The product is available and uses the Pricebook Entry's List Price.

EUR: The product is available and uses the Pricebook Entry's List Price.

GBP: The product is unavailable due to the absence of a Pricebook Entry in GBP.

ï‚· Why Other Options Are Incorrect:

A & D: These imply product unavailability in all currencies, which contradicts the configuration.

B: GBP would not add the product with a zero List Price due to Pricebook Entry restrictions.

ï‚· Salesforce CPQ Reference:

Multi-currency behavior and product availability are documented under CPQ Pricing and Product Management ​.

In Salesforce CPQ, when search filters are configured with predefined values and visible to sales reps, their interaction with the filter is determined by the filter’s configuration and available operators. The behavior described here is tied to Search Filters in the Product Selection screen, which allow users to refine the list of displayed products based on specific criteria.

Search Filter Configuration:

Predefined Filter Value: Here, the filter is set with a value ("Green").

Operator: The operator “starts with” limits the search to product codes beginning with the text "Green."

Sales Rep Interaction with the Filter:

The visibility of the search filter enables sales reps to view and interact with the criteria during product selection.

Specifically, sales reps have the ability to delete the predefined text to ignore the filter and retrieve a broader or unrestricted product list.

Documentation Alignment:According to Salesforce CPQ guidelines (as referenced in the Salesforce CPQ package settings and user behaviors), if filters are not marked as "required," users can remove or modify the filter values dynamically. This is designed to offer flexibility during quoting while maintaining filter defaults for ease of use.

The interaction described above aligns with Salesforce CPQ's behavior regarding visible search filters, emphasizing that sales reps can clear the filter text unless restricted by additional customization.

Use Case Reference:

When a sales rep begins a quote and searches for products, the filter defaults to "Green."

If the rep does not want to limit the product search to codes starting with "Green," they can simply remove the text and refresh the results.

Relevant Salesforce CPQ References:

Search Filters in the Quote Line Editor section of CPQ documentation .

Guidelines for Search Filter Configuration and behaviors when visible filters are not required .

ï‚· Dynamic SKU Generation:

A dynamic SKU is created based on user choices during the configuration process. This requires fields that define patterns and positions for combining components into a single SKU.

ï‚· Required Fields:

Component Code Position: Determines the position of each component in the SKU.

Component Code: Represents individual product codes that contribute to the SKU.

Configured Code Pattern: Defines the overall pattern of the dynamically generated SKU.

ï‚· Salesforce CPQ Reference:

Dynamic SKU creation is described under Configuration and Product Bundling Guidelines ​.

ï‚· Requirement:

Amend an active contract and adjust prices for subscriptions and assets based on new discounts.

ï‚· Solution:

Use the Amend Contract process.

Adjust prices for subscriptions or assets directly by modifying the Net Price or Price field.

Use the Refresh Prices button to apply changes to the amended contract.

ï‚· Why Other Options are Incorrect:

A: Cloning Quote Lines is unnecessary and inefficient for contract amendments.

B: Changing the contract status to Draft is not supported in standard CPQ.

D: Creating a new Price Book is not required for this use case.

ï‚· Salesforce CPQ Reference:

The Amendments Process is extensively documented in CPQ Subscription Management ​.

ï‚· Requirement:

Sales reps need to identify Product Options linked to Quote Lines in the Quote Line Editor.

ï‚· Solution:

Enabling Visualize Product Hierarchy organizes Quote Lines based on their position within the bundle, displaying the parent-child relationship.

ï‚· Why Other Options Are Incorrect:

A: The Product Option Drawer enables detail viewing but does not organize Quote Lines.

B: Preserve Bundle Structure applies to output documents, not the Line Editor.

D: Keep Bundle Together affects grouping but not hierarchy visualization.

ï‚· Salesforce CPQ Reference:

Hierarchy settings are covered in the Quote Line Editor Configuration documentation ​.

ï‚· Issue:

Prices are hidden on the Configure Products page due to restricted field visibility.

ï‚· Solution:

Adjust the Field-Level Security settings for the Unit Price field on the Product Option object to ensure visibility.

ï‚· Why Other Options Are Incorrect:

B: The Option Configuration Field Set affects configuration but does not control visibility.

C & D: Default Pricing Table and Price Editable settings do not impact visibility on the Configure Products page.

ï‚· Salesforce CPQ Reference:

Managing field visibility is outlined in CPQ Field-Level Security documentation ​.

ï‚· Requirement:

Render separate Line Item sections for each Product Family and bundle on the output document.

ï‚· Solution Steps:

Option B: Create a Line Item section for each Product Family and use the Filter field to display only the relevant products for each section.

Option C: Use a formula field on the Quote Line object to identify the bundle's Name and Number, then set this field in the Group field to group lines within each section.

ï‚· Why Other Options Are Incorrect:

A: The Conditional Print field is not used for rendering specific Product Families in Line Item sections.

D: Sort Order on Product records does not meet the grouping and filtering requirements for the output document.

ï‚· Salesforce CPQ Reference:

Document generation and Line Item grouping are detailed in Quote Templates Configuration ​.

ï‚· Requirement Overview:

Restrict sales reps to only selecting subscription Products when using the Add Subscriptions Custom Action.

ï‚· Solution Details:

The Search Filter for the Add Subscriptions action should include only subscription Products.

Setting the Filter Value to Hidden ensures that only Products matching the filter criteria are displayed.

ï‚· Steps to Configure:

Navigate to the Search Filter related to the Add Subscriptions action.

Set the Filter Value to True.

Mark the Hidden checkbox to restrict visibility to subscription Products.

ï‚· Validation:

Test the Custom Action to confirm that only subscription Products are visible.

ï‚· Requirement Overview:

Adjust the List Price dynamically based on the geographic area using a custom Price Multiplier stored in a custom object.

ï‚· Solution Details:

Custom List Unit Price Field: Store the adjusted List Price for the specific geographic area.

Lookup Price Rule: Retrieve the multiplier from the custom object and calculate the adjusted List Price.

ï‚· Steps to Configure:

Create a Custom Field (e.g., Custom List Unit Price) on the Quote Line.

Create a Lookup Price Rule to:

Retrieve the Price Multiplier from the custom object.

Calculate and populate the custom List Unit Price field.

ï‚· Validation:

Generate a Quote and confirm the List Price reflects the appropriate multiplier for the geographic area.

ï‚· Issue Context:

Not all Quote Lines are generating Opportunity Product records during the Amendment process.

ï‚· Possible Causes:

A. Net Total = 0:

Salesforce CPQ does not create Opportunity Products for Quote Lines with a Net Total of zero.

D. Exclude from Opportunity:

If the Product has the Exclude from Opportunity checkbox set to TRUE, it prevents Opportunity Product creation.

ï‚· Steps to Investigate:

Verify the Net Total of the Quote Lines.

Check the Product configuration for the Exclude from Opportunity setting.

ï‚· Validation:

Update the relevant fields and test the Amendment process to ensure all eligible Quote Lines generate Opportunity Products.

ï‚· Requirement Overview:

A nonrenewable subscription Product priced annually.

ï‚· Key Field Configurations:

Subscription Term = 12: Specifies an annual subscription.

Subscription Type = One-Time: Indicates that the Product is nonrenewable.

Subscription Pricing = Fixed Price: Defines a flat annual price.

ï‚· Steps to Configure:

Navigate to the Product record.

Update the fields as specified above.

Save and test by adding the Product to a Quote.

ï‚· Validation:

Confirm the subscription term and pricing are applied correctly and the product does not renew automatically.

ï‚· Considerations for Authorizing Calculation Service:

The Calculation Service must be authorized by a user who has sufficient privileges and stable permissions.

ï‚· Solution Steps:

Option B: Use a non-human admin user (e.g., an integration user) to authorize the Calculation Service. This ensures consistent access and avoids disruptions due to personnel changes.

Option C: Place the user at the top of the Role Hierarchy to ensure full visibility and access across relevant objects.

ï‚· Salesforce CPQ Reference:

Proper user configuration for the Calculation Service is outlined in the CPQ Authorization Guidelines ​.

ï‚· Requirement Overview:

Universal Containers wants to aggregate the quantities of all Product Options in Feature A to determine the Discount Tier.

ï‚· Key Configuration:

Assign the Discount Schedule to the Product Feature itself.

Enable the Cross Orders checkbox to aggregate quantities across multiple orders or contracts.

ï‚· Steps to Configure:

Navigate to the Product Feature record for Feature A.

Set the Discount Schedule field to the appropriate Discount Schedule.

On the Discount Schedule, check the Cross Orders box.

ï‚· Validation:

Add multiple Product Options from Feature A to a Quote and verify that their quantities are aggregated for discount calculation.

ï‚· Requirement:

Calculate the prorate multiplier when a subscription product’s End Date differs from the Quote’s End Date.

ï‚· Solution:

CPQ uses the Quote Line date (specific to the subscription product) to calculate the prorate multiplier. This ensures alignment with the subscription term.

ï‚· Why Other Options Are Incorrect:

A & D: Earliest or latest dates do not determine prorate multipliers.

B: The Quote date applies to the Quote as a whole, not individual subscription products.

ï‚· Salesforce CPQ Reference:

Prorate multiplier calculations are outlined in Subscription Management Guidelines ​.

The order of precedence for evaluating subscription dates is as follows

(1) Quote Line,

(2) Quote Line Group, and

(3) Quote

https://help.salesforce.com/s/articleView?id=000383503 &type=1

ï‚· Requirement:

Organize quoted products by project milestones and generate a separate Order for each Quote Line Group.

ï‚· Solution:

Use Salesforce automation to set the Order by Quote Line Group field on the Quote. This ensures the system generates separate Orders based on the grouping in the Quote Line Editor.

ï‚· Why Other Options Are Incorrect:

B: Relying on notes is manual and error-prone, lacking automation for generating separate Orders.

C: Validation Rules prevent specific actions but do not help organize Orders by Quote Line Group.

D: Custom picklist fields are unnecessary when Order by Quote Line Group exists as a standard feature.

ï‚· Salesforce CPQ Reference:

The Order by Quote Line Group feature is outlined in Order Management Configuration ​.

ï‚· Requirement:

Ensure the correct Distributor Discount is applied to Quote Lines based on the distributor's Discount_Level__c field value.

ï‚· Solution:

Configurator Scoped Price Rule:

A Price Condition checks whether the SBQQ__Quote__r.Distributor__c field is populated.

If the field is blank, the rule does not execute.

Price Action:

Injects the value of the Discount_Level__c field from the Distributor account into the Quote Line's SBQQ__DistributorDiscount__c field.

ï‚· Why Option A is Correct:

Configurator Scope ensures the rule is evaluated during configuration, applying discounts dynamically as the Quote is edited.

ï‚· Why Option B is Incorrect:

Calculator Scoped Price Rules execute during calculations (not configuration), which may result in delayed discount updates.

ï‚· Salesforce CPQ Reference:

Price Rules and their scopes are documented in the CPQ Pricing Logic Configuration ​.

ï‚· Scenario Breakdown:

Product A has a base list price of $100.

A quantity of 15 is entered on the quote.

Gold Hardware Maintenance Discount applies because contracted pricing is enabled.

Discount for the quantity range (11–20) is 15% (as shown in the table).

ï‚· Net Price Calculation:

List Price = $100

Discount = 15%

Quantity = 15

Net Total Price = $100 × 15 × (1 - 0.15) = $1,275.

ï‚· Justification for Selected Discount:According to Salesforce CPQ guidelines, when contracted pricing applies, it takes precedence over other Discount Schedules. The Gold Discount Schedule is therefore applied.

ï‚· Testing and Validation:Test the configuration using a sample quote to ensure the correct schedule is applied and the net total price matches the expected value.

ï‚· Requirement:

Ensure a Product Rule fires only within a specific bundle.

ï‚· Solution:

Associating the Configuration Rule with the Parent Product ensures that the rule executes only during configuration of the specified bundle.

ï‚· Why Other Options Are Incorrect:

A, B, C: Associating the rule with Product records, Features, or Options does not scope the rule specifically to the parent bundle.

ï‚· Salesforce CPQ Reference:

Configuration Rules and their association with Parent Products are documented in CPQ Configuration Rule Guidelines ​.

ï‚· Requirement:

Allow users to generate output documents in Microsoft Word format.

ï‚· Solution:

The Allow Output Format Change checkbox in User Settings enables users to select alternative formats like Microsoft Word during document generation.

ï‚· Why Other Options Are Incorrect:

A: The checkbox is user-specific, not template-specific.

C: Creating a second template is unnecessary when users can dynamically change the format.

D: Template Sections do not control output formats.

ï‚· Salesforce CPQ Reference:

Configuring user settings for document generation is detailed in CPQ Quote Templates Documentation ​.

ï‚· Requirement:

Ensure that custom field data from original Quote Lines flows into Renewal Quote Lines.

ï‚· Solution:

Use twin fields on the Asset and Subscription objects to store and transfer data. Twin fields are automatically mapped during renewal processes, ensuring data flows seamlessly.

ï‚· Why Other Options Are Incorrect:

A: A formula field cannot persist data on Renewal Quotes.

B: Automatic mapping does not apply to custom fields without twin fields.

C: A Price Rule is unnecessary when twin fields handle this data flow.

ï‚· Salesforce CPQ Reference:

Twin fields and their functionality are described in CPQ Subscription Management ​.

ï‚· Subscription Product Configuration:

Product B uses the Percent of Total pricing model based on Product A's Net Price.

Product B's Percent of Total Base is set to "Net," and its Percent of Total Target is set to Product A.

Product B's Percent of Total (%) is configured as 10%.

ï‚· Calculation:

Product A Net Total = $2,400

Product B Net Total = 10% of Product A Net Total = 2,400×0.1=2402,400 \times 0.1 = 2402,400×0.1=240.

ï‚· Salesforce CPQ Reference:

Percent of Total pricing logic is described under Percent of Total Products ​.

Universal Containers requires a dynamic approach to display the Monthly Price column on the Quote Document only when the Payment Terms field is set to "Net 30". Here's how to achieve this:

Step 1: Create a Monthly Price Line Column

Navigate to Quote Templates in Salesforce CPQ.

Select the relevant Quote Template.

In the Line Columns related list:

Create a new Line Column for "Monthly Price."

Configure the desired settings for how the Monthly Price should display in the PDF.

Step 2: Create a Custom Formula Field

Navigate to Setup > Object Manager > Quote.

Create a custom formula field (e.g., Show_Monthly_Price) on the Quote object:

Type: Formula (Checkbox).

Formula Logic: IF(Payment_Terms__c = "Net 30", TRUE, FALSE).

Replace Payment_Terms__c with the API name of the Payment Terms field.

This formula ensures the field returns TRUE only when Payment Terms equals "Net 30."

Step 3: Configure Conditional Print Field on the Line Column

Return to the Quote Template and edit the Monthly Price Line Column.

Set the Conditional Print Field to Show_Monthly_Price.

This links the visibility of the Monthly Price column to the custom formula field you created​​.

Step 4: Validate in Quote Document

Generate a Quote Document for a Quote where Payment Terms are set to "Net 30."

The Monthly Price column should appear in the PDF.

Change the Payment Terms to a value other than "Net 30" and regenerate the document.

The Monthly Price column should not appear.

Step 5: Optional Enhancements

Discard Width When Hidden:In the Monthly Price Line Column, enable this setting to avoid column width adjustments when the column is hidden.

Test Across Use Cases:Validate across different Payment Terms to ensure robust behavior.

By using a combination of the Conditional Print Field and a custom formula field, Universal Containers can dynamically control the visibility of the Monthly Price column​​.

ï‚· Requirement Overview:

Configure tiered pricing for Product A specific to a customer for all future Quotes.

ï‚· Solution Details:

Use a Discount Schedule with tiered pricing.

Assign the Discount Schedule to a Contracted Price record tied to the customer's Account.

ï‚· Steps to Configure:

Create the Discount Schedule with the desired tiers.

Navigate to the customer’s Account.

Create a Contracted Price record:

Reference Product A.

Assign the Discount Schedule.

ï‚· Validation:

Generate a Quote for the customer and confirm the tiered pricing is applied correctly.

ï‚· Requirement Overview:

A customer requires specific pricing for their account.

ï‚· Solution:

B. Contracted Price Record:

Directly create a Contracted Price record related to the customer’s Account.

D. Contracted Checkbox:

Select the Contracted checkbox on the Quote record to generate a Contracted Price automatically when the Quote is finalized.

ï‚· Steps to Configure:

Option B:

Navigate to the Account and create a Contracted Price record for the specific Product and pricing.

Option D:

On the Quote, select the Contracted checkbox and ensure the Quote is synced to generate the Contracted Price.

ï‚· Requirement Overview:

Universal Containers wants to create a subscription product that will persist indefinitely unless canceled by the customer.

ï‚· Key Configuration:

The Evergreen value in the Subscription Type field defines a perpetual subscription in Salesforce CPQ.

Using a Price Rule ensures this field is dynamically set on each Quote Line for the product, automating downstream processes such as contract generation and order management.

ï‚· Steps to Implement:

Create a Price Rule targeting the Quote Line object.

Set the Subscription Type field to Evergreen for the relevant Quote Lines.

Activate and test the Price Rule to confirm the behavior.

ï‚· Dynamic Features:

A Dynamic Feature allows administrators to automatically update or populate Product Options for a bundle based on defined rules and conditions.

ï‚· Filter Product Rules:

Applying a Filter Product Rule ensures that only relevant or newly available products appear as options for the bundle. This reduces manual maintenance while keeping the bundle dynamic.

ï‚· Salesforce CPQ Reference:

Dynamic Features and Filter Product Rules are part of advanced bundling techniques documented under Product Configuration ​.

A. Leverage Salesforce automation to select the Order by Quote Line Group field on the Quote.

ï‚· Requirement:

Different profiles need to see distinct sets of fields in the Quote Line Editor.

ï‚· Solution:

Create two field sets on the Quote Line object, one for each profile.

Use a text formula field named EditLinesFieldSetName on the Quote object to dynamically return the appropriate field set name based on the user’s profile.

ï‚· Why Other Options Are Incorrect:

A & B: Field sets must be created on the Quote Line object, not the Quote object.

D: This duplicates C but introduces a typo or incorrect description in the explanation.

ï‚· Salesforce CPQ Reference:

Field set configurations for the Quote Line Editor are detailed in CPQ Field Configuration Documentation ​.

ï‚· Requirement:

Provide 80 products for general access while restricting access to 20 special products for a specific user group.

ï‚· Solution:

Two Price Books:

General Access Price Book: Includes only the 80 products available to all users.

Special Access Price Book: Includes all 100 products for users with elevated access.

Guided Selling: Dynamically assigns the appropriate Price Book based on user access level, ensuring visibility is controlled.

ï‚· Salesforce CPQ Reference:

The Price Book strategy with Guided Selling is detailed in the Product and Price Configuration guidelines ​.

Scenario:

Renewal Pricing Method is set to List, and the Quote contains standalone fixed-price subscription and non-subscription products.

Behavior:

Discounts from the original Quote are carried forward to the renewal Quote automatically as part of the renewal process, ensuring consistency in pricing.

Salesforce CPQ Reference:

Renewal Quote generation processes consider discounting rules as part of the Renewal Pricing Method ​.

=========================

ï‚· Advanced Approvals Context:

The Opportunity Object is configured out-of-the-box to integrate fully with Advanced Approvals.

Other objects, like the CPQ Quote or Quote Line, may require additional customization.

ï‚· Functionality:

Advanced Approvals use Approval Rules, Chains, and Conditions to automate the approval process.

Predefined templates and configurations are readily available for the Opportunity Object.

ï‚· Validation:

After installation of the Advanced Approvals package, confirm the Opportunity Object's configuration. No additional setup is required for basic functionality​​.

ï‚· Requirement Overview:

Universal Containers wants the Shipping Plus product to appear at the top of the Product Selection list.

ï‚· Key Configuration:

The Sort Order field determines the sequence of Products in Product Selection.

Products with lower numerical Sort Order values appear at the top.

ï‚· Steps to Configure:

Navigate to the Product Record for Shipping Plus.

Set the Sort Order field to the lowest available value (e.g., 1).

Save and test the configuration in the Product Selection screen.

ï‚· Validation:

Ensure that Shipping Plus appears at the top of the Product Selection list.

ï‚· Scenario Breakdown:

List Price = $100.00 per unit.

Quantity = 21 units.

Discount Schedule:

First Level (1–11 units): 10% discount.

Second Level (11–21 units): 25% discount.

Third Level (21+ units): 50% discount.

ï‚· Slab Discount Calculation:

First Level (1–11 units):

Price = $100 × 10 = $1,000

Discount = 10% = $1,000 × 0.10 = $100

Net = $1,000 - $100 = $900

Second Level (11–21 units):

Price = $100 × 10 = $1,000

Discount = 25% = $1,000 × 0.25 = $250

Net = $1,000 - $250 = $750

Total Net = $900 + $750 = $1,700

ï‚· Validation:This matches Salesforce CPQ's standard behavior for Slab Discount Schedules, where discounts are applied per tier.

Requirement:

Prevent users from reconfiguring a bundle after its initial configuration.

Solution:

Set Configuration Type to Allowed to permit configuration during initial setup.

Set Configuration Event to Add to allow configuration only when the product is added, blocking reconfiguration later.

Why Other Options Are Incorrect:

A: Disabled blocks all configuration, including initial setup.

B: Configuration Event = Always allows continuous reconfiguration.

D: Reconfigure Line Custom Action is unrelated to this requirement.

Salesforce CPQ Reference:

Configuration Type and Event settings are documented in Bundle Configuration ​.

ï‚· Requirement:

Ensure approval requests are routed to a substitute manager during the original manager's absence.

ï‚· Solution:

The Delegated Approver lookup field on the Approver record allows the admin to specify a temporary approver.

Setting the Delegation End field ensures the delegation automatically ends upon the original manager’s return.

ï‚· Why Other Options Are Incorrect:

A: Using the Next Approver field for temporary delegation is not the intended functionality.

B: Creating an Approval Rule with start and end dates is overly complex and unnecessary.

D: Replacing the original Approver record risks permanent changes and is not recommended for temporary delegation.

ï‚· Salesforce CPQ Reference:

Delegated Approval Settings are documented under Advanced Approvals Configuration Guidelines ​.

ï‚· Requirement Overview:

Sales reps need to redistribute Order Products across multiple Orders.

ï‚· Key Considerations:

Ownership Requirement: Only the Order owner or users with elevated permissions (e.g., Modify All) can edit an Order.

Allow Multiple Orders Setting: This setting must be enabled in the CPQ Orders package to allow splitting or redistributing Order Products.

ï‚· Steps to Enable:

For Ownership:

Confirm the sales rep is listed as the owner of the Order.

For Package Settings:

Navigate to CPQ Package Settings > Orders.

Enable the "Allow Multiple Orders" checkbox.

ï‚· Testing:

Ensure that the Edit Order Products button is exposed on the Order Page Layout and verify redistribution functionality.

ï‚· Issue Context:

A Contract could not be created from an Order for a new customer.

ï‚· Troubleshooting Steps:

A. Confirm Order Product Activation:

Contracts can only be generated for activated Order Products.

C. Check Apex Jobs:

Errors in the contracting process are logged in Apex Jobs. Review these logs for potential issues.

E. Ensure Subscription-Based Order Product:

Contracts require at least one subscription-based Product on the Order.

ï‚· Validation:

Verify that all conditions are met and retest the Contract creation process.

ï‚· Requirement:Populate a Configuration Attribute with a dynamic value when the configurator page loads.

ï‚· Solution Mechanics:

Process Builder can be used to dynamically set values on records based on predefined logic.

By targeting the Product Option field, which maps to the Configuration Attribute, Process Builder ensures that the value is set upon record creation.

ï‚· Steps to Implement:

Create a new Process Builder.

Trigger on the creation of the Quote Line record (or related record based on Configuration Attribute setup).

Define criteria to determine the dynamic value.

Use the Update Records action to populate the Product Option field with the default value.

ï‚· Advantages of Process Builder:

Allows for dynamic and conditional logic.

Automates the default value population without user intervention.

ï‚· Testing and Validation:

Create a test bundle with the Configuration Attribute.

Load the configurator and verify that the attribute is pre-populated.

ï‚· Requirement:

Hide products with the Product Family "Software" when a Configuration Attribute is set to "Perpetual."

ï‚· Solution:

Use an Error Condition to evaluate the Product Family value on the Product Option record.

Configure a Product Action to Show all products except those with the Product Family "Software."

ï‚· Mechanism:

The Error Condition evaluates the Configuration Attribute's value against the Product Option.

The Product Action ensures visibility is dynamically controlled based on the evaluated condition.

ï‚· Salesforce CPQ Reference:

Error Conditions and Product Actions are key components of Product Rules in CPQ to implement dynamic product behavior ​.

ï‚· Issue Context:

Users encounter a warning when searching Campaign records in the Quote Line Editor.

ï‚· Root Cause:

For Lookup fields to work correctly in Salesforce CPQ's Quote Line Editor, a Twin Field must exist on the target object (Campaign) with the same API name as the Quote Line lookup field.

ï‚· Solution Steps:

Create a custom field on the Campaign Object with the same API name as the lookup field on the Quote Line Object.

Ensure the field types match (e.g., both are Lookup fields or Text fields).

ï‚· Validation:

Test the functionality by searching for Campaign records in the Quote Line Editor. The warning message should no longer appear.

ï‚· Salesforce CPQ Documentation Reference:

This is a common configuration for CPQ Lookup fields in the Quote Line Editor​​.

ï‚· Bundle Configuration:

Small Storage Container (Option 1): $2.00 × 10 = $20.00

Shipping (Option 4): $7.50 (bundled).

Other Options (Option 2 and Option 3):

Medium Storage Container: Not selected.

Custom Box Label: Not selected.

ï‚· Calculation:

Bundle Parent Product Price: $5.00

Total Price: $5.00 (bundle) + $20.00 (Option 1) + $7.50 (Option 4) = $25.00

ï‚· Why Other Answers Are Incorrect:

A: Ignores bundled Option 4 price.

C: Includes non-selected options in the total.

D: Excludes all Option prices, which is inaccurate.

ï‚· Salesforce CPQ Reference:

Bundling logic and pricing are covered under Bundle Configuration Guidelines ​.

ï‚· Requirement:

Track individual serial numbers for each unit of Product A sold.

ï‚· Solution Details:

Asset Conversion Field determines how assets are created from Quote Lines.

Setting Asset Conversion to One Per Unit creates one Asset record for each unit sold, allowing tracking of individual serial numbers.

ï‚· Implementation:

Navigate to the Product Record for Product A.

Set Asset Conversion to One Per Unit.

ï‚· Justification:

This setup aligns with Salesforce CPQ's approach for granular tracking of Assets associated with product sales​​.

ï‚· Requirement Overview:

Universal Containers sells a Product exclusively as part of a bundle and does not want it to appear in the Product Selection screen.

ï‚· Solution:

The Component checkbox ensures the Product is only available as part of a bundle and is hidden from the general Product Selection screen.

ï‚· Steps to Configure:

Navigate to the Product Record for the item.

Select the Component checkbox.

Save the changes.

ï‚· Validation:

Confirm that the Product is not visible on the Product Selection screen but is available within its assigned bundles.

ï‚· Scenario:

Automatically select the Diamond Warranty Option in the child bundle if Premium Container is selected in the parent bundle and no warranty is selected.

ï‚· Solution:

Child Bundle Condition Level = 1: Ensures the condition applies at the child bundle level.

Child Bundle Action Level = None: Prevents overwriting user-selected options but enables automatic defaulting when none are selected.

ï‚· Why Other Options Are Incorrect:

B & C: Setting inappropriate levels may lead to overwriting user selections or incorrect rule execution.

D: Setting both levels to None results in no action or condition enforcement.

ï‚· Salesforce CPQ Reference:

Configuration rules and child bundle handling are outlined in CPQ Bundle Configuration Guidelines ​

ï‚· Requirement:

Allow users to choose options and define quantities during bundle configuration.

ï‚· Configuration Types:

None (A): Users can freely choose options and set quantities.

Allowed (C): Users can choose options and optionally set quantities.

Required (E): Users must configure the options and define quantities.

ï‚· Why Other Options Are Incorrect:

B: Configurable is not a valid value for the Configuration Type field.

D: Disabled prevents any configuration, which contradicts the requirement.

ï‚· Salesforce CPQ Reference:

Configuration Types are documented under Bundle Configuration Guidelines ​.

ï‚· Requirement Overview:Universal Containers needs the quantity of product options in a bundle to automatically scale based on the quantity of the parent bundle product.

ï‚· Salesforce CPQ Mechanism:

The Type field on the Product Option allows for specific configuration behaviors.

When the Type is set to Component, Salesforce CPQ automatically multiplies the option's quantity by the bundle product's quantity. This ensures that the dependent options align with the parent bundle quantity.

ï‚· Implementation Steps:

Navigate to the Product Option record associated with the bundle.

Set the Type field to Component.

Ensure that other configuration settings, such as quantity constraints, align with the desired outcome.

Test the functionality by adding the bundle to a quote and adjusting the quantity. The option quantities should scale proportionally.

ï‚· Relevant Salesforce CPQ Documentation:This behavior is a standard feature in Salesforce CPQ and is documented under Product Bundles and Options Configuration.

ï‚· Requirement:

Prevent users from selecting both Product C and Product D in a bundle configuration.

ï‚· Solution:

Using an Option Constraint with Type = Exclusion ensures that selecting one product automatically excludes the other.

ï‚· Why Other Options Are Incorrect:

A: Dependency constraints ensure one product depends on another, which is the opposite of the requirement.

B & D: Setting Min Options and Max Options in a Product Feature does not enforce mutual exclusivity.

ï‚· Salesforce CPQ Reference:

Option Constraints and their configuration are detailed in CPQ Bundling Guidelines ​.

ï‚· Requirement Overview:

Reduce scrolling in the configurator for a bundle with many Features and Options.

ï‚· Solutions:

A. Option Selection Method = Add: Allows users to select options from a pop-up window instead of scrolling through the configurator.

D. Group Features into Tabs: Use the Category field to group Features into tabs for easier navigation.

E. Option Layout = Tabs: Configure the bundle to display Options in a tabular format, reducing scrolling.

ï‚· Steps to Configure:

Set the Option Selection Method to Add on relevant Product Features.

Populate the Category field on Product Features to group them into tabs.

Change the Option Layout on the bundle Product to Tabs.

ï‚· Validation:

Test the configurator to ensure the layout reduces scrolling and improves usability.

ï‚· Requirement:

Ensure that the cubic volume selected at the bundle level applies to all Product Options.

ï‚· Solution:

Option C: Setting the Configuration Attribute's Apply to Product Options to True ensures the selected value cascades to all Product Options within the bundle.

Option D: Creating a bundle-level Configuration Attribute allows sales reps to select a single cubic volume value that governs all Product Options in the bundle.

ï‚· Why Other Options Are Incorrect:

A: Lookup Price Rules reference external objects but are not relevant to syncing a volume value across Product Options.

B: Feature-level Configuration Attributes are scoped to specific features, not the entire bundle.

ï‚· Salesforce CPQ Reference:

The functionality of Configuration Attributes and their application to Product Options is documented in Bundle Configuration Guidelines ​.

https://help.salesforce.com/s/articleView?id=sf.cpq_config_attribute_guidelines.htm &type=5

ï‚· Requirement Overview:

Ensure that the Configuration Attribute value is retained when reconfiguring a bundle.

ï‚· Solution:

Create a twin field on the Quote Line object with the same API name as the Configuration Attribute. This allows the value to persist and be passed between configurations.

ï‚· Steps to Configure:

Navigate to Setup > Object Manager > Quote Line.

Create a new custom field with the same API name as the Configuration Attribute.

Test the configuration to ensure the value persists during reconfiguration.

ï‚· Requirement Overview:

Universal Containers wants to show Quote Line items grouped by Product Family with subtotals for each family in Quote Documents.

ï‚· Solution Details:

Salesforce CPQ allows grouping of Line Items in Quote Templates.

Setting SBQQ__ProductFamily__c as the Group field organizes the Quote Lines into separate sections for each Product Family.

ï‚· Configuration Steps:

Navigate to the Quote Template.

Create a new Line Items Section.

In the Grouping field, set SBQQ__ProductFamily__c.

Save and test the template by generating a Quote Document.

ï‚· Validation:

Confirm that the generated document displays separate tables for Hardware, Software, and Professional Services, with subtotals for each group.