Sales-Admn-202 Salesforce Certified CPQ Administrator Question and Answers

ï‚· Requirement Overview:

A user must have the ability to approve any approval request, regardless of who the request is assigned to.

ï‚· Solution:

Granting the Modify All Data permission provides administrative privileges across all Salesforce objects, including the ability to approve any approval request in Advanced Approvals.

ï‚· Steps to Configure:

Navigate to the user’s Profile or Permission Set.

Add the Modify All Data permission.

Save and test the user’s ability to approve any request.

ï‚· Validation:

Confirm the user can approve approval requests without assignment restrictions.

ï‚· 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.

ï‚· 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 Overview:

The Require Approved Quote setting prevents certain records from being created without an approved Quote.

ï‚· Solution Details:

When this setting is enabled, Salesforce CPQ blocks the creation of Order records unless the associated Quote has been approved.

ï‚· Validation:

Test by attempting to create an Order from an unapproved Quote and confirming that the system blocks the action.

ï‚· Requirement:

Notify users in the Quote Line Editor when approval is required to discourage excessive discounting.

ï‚· Solution:

Use a Product Rule with Alert Action to display a notification or message in the Quote Line Editor when a user exceeds predefined discount thresholds.

ï‚· Why Other Options Are Incorrect:

A: Validation Rules prevent actions but do not notify users.

B: Filter Rules are used for restricting product selection, not notifications.

D: Selection Rules govern product compatibility and are irrelevant here.

ï‚· Salesforce CPQ Reference:

Alert actions in Product Rules are outlined in CPQ Product Rule 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.

ï‚· Scenario Overview:

The Custom value for the Condition Met field allows for complex logical operations using a mix of AND/OR across multiple Price Conditions.

ï‚· Use Case:

When a Price Rule has three or more conditions and requires specific combinations of AND and OR logic, the Custom option is required.

ï‚· Implementation:

Navigate to the Price Rule.

Set Condition Met to Custom.

Specify the logic (e.g., (Condition 1 AND Condition 2) OR Condition 3).

ï‚· Validation:This ensures Salesforce CPQ evaluates the Price Rule as intended, supporting mixed logical conditions.

ï‚· 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:

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

ï‚· Requirement:

Minimize maintenance and ensure scalability for professional services in enterprise server bundles.

New professional services are introduced frequently, requiring dynamic handling.

ï‚· Solution Steps:

Dynamic Feature (B): Allows dynamic grouping and population of professional services products, ensuring that new services are automatically included in the configuration without manual updates.

Filter Product Rule (D): Ensures only compatible professional services are displayed by applying a filtering condition with a Product Action.

ï‚· Why Other Options Are Incorrect:

A: Custom Actions are useful for guiding users during selection but do not minimize maintenance or scale dynamically.

C: A nested bundle containing all services is cumbersome to maintain as new services are introduced.

ï‚· Salesforce CPQ Reference:

Dynamic Features and Filter Product Rules are key tools for managing scalable configurations ​.

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:

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:

Identify any Quotes where a discount has been applied to options within a bundle.

ï‚· Solution Details:

B. Summary Variable:

Use a Summary Variable to check if any Quote Line within the bundle has a Discount > 0.

Configure the Max aggregation function to evaluate discounts.

C. Price Condition:

Add a condition to check if the Discount field (SBQQ__Discount__c) on a Quote Line is greater than 0.

ï‚· Steps to Configure:

Summary Variable:

Navigate to Summary Variables and create one with:

Target Object: Quote Line.

Aggregate Function: Max.

Aggregate Field: SBQQ__Discount__c.

Price Condition:

Add a condition to the Price Rule:

Object: Quote Line.

Field: SBQQ__Discount__c.

Operator: Greater Than.

Filter Value: 0.

ï‚· Validation:

Add bundle options with discounts to a Quote and verify that the rule identifies the discounted options.

ï‚· Requirement:

Use fixed pricing for quantity tiers without additional discounts.

ï‚· Solution Steps:

B: Marking the product as Non-Discountable prevents additional discounts.

D: Set the Pricing Method to Block to define fixed prices per quantity tier.

E: Create Block Pricing records to define fixed prices for each quantity tier (e.g., 1-5 licenses = $1,000).

ï‚· Why Other Options Are Incorrect:

A: Fixed Price is not suitable for tiered pricing.

C: Slab Discount Schedules are not used for block pricing.

ï‚· Salesforce CPQ Reference:

Tiered and Block Pricing setups are detailed in Pricing Configuration ​.

ï‚· 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​​.

Tiered pricing in Salesforce CPQ applies a cumulative price where each tier has a marginal rate (e.g., $9 per unit above 100). This matches the scenario: $1,000 for 0-100 units, then $9/unit for 101-500, $8/unit for 501-1,000, and $7/unit above 1,000, building on the prior tier’s total (e.g., $4,600 at 500). Option B (Tiered) supports this incremental pricing model. Option A (Block) uses fixed prices per range, not cumulative rates. Option C (Segmented) isn’t a standard CPQ pricing method. Option D (List) applies a flat unit price, ignoring tiers. Salesforce CPQ documentation defines Tiered pricing for this use case.

ï‚· 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 ​.

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.

ï‚· 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 ​.

ï‚· Requirement Overview:

Admin needs to generate one Asset record for each unit of the Product upon contracting.

ï‚· Solution Details:

The Asset Conversion field determines how Salesforce CPQ creates Asset records from Quote Lines.

Setting Asset Conversion to One per Unit ensures that for each quantity of the Product, a corresponding Asset is created.

ï‚· Steps to Configure:

Navigate to the Product record.

Locate the Asset Conversion picklist and select One per Unit.

Save and test the configuration by creating a Quote, contracting it, and verifying the Asset creation.

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.

ï‚· 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 Overview:

A group of users should receive Approval requests simultaneously, and only one user's response is required to approve.

ï‚· Key Configuration:

Use a Group ID to associate the group of approvers.

Setting Unanimous = False ensures that only one approval is needed to proceed.

ï‚· Steps to Configure:

Navigate to the Approver Record related to the Approval Rule.

Reference the appropriate Group ID.

Set the Unanimous checkbox to False.

ï‚· Validation:

Test the Approval process by submitting a Quote for approval and confirming that one approval suffices.

ï‚· 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 ​.

ï‚· 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 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:

Ensure that products available for selection are filtered by the Quote’s currency.

ï‚· Solution:

CPQ filters products based on the Price Book Entries associated with the Opportunity/Quote’s currency.

ï‚· Why Other Options Are Incorrect:

A: Active currencies do not determine product availability.

B: Dated Exchange Rates do not affect product selection directly.

C: Products with a zero Pricebook Entry are not valid for selection.

ï‚· Salesforce CPQ Reference:

Multi-currency product selection is documented in CPQ Multi-Currency Configuration ​.

ï‚· Requirement Overview:

Limit the Product Options displayed in a bundle based on the service level selected by the user via a Configuration Attribute.

ï‚· Solution Details:

Selection Price Rule: Use a Selection Price Rule to dynamically show or hide Product Options based on the selected value of the Configuration Attribute.

Apply Immediately: Ensures that changes based on the service level selection occur in real-time during configuration.

ï‚· Steps to Configure:

Create the Selection Price Rule:

Define the Price Rule with a Condition targeting the Configuration Attribute value.

Use a Price Action to show or hide Product Options.

Set Apply Immediately:

Navigate to the Configuration Attribute.

Set Apply Immediately to TRUE.

ï‚· Validation:

Test the bundle configuration by changing the service level and verifying the Product Options displayed dynamically update.

ï‚· Requirement Overview:

Control the visibility of fields in the Quote Line Editor.

ï‚· Solution:

The Edit Lines Field Set Name special field on the Quote object references the field set used to control which Quote Line fields are visible in the editor.

ï‚· Steps to Configure:

Navigate to the Field Set on the Quote Line object.

Add or remove fields from the field set referenced in the Edit Lines Field Set Name field.

ï‚· Validation:

Test the Quote Line Editor to ensure only the configured fields are visible.

ï‚· 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 ​.

ï‚· 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 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.

ï‚· Requirement Overview:

Reference specific Error Condition records in the Advanced Condition field of a Product Rule.

ï‚· Solution:

Use the Index field value from the Error Condition record in the Advanced Condition formula.

ï‚· Example:

If the Index field value is 1 for a specific Error Condition, reference it as 1 in the Advanced Condition (e.g., 1 AND 2).

Comprehensive Detailed Step-by-Step Explanation with all Salesforce CPQ References

To split orders based on product family when creating orders from quotes in Salesforce CPQ, the following steps must be followed:

Enable the Allow Multiple Orders Setting

Navigate to Setup > Installed Packages and locate Salesforce CPQ.

Click Configure, then go to the Orders tab in the CPQ package settings.

Check the Allow Multiple Orders option. This allows multiple orders to be created from a single quote.

This setting ensures that products can be grouped and split into separate orders based on specific criteria like Product Family​​.

Set the Order By Field to Product Family

From the object management settings for Quotes, edit the Order By field.

Add "Product Family" as a picklist value if it is not already available.

On the Quote, select Product Family in the Order By field.

Save your changes. When creating an order, Salesforce CPQ will group quote lines into separate orders based on the Product Family​​.

Process for Creating Orders

On the quote, select the Ordered checkbox.

Salesforce CPQ will automatically split the quote into multiple orders, grouping quote lines by the Product Family value​.

Notes and Considerations

If some quote lines do not have a value for the field used in the Order By, they will be grouped into one order.

This functionality is available in Salesforce CPQ editions starting from Summer ’16​​.

By following these steps, administrators can ensure that similar products are automatically separated into different orders based on their product family.

ï‚· Requirement Overview:

Maintenance Feature: At least one Product Option must be selected.

Support Feature: At least one and no more than two Product Options must be selected.

ï‚· Key Configurations:

Min Options = 1: Ensures users select at least one option.

Max Options = 2: Ensures users cannot select more than two options.

ï‚· Steps to Configure:

Navigate to the Feature Record for Maintenance and set Min Options = 1.

Navigate to the Feature Record for Support and set Min Options = 1 and Max Options = 2.

ï‚· Validation:

Test the bundle in the Quote Line Editor and verify the selection behavior for both Features.

ï‚· Requirement Overview:

Universal Containers needs to attach required PDF documents stored in Salesforce Documents to the Quote output.

ï‚· Solution:

Use the Additional Document feature on the Quote Template to include PDF files in the generated output.

ï‚· Steps to Configure:

Navigate to the Quote Template.

Create an Additional Document for each required PDF:

Reference the document stored in Salesforce.

Save the Quote Template.

ï‚· Validation:

Generate a Quote document and confirm that the Additional Documents are included as attachments.

In Salesforce CPQ, the Option Layout field on the Product record determines how bundle options are presented in the configurator. To allow users to view all available and selected options by scrolling on a single page, the "Sections" layout is ideal. This layout organizes options into collapsible sections based on Product Features, keeping everything visible on one page without requiring navigation steps like a wizard. Option A (Wizard) presents options step-by-step across multiple pages, which doesn’t meet the single-page requirement. Option B (assigning all options to one feature) limits organization and doesn’t address the layout requirement. Option C (Dynamic selection method) controls runtime behavior of options but doesn’t influence the single-page scrolling display. Salesforce CPQ documentation confirms that the "Sections" layout supports a scrollable, single-page view.

ï‚· Subscription Term and List Price:

Subscription Product A has a Subscription Term of 6 months with a List Price of $100.

When added to a Quote with a Term of 12 months, the List Price is prorated to account for the longer term.

ï‚· Proration and Ranged Discount Schedule:

A Ranged Discount Schedule applies discounts based on quantity, volume, or term thresholds.

For the 12-month term, the price is prorated to $200 (2 times the List Price for 6 months).

The Discount Schedule applies a 25% discount to the prorated price, reducing it to $150.

ï‚· Regular Price Calculation:

The Regular Price reflects the discounted value after applying the Discount Schedule:Regular Price=200×(1−0.25)=150×0.5=75\text{Regular Price} = 200 \times (1 - 0.25) = 150 \times 0.5 = 75Regular Price=200×(1−0.25)=150×0.5=75.

ï‚· Key Salesforce CPQ Reference Points:

Ranged Discount Schedules modify the List Price based on configured thresholds .

Subscription Pricing Logic ensures correct proration for products with terms different from the Quote Term .

ï‚· Issue Context:

Some Opportunity Products are not syncing from the Quote, causing pipeline inaccuracies.

ï‚· Troubleshooting Steps:

A. Ensure the Quote’s Account lookup is populated:

A missing Account lookup can prevent synchronization as it ties the Quote to the Opportunity.

B. Ensure the Opportunity’s Primary Quote lookup is populated:

The Primary Quote must be explicitly linked to the Opportunity for synchronization to occur.

E. Check the Quote’s Primary checkbox for a value of True:

Only the Primary Quote syncs Opportunity Products. Ensure the checkbox is set to True.

ï‚· Validation:

Verify that Opportunity Products sync correctly after ensuring these fields are properly populated.

ï‚· 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 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​​.

ï‚· Scenario:

The Create Order button generates an Order with half the Quote Lines, and the Ordered checkbox is selected.

ï‚· Outcome:

When the Ordered checkbox is checked, remaining Quote Lines are eligible for a new Order. A second Order will be generated for the remaining lines.

ï‚· Why Other Options Are Incorrect:

A: An Order without Order Products is invalid in this scenario.

C: No error is thrown because multiple Orders are allowed from the Quote.

D: Existing Orders are not updated with new Quote Lines.

ï‚· Salesforce CPQ Reference:

The behavior of the Create Order button is detailed in CPQ Order Management documentation ​.

ï‚· Requirement:

When a fixed bundle is selected, users should bypass the configuration process entirely.

ï‚· Solution:

Setting the Configuration Type to Allowed ensures users can configure the bundle if necessary.

Setting the Configuration Event to Always skips the configuration process automatically for preconfigured bundles.

ï‚· Why Other Options Are Incorrect:

A: Setting Configuration Type to Disabled prevents any configuration, which may not align with future flexibility requirements.

B: Required forces configuration instead of skipping it.

D: Configuration Event = Add requires the user to manually trigger the process during addition.

ï‚· Salesforce CPQ Reference:

Bundle Configuration Settings and their implications are detailed in CPQ Configuration Guidelines ​.

ï‚· 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 ​.

ï‚· 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 ​.

Requirement:

Separate products into different Line Item tables by Product Family when rendering a document.

Solution:

The Group Field functionality within a single Template Section can group Line Items by Product Family dynamically, avoiding the need for multiple Template Sections.

Why Other Options Are Incorrect:

B & D: Creating multiple Template Sections for each Product Family introduces redundancy and is less efficient.

C: LineSortField sorts products but does not create separate tables.

Salesforce CPQ Reference:

Group Field functionality is explained in the Quote Templates and Template Sections guidelines ​.

ï‚· 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 ​.

ï‚· 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 ​.

ï‚· 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 ​.

ï‚· Field Location and API Name:

The custom text field Additional_Text__c resides on the Quote object.

In Salesforce CPQ, the correct syntax to reference fields in HTML templates is to use the merge field syntax appropriate to the object.

ï‚· Syntax Explanation:

{!quote.Additional_Text__c} directly references the field from the Quote object in a format recognized by the CPQ document generation engine.

Alternative options such as {ISBQQ__Quote__r.Additional_Text__c} reference lookup relationships and do not apply here.

ï‚· Salesforce CPQ Reference:

As per the Quote Template Content documentation, use the merge fields directly associated with the object being utilized in the template ​.

ï‚· 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 ​.

To display Maintenance and Support products in separate sections, the admin must create Product Features, as features define sections in the CPQ configurator. To control the order (Support above Maintenance), the "Number" field on the Product Feature determines the sequence, with lower values appearing first. Option B correctly specifies two features (Maintenance and Support) and assigns a lower Number to the Support Feature, ensuring it displays above Maintenance. Option A relies on alphabetical ordering, which doesn’t guarantee Support above Maintenance (e.g., "M" precedes "S"). Options C and D use Product Options, which don’t create sections—only features do—and thus fail the separate-sections requirement. Salesforce CPQ documentation confirms feature ordering via the Number field.

ï‚· Issue:

Sales reps experience excessive horizontal scrolling to access the Clone and Delete actions in the Quote Line Editor.

ï‚· Solution:

Quote Line Editor Drawers provide a compact and user-friendly way to access actions without excessive scrolling.

ï‚· Steps to Configure:

Navigate to Setup > Custom Actions.

Configure the Clone and Delete actions to appear in the Quote Line Editor drawers.

ï‚· Validation:

Open the Quote Line Editor and confirm that the actions are accessible without horizontal scrolling.

ï‚· Requirement Overview:

Northern Trail Outfitters wants future renewals to be reflected in the Opportunity pipeline as soon as a Contract is created.

ï‚· Solution Details:

The Renewal Quoted checkbox ensures that the renewal Opportunity is created and linked to the pipeline when the Contract is generated.

ï‚· Steps to Automate:

Use a Process Builder or Flow to automatically set the Renewal Quoted checkbox on the Contract upon creation.

ï‚· Validation:

Test the process by creating a new Contract and verifying that the renewal Opportunity is added to the pipeline.

ï‚· Requirement Overview:

Limit users from selecting more than 10 product options within a specific Product Feature.

ï‚· Key Mechanism:

The Max Options field on the Feature record limits the maximum number of product options that can be selected for that feature.

ï‚· Steps to Configure:

Navigate to the Feature Record associated with the Product Bundle.

Set the Max Options field to 10.

Save and test by adding the Product Bundle to a Quote.

ï‚· Validation:

When a user attempts to select more than 10 product options within the feature, Salesforce CPQ will prevent further selections and display an appropriate message.

ï‚· 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 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:

Universal Containers wants to control whether the Additional Discount column appears on the Quote Template.

ï‚· Solution:

By creating a custom checkbox field (Show_Discount__c), administrators can dynamically control the visibility of the Additional Discount column.

This checkbox is referenced in the Conditional Print Field of the Quote Template Line Column settings for the Additional Discount column.

ï‚· Mechanism:

When the Show_Discount__c checkbox is TRUE, the column appears.

When FALSE, it does not display.

ï‚· Salesforce CPQ Reference:

Conditional Print Field functionality in Quote Templates allows for dynamic content visibility based on field values ​.