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

 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.

 Approval Scenarios in Advanced Approvals:Salesforce CPQ Advanced Approvals allows flexible approval processes, including the ability to handle group approvals within a single step.

 Key Features:

Any group member may approve: If this option is configured, approval from one group member is sufficient to move the approval step forward.

All group members must approve: When this option is selected, every group member must approve the request before the step can proceed.

 Configuration Steps:

Navigate to the Approval Rule and ensure that the Approval Chain or Approval Step is configured to support group-based logic.

Specify the behavior for the group in the Approval Step Settings.

 Use Cases:

Use "Any group member may approve" for time-sensitive scenarios.

Use "All group members must approve" for critical approvals that require consensus.

To manage a subset of eco-friendly products for opportunities flagged as eco-friendly while allowing flexibility to include all bundles, follow these steps:

Step 1: Create a Filter Product Rule

Filter Product Rules help define dynamic filtering of products displayed during the quoting process.

Navigate to Product Rules

Go to Salesforce Setup → Product Rules and click New.

Set the Type to Filter and define a clear Name such as "Eco-Friendly Product Filter."

Configure the Filter Logic

Define the conditions to identify eco-friendly and bundle products.

Use the Conditions related list to target the relevant product fields (e.g., a custom checkbox for eco-friendly products and a type field for bundles).

Example condition:

Field = Eco-Friendly Checkbox

Operator = Equals

Value = True

Step 2: Set up the Product Action

Product Actions define what the rule does when triggered.

Add a Product Action

In the Product Rule, go to the Product Actions related list and click New.

Set the Type to Optional Filter. This allows the system to apply the filter by default but enables users to remove the filter and see all bundles.

Link to Add Products Button

Make sure this action links to the Add Products custom action.

Step 3: Ensure Opportunity Integration

The Opportunity flagged as eco-friendly must drive this behavior.

Custom Field Dependency

Ensure the Opportunity has a field (e.g., Eco-Friendly Checkbox) that can be referenced in the Filter Product Rule or through a related custom formula on the Quote.

Dynamic Behavior

When the Opportunity is flagged, the filter is applied dynamically, displaying only eco-friendly and bundle products in the Add Products dialog.

Step 4: Test and Validate

Test the behavior by flagging different Opportunities as eco-friendly and verifying the Add Products functionality:

Eco-Friendly flag → Default to eco-friendly products and bundles.

No flag → All products, including non-eco-friendly bundles, are shown.

Additional Considerations:

Search Filter IntegrationThe Search Filter can complement this approach by providing additional options for users to refine their selections further​​.

User TrainingTrain sales reps on how to toggle the filter manually if needed.

This setup allows Universal Containers to meet its business objectives while maintaining flexibility for its sales team​.

 Requirement Overview:

Prevent users from making price changes to Quotes or Quote Lines that have already been approved.

 Solutions:

C. Validation Rule:

Create a Validation Rule to block any material changes to approved Quotes or Quote Lines.

D. Product Rule:

Use a Validation Product Rule to prevent edits to pricing fields once a Quote has been approved.

 Steps to Configure:

Validation Rule:

Navigate to Setup > Validation Rules for the Quote and Quote Line objects.

Create rules to restrict edits when the status is set to Approved.

Product Rule:

Create a Validation Product Rule targeting Quote or Quote Line fields.

 Validation:

Test by attempting to edit an approved Quote and verifying the system prevents changes.

 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 ​.

When amending a contract in Salesforce CPQ, the net pricing of products can sometimes appear incorrect, especially when quantities are adjusted on existing subscriptions. The "Revised Quantity" field on the Subscription record is used during amendments to reflect the updated quantity of a subscription product after the amendment. If this field is set incorrectly or unexpectedly (e.g., manually or via automation), it can override the expected quantity and cause discrepancies in pricing calculations, especially for existing products. This aligns with the scenario where the issue only occurs when quantities are adjusted on existing products. Option B (Price Rule firing On Calculate) could affect pricing but typically wouldn’t target only existing products or cause quantity-specific issues unless explicitly designed to do so. Option C (Price Rule firing Before Calculate) might alter pricing but wouldn’t directly tie to quantity adjustments on amendments. Option D (Discount Schedule with Cross Order unselected) affects pricing tiers but isn’t directly related to amendment quantity adjustments. Per Salesforce CPQ documentation, the "Revised Quantity" field is a key factor in amendment scenarios impacting pricing consistency.References: Salesforce CPQ Documentation - "Amending Subscriptions" and "Subscription Fields" (Revised Quantity).

 Scenario:

A tiered pricing structure requires different amounts to be applied based on the quantity purchased.

 Solution:

Use a Discount Schedule with:

Type = Slab: Ensures different price amounts are applied for each tier.

Discount Unit = Amount: Specifies fixed dollar values for each tier.

 Why Other Options are Incorrect:

A, B: Block pricing is unsuitable because the requirement is tier-based, not fixed blocks.

C: Range type does not handle tiered pricing accurately.

 Salesforce CPQ Reference:

Discount Schedules with Slab type are detailed in CPQ Discounting Guidelines ​.

 Requirement Overview:

Ensure that the Contract Name field is visible to users when initiating an Amendment.

 Key Configuration:

The Active Contract Lookup Field Set on the Contract object determines which fields appear when selecting a Contract for an Amendment.

 Steps to Configure:

Navigate to the Field Set named Active Contract Lookup on the Contract Object.

Add the custom Contract Name field to the Field Set.

 Validation:

Test the Amendment process to confirm that the Contract Name field is visible.

 Requirement Overview:

Assign generated Approval requests to the user's direct manager.

 Solution:

Salesforce CPQ's Advanced Approvals package includes the setting Next Automated Approver Determined By, which allows Approvals to be routed automatically to the user's manager.

 Steps to Configure:

Navigate to the Approval Process.

Set Next Automated Approver Determined By to Manager.

Save and test the Approval process to ensure it correctly assigns to the manager.

 Requirement:

Clients can negotiate a discount for Product A until a specified date before contract activation.

 Relevant Fields on the Contracted Price Record:

Product: Identifies Product A as the subject of the negotiated price.

Expiration Date: Specifies the end of the discount eligibility period.

Discount: Sets the agreed discount percentage for the negotiated price.

 Salesforce CPQ Reference:

Contracted Price Record management is key to implementing client-specific pricing strategies ​.

 Requirement Overview:

A Percent of Total option in a multi-level bundle must calculate its value based on other options in the same level.

 Key Configuration:

The Percent of Total Scope field determines the scope of the calculation.

Setting it to Components limits the calculation to options within the same bundle level.

 Steps to Configure:

Navigate to the Product Option record for the Percent of Total option.

Set Percent of Total Scope to Components.

 Validation:

Add the bundle to a Quote and verify that the Percent of Total calculation includes only the options at the same level.

Understanding the Requirement:

Universal Containers needs Product Option A to be automatically included with Product B during the configuration.

Sales reps should not be able to remove Product Option A.

Salesforce CPQ Mechanism:

The Required field on a Product Option ensures that it is mandatory within a bundle and cannot be deselected by the user during configuration.

Field Behavior:

When the Required checkbox is selected for a Product Option:

The option is always included in the bundle configuration.

Users cannot remove or modify it unless additional automation (like a product rule) overrides this setting.

Configuration Steps:

Navigate to the Product Option A record associated with Product B in Salesforce CPQ.

Select the Required checkbox and save the changes.

Ensure that no conflicting product or price rules exist that could affect this behavior.

Field Alternatives and Clarifications:

Bundled: Sets the option as a part of the bundle, but this primarily affects pricing (sets price to zero) and doesn't enforce inclusion.

Quantity Editable: Allows control over whether users can adjust the quantity but does not prevent removal.

Selected: Preselects the option during configuration but still allows users to deselect it.

Verification and Testing:

Create a test configuration with Product B as the parent and verify that Product A is always included in the bundle.

Attempt to remove Product A to confirm that it is not possible.

References:

Verified from Salesforce CPQ official guidelines on "Required" field functionality for Product Options​​.

 Simplification Method:

By adding the PDF as a required Additional Document in the Quote Template, Salesforce CPQ ensures the PDF is automatically included with each generated Quote.

 Steps to Configure:

Navigate to the Quote Template.

Add the PDF file under the Additional Documents section.

Mark it as required for automatic inclusion.

 Salesforce CPQ Reference:

The Additional Documents feature simplifies document management in Quote Templates ​.

 Requirement Overview:

Universal Containers wants to sell monthly subscriptions and round additional days up to the nearest month when calculating prorated prices.

 Solution Details:

Subscription Term Unit = Month: Ensures that subscriptions are billed on a monthly basis.

Subscription Prorate Precision = Month: Rounds up additional days to the next month.

 Steps to Configure:

Navigate to CPQ Package Settings > Subscription and Renewal Settings.

Set the Subscription Term Unit to Month.

Set the Subscription Prorate Precision to Month.

Save and test the configuration by creating a Quote with subscription products.

 Validation:

Ensure that additional days are rounded up to the next month in the prorated pricing calculation​​.

 Requirement:

The processor is priced differently when sold as a standalone product versus as part of a laptop bundle.

 Solution:

Marking the processor as Bundled ensures the discounted price applies only when it is part of the laptop bundle.

 Mechanism:

When the Bundled checkbox is TRUE, Salesforce CPQ applies the discounted pricing for bundle components based on the defined Price Book Entry.

 Salesforce CPQ Reference:

Bundled pricing behavior is described in the Product Option and Bundle Configuration Guidelines ​.

 Smart Approvals Overview:

Salesforce CPQ's Smart Approvals streamline the approval process by re-evaluating previously approved records to avoid redundant approvals.

 Rejected Quotes Resubmission:

If a quote is rejected, and the user resubmits it without exceeding previously approved values, it bypasses the full approval chain and is sent directly to the person who rejected it.

This functionality minimizes unnecessary delays and ensures efficient quote handling.

 Documentation Alignment:

Smart Approvals Configuration and behavior as outlined in CPQ guidelines ensure approval efficiency ​.

 Requirement:

Allow customers to return asset Products and receive credit.

 Solution:

Setting the Asset Amendment Behavior to Allow Refund enables the product to be reduced in quantity on an Amendment Quote.

Reducing the Quantity on the Amendment Quote triggers a refund process in CPQ.

 Why Other Options Are Incorrect:

A: Negative quantities are not a supported standard in Amendment Quotes.

C & D: Asset records should not be manually edited as changes must flow through Quotes and Orders.

 Salesforce CPQ Reference:

Refund handling and Asset Amendment Behavior are described in Amendment and Renewal Processes ​.

 Requirement Overview:

Warranty pricing should be based on the discounted prices of hardware products.

 Solution Details:

The Percent of Total Base field determines the pricing basis for Percent of Total Products.

To ensure the price reflects discounted values, set the Percent of Total Base to Net Price.

 Steps to Configure:

Navigate to the Warranty Product record.

Update the Percent of Total Base field to Net Price.

Save and test the configuration by adding hardware products and the Warranty to a Quote.

 Validation:

The Warranty price should now calculate as 10% of the discounted prices of hardware products​​.

Understanding the Requirement:

Universal Containers wants sales reps to associate Campaign records with Quote Lines using a lookup field in the Quote Line Editor.

The requirement includes avoiding warning messages when searching for Campaign records.

Salesforce CPQ Lookup Field Behavior:

When a lookup field is added to the Quote Line Editor, Salesforce CPQ searches for records in the target object (e.g., Campaign).

To avoid warnings, the target object (Campaign) must have a specific field set named CPQ_Lookup, which defines the fields displayed in the search results.

Steps to Implement the Solution:

Step 1: Navigate to the Campaign object in Salesforce Setup.

Step 2: Go to the "Field Sets" related list and click "New."

Step 3: Name the field set CPQ_Lookup (case-sensitive).

Step 4: Add the fields you want to display in the lookup search results (e.g., Campaign Name, Start Date, Owner).

Step 5: Save the field set.

Integration with the Quote Line Editor:

The system will now use the fields defined in the CPQ_Lookup field set when sales reps perform a search for Campaign records.

This ensures the lookup field operates without errors or warnings in the Quote Line Editor.

Key Considerations:

Ensure that all required fields for identifying Campaign records are included in the CPQ_Lookup field set.

Test the lookup functionality in the Quote Line Editor to confirm smooth operation.

Validation:

Add a Campaign lookup field to a Quote Line in the Quote Line Editor and test the search functionality. Verify that the fields defined in the CPQ_Lookup field set appear in the search results without warnings.

References:

Salesforce CPQ documentation on setting up lookup fields and field sets emphasizes creating a CPQ_Lookup field set to avoid warnings

 Requirement:

To allow sales reps to view a subset of products via a button in the Quote Line Editor.

 Solution:

A Custom Action with a Search Filter is configured to dynamically limit the displayed products.

 Mechanism:

The Custom Action triggers the Product Selection process, with the Search Filter applying criteria to display only the desired subset of products.

 Salesforce CPQ Reference:

Custom Actions and Search Filters are documented as the preferred method to customize product visibility in the Product Selection process .

 Scenario Overview:

List Unit Price: Product A's standard price is $150.

Contracted Price: CK has a contracted price of $100 for Product A.

Discretionary Discount: CK negotiated a 10% discretionary discount for this deal.

 Price Calculation:

List Unit Price remains the standard price of $150.

Regular Unit Price applies the contracted price of $100.

Customer Unit Price: After applying the 10% discretionary discount on the contracted price,Customer Unit Price=100−(100×0.1)=90\text{Customer Unit Price} = 100 - (100 \times 0.1) = 90Customer Unit Price=100−(100×0.1)=90.

Net Unit Price matches the Customer Unit Price for the 10 units being purchased, which is $90.

 Salesforce CPQ Reference:

Salesforce CPQ Contracted Price logic ensures negotiated prices override the List Price, and additional discretionary discounts apply as expected ​.

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 ​.

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

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:

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 ​.

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 .

 Scenario:

Product A has no Subscription Pricing, while Product B uses Percent of Total with a shared category.

During renewal, Product A has a Net Total of zero.

 Reason:

When the Renewal Model is set to Asset-Based, only assets tied to the Contract are included in the renewal.

Since Product A has no Subscription Pricing, it is not treated as a subscription and thus has a Net Total of zero.

 Why Other Options Are Incorrect:

B: Product A is not pre-owned in this scenario.

C: The Include Net-New Products in Maintenance setting applies to maintenance scenarios, not standard renewals.

D: Asset Conversion determines asset behavior, not renewal totals.

 Salesforce CPQ Reference:

Renewal behaviors with Asset-Based Models are covered in CPQ Renewal Settings Documentation ​.

 Requirement Overview:

Prevent the user from selecting Product B unless Product A is also selected in the bundle.

 Key Configurations:

Type = Dependency: Ensures that one Product is dependent on the selection of another.

Active = True: Activates the Option Constraint for use in the configurator.

 Steps to Configure:

Navigate to the Option Constraint record.

Set the Type to Dependency.

Mark the Active checkbox as True.

Define Constrained Option (Product B) and Constraining Option (Product A).

 Validation:

Add the bundle to a Quote and confirm that selecting Product B is only possible when Product A is also selected.

 Real-Time Calculation:

The Calculate Immediately field in CPQ ensures that pricing calculations occur automatically when changes are made in the Quote Line Editor without requiring manual saving.

 Field Behavior:

Enabling this field configures CPQ to detect changes to the Partner Discount or other relevant fields and trigger real-time recalculations.

 Salesforce CPQ Reference:

Configuration settings for real-time pricing calculations are documented in the Pricing and Calculation Package Settings .

 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​​.

 Scenario Overview:

A Configuration Attribute displays a picklist with more values than the corresponding field on the Quote Line, which is restricted to a predefined set.

 Behavior:

When a user selects a value that is not in the Quote Line field’s restricted picklist, Salesforce CPQ prevents saving and displays an error.

 Validation:

The Quote Line enforces the picklist restriction, ensuring data integrity across the configuration and Quote Line Editor.

 Issue Context:

Lookup Price Rules rely on the SBQQ__LookupObject__c field to reference the target object (e.g., Rental Rates).

If this API name is inaccurate or incorrectly input, the rule will fail to retrieve the desired value.

 Review Steps:

Go to the Price Rule record.

Check the SBQQ__LookupObject__c field. Confirm the API Name of the Rental Rates object is accurate.

Example: Ensure the API name matches exactly (e.g., Rental_Rates__c).

 Additional Checks:

Verify the Lookup Queries. Ensure the filter conditions correctly target a valid record on the referenced object.

 Salesforce Documentation Reference:This behavior follows Salesforce CPQ's guidelines on Lookup Price Rules configuration​​.

 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:

Understand what impacts the number of query rows returned when using Lookup Rules in Salesforce CPQ.

 Factors:

C. Total Number of Quote Lines: Each Quote Line triggers a lookup, increasing the number of query rows.

D. Total Number of Fields on the Lookup Object: More fields on the object result in larger query rows.

E. Total Number of Lookup Queries: Multiple lookup queries executed during the Quote Line processing impact the total rows returned.

 Steps to Validate:

Analyze the Lookup Rule configuration and test its behavior with varying Quote Line counts, field sizes, and query numbers.

To set a dynamic default value for a Configuration Attribute when the configuration page loads, automation must populate the associated Product Option field automatically. Option A uses a Flow to update the Product Option field tied to the Configuration Attribute, triggered upon record creation (e.g., when the Quote Line is initiated), ensuring the value is set dynamically at page load. Option B (Price Rule) requires manual user action ("Apply Rules"), which doesn’t meet the "moment the page loads" requirement. Option C (Quote formula field) isn’t directly supported as a default source for Configuration Attributes without additional customization. Option D (Quote Line field with Price Rule) lacks real-time dynamism and alignment with page load timing. Salesforce CPQ documentation highlights Flows as a robust solution for dynamic defaults.References: Salesforce CPQ Documentation - "Configuration Attributes" and "Using Flows in CPQ".

 Requirement:

Apply different uplift rates to Product Families X and Y upon renewal.

 Solution Steps:

Option A: Set the Renewal Uplift Rate on each Subscription record for Product Families X and Y.

Option C: Configure the Account’s Renewal Pricing Method as "Uplift" to enable uplift calculations during renewal.

 Why Other Options Are Incorrect:

B and D: These options fail to apply the correct rates at the Subscription or Product Family level.

 Salesforce CPQ Reference:

Uplift rates and Renewal Pricing methods are outlined in CPQ Renewal Configuration Guidelines ​.

UESTION NO: 83

Users at Universal Containers want to know how Approval requests will be routed prior to submitting a Quote for approval.

How can the admin meet this requirement?

A. Using Native Approvals, build a custom Visualforce Page to display the Approval Process for the Quote.

B. Using Advanced Approvals, place the Preview Approval button on the Quote page layout.

C. Using Advanced Approvals, build a custom Visualforce Page to display the Approval Chains for the Quote.

D. Using Native Approvals, build a custom button to display the approval matrix to users.

Answer: B

 Requirement:

Sales reps need visibility into the Approval Chain before submitting a Quote for approval.

 Solution:

The Preview Approval button in Advanced Approvals allows users to view the Approval Chain directly from the Quote page.

 Why Other Options Are Incorrect:

A and C: Building custom Visualforce pages is unnecessary with Advanced Approvals.

D: Native Approvals do not offer a built-in preview feature.

 Salesforce CPQ Reference:

Advanced Approvals functionality, including the Preview Approval button, is detailed in CPQ Approval Configuration ​.

 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.

 Requirement:

The Color of containers (a Configuration Attribute) must be displayed in the output document.

 Solution:

Create a Color field:

On Product Option: Captures the color selection during configuration.

On Quote Line: Ensures the selected color is carried forward to the quote document.

 Why Other Options are Incorrect:

B, D: These options do not account for both configuration and quote visibility requirements.

C: The Product object alone cannot store configuration-specific selections like color.

 Salesforce CPQ Reference:

Configuration Attributes and their linkage to Quote Lines are documented in CPQ guidelines ​.

Amendment Functionality:

Amendments are used to modify existing contracts by adjusting quantities, discounts, or adding products while maintaining contract continuity.

Supported Scenarios:

A: Quantity changes with new discounts can be applied during amendments.

C: New products can be added and aligned with the contract’s existing term (co-terminated).

Salesforce CPQ Reference:

Amendments are extensively documented under Contract and Subscription Management ​.

 Requirement Overview:

Universal Containers wants to restrict sales reps to accessing only region-specific Products while allowing managers to access all Products.

 Solution:

C. Price Books per Region: Create a separate Price Book for each region, associating only the relevant Products. Share each Price Book with the respective sales reps.

D. Product Rules: Use Product Rules to hide Products from sales reps outside their assigned regions.

 Steps to Configure:

Price Book Setup:

Navigate to Price Books.

Create a Price Book for each region and associate the specific Products.

Use Sharing Rules to share the Price Books with the appropriate sales reps.

Product Rule Setup:

Create a Product Rule with a Condition to hide Products based on the user’s region.

 Validation:

Test by logging in as a sales rep and verifying that they can only see Products for their assigned region.

 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:

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 ​.

 Potential Causes:

Component Checkbox: Products marked as Components are typically excluded from being directly selectable in the Product Selection screen unless part of a bundle .

Search Filter: Custom Search Filters on the Add Products button limit the display of products based on criteria such as product attributes or field values.

 Excluded Reasons:

Hidden Checkbox: This is generally used to hide products from the Quote Line Editor, not the Product Selection screen.

Custom Action Condition: While these can limit the Add Products button's visibility, they do not directly affect individual product visibility.

 Salesforce CPQ Reference Points:

Documentation on Product Selection Behavior and Search Filters confirms these behaviors ​.

 Issue Context:

The custom field is not being updated by the Price Rule even after enabling triggers in the CPQ Package Settings.

 Root Cause:

After creating new fields or updates, the Post Install Script must be executed to register custom fields in the Calculator Referenced Fields list.

 Solution Steps:

Navigate to Setup > Installed Packages > Salesforce CPQ.

Locate the Post Install Scripts section and click Run.

Test the Price Rule again to verify that the custom field is updated correctly.

 Salesforce CPQ Documentation Reference:

Custom fields must be registered with the calculator for the Price Rule engine to interact with them properly​​.

 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.

 Requirement:

Ensure the Warranty Period from the Product is correctly transferred to the Asset record.

 Solution:

Create a twin field on the Quote Line because:

The Quote Line stores product-specific information during quoting.

When the Quote is contracted, the twin field ensures the value is passed to the Order Product and then to the Asset record.

 Why Other Options Are Incorrect:

A: The Product Option is used within bundles and does not directly transfer to the Asset.

B: The Order Product receives data from the Quote Line, so the twin field must originate there.

C: The Opportunity Product is not involved in the CPQ twin field data flow.

 Salesforce CPQ Reference:

Twin fields and their data flow from Quote Line to Asset are detailed in CPQ Field Mapping Documentation ​.

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​​.

 Issue:

Quote Lines on Quote A are grouped incorrectly in the output document.

 Possible Causes:

C: Quote Line Groups: Existing Quote Line Groups on the Quote override the Group Field setting in the template.

D: Group Field in Template Section: The Group Field value in the Line Items template section may cause unexpected grouping.

 Why Other Options Are Incorrect:

A: The Modified By field has no impact on template grouping.

B: Configuration Attributes like location affect product selection, not grouping in Quote templates.

 Salesforce CPQ Reference:

Grouping behavior is explained in the Quote Templates and Line Item Configuration documentation ​.

 Scenario:

Contracts are not being generated for activated Orders containing subscription-based products.

 Why Debug Logs?

Debug Logs capture real-time system activity, including Apex triggers and CPQ package processes.

They provide detailed error messages and can identify issues such as missing triggers, misconfigured objects, or dependency errors.

 Steps to Investigate:

Enable Debug Logs in Salesforce Setup for the affected user or system process.

Perform the action that generates the error (e.g., activating the Order).

Review the logs for errors related to Contract generation.

 Hierarchy of Discount Schedule Application:Salesforce CPQ applies Discount Schedules based on object precedence.

Contracted Price: Overrides Discount Schedules at the Product or Feature level when specific pricing agreements are in place for an Account.

Product Option: A Discount Schedule on a Product Option takes precedence over one defined at the Product Feature level.

 Key Configurations:

Contracted Price: Navigate to the Contracted Price record and add the Discount Schedule.

Product Option: Assign the Discount Schedule on the Product Option record.

 Validation:

Test configurations to confirm the Discount Schedule is applied at the appropriate level and overrides the Feature-level Discount Schedule.

 Requirement:

Ensure a product priced as a Percent of Total has a minimum price of $100.

 Solution Steps:

Option A: Create a Price Book Entry of $100 to set the minimum price for the product.

Option D: Create a $0 Price Book Entry to handle scenarios where Percent of Total calculation would otherwise drop below $100.

 Why Other Options Are Incorrect:

B: The custom Percent_of_Total_Target_c field is not used for minimum pricing enforcement.

C: The Percent of Total Constraint field alone does not enforce minimum pricing.

 Salesforce CPQ Reference:

Percent of Total pricing and minimum price settings are described in CPQ Pricing Configuration ​.

 Issue Analysis:

Products not syncing to Opportunity Products is usually caused by specific CPQ conditions or rules.

 Reasons for Failure:

B: Products with an Effective Quantity of zero are excluded from syncing.

C: Validation Rules on the Opportunity Product object may silently block the sync process if they are not met.

D: Products with a price of zero do not sync by default.

 Why Other Options Are Incorrect:

A: Missing Price Book Entries prevent quoting entirely, not syncing issues.

E: The Exclude from Opportunity checkbox applies to the Product Option, not the syncing process.

 Salesforce CPQ Reference:

CPQ guidelines for syncing Quote Lines to Opportunity Products ​.

 Requirement Overview:

Sales reps need to know when manual overrides on a Discount Schedule will remain unaffected by Admin updates.

 Key Behavior:

When the Save or Quick Save button is clicked, the manual override is committed, and the Discount Schedule changes made by the Admin will not affect it.

 Validation:

Test the behavior by manually overriding a discount, saving the Quote, and confirming that Admin updates to the Discount Schedule do not impact the saved Quote.

 Scenario:

A Price Rule utilizes a Lookup Object and Lookup Queries, and multiple records meet the criteria for a single Quote Line.

 Behavior:

When more than one lookup record meets the criteria, Salesforce CPQ does not apply any value to the Target Field. Instead:

The Target Field retains its original value.

An error message is displayed in the Quote Line Editor, notifying the user of the conflict.

 Why Other Options Are Incorrect:

A & D: Salesforce CPQ does not resolve ties by sorting records alphabetically.

C: The system does not apply values based on record creation date.

 Salesforce CPQ Reference:

Lookup Queries behavior and error-handling are outlined in CPQ Price Rules Configuration Guidelines ​.

 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 ​.