Free Salesforce Sales-Admn-202 Practice Exam with Questions & Answers | Set: 5

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

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

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

Product A must always be included in the bundle.

Product B should be included by default but can be removed by the user.

 Key Configurations:

Required = FALSE: This ensures that Product B is not mandatory and can be removed by the user.

Selected = TRUE: This includes Product B by default when the bundle is added to the Quote.

 Steps to Configure:

Navigate to the Product Option record for Product B.

Set Required to FALSE.

Set Selected to TRUE.

Save and test the behavior by adding the bundle to a Quote.

 Validation:

Product B should be pre-selected in the Quote Line Editor but can be deselected by the user.

This setup ensures flexibility for Product B while ensuring Product A remains mandatory​​.

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

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

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

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

When Product A is selected, Product B should be automatically selected within the bundle.

The admin created a Product Rule, but it fails to trigger immediately.

 Key Mechanism:

The Apply Immediately checkbox ensures that the Product Rule executes as soon as the parent Product (Product A) is selected. Without this, the rule may not fire until additional actions (e.g., clicking Calculate) occur.

 Steps to Resolve:

Navigate to the Product Option record for Product A.

Set the Apply Immediately field to True.

Save and test the configuration by adding the bundle to a Quote.

 Justification:

"Apply Immediately" is required for Product Rules to trigger instant actions, ensuring dependencies like auto-selection are respected without delay​​.

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