Industries-CPQ-Developer Salesforce Certified Industries CPQ Developer (SU24) Questions and Answers

To decrease the price of a product in a promotion in Salesforce Industries CPQ, the following methods are used:

• Use a pricing element adjustment (A): This involves adjusting specific pricing elements that make up the total price of the product, such as discounts or surcharges.
• Use a pricing variable (E): This allows for the dynamic calculation of prices based on variables defined within the promotion, which can be configured to reduce the product price under certain conditions.

These techniques provide a high degree of flexibility and precision in pricing adjustments, enabling tailored pricing strategies that can adapt to various promotional conditions and customer interactions.

When creating a pricing adjustment in Salesforce Industries CPQ, to ensure users understand why the price has been adjusted, a developer should: D. Include display text for the pricing adjustment: This ensures that whenever a pricing adjustment is applied, there is clear, descriptive text explaining the reason for the adjustment. This text is displayed to the user, providing transparency and clarity about the changes to the pricing.

Providing clear display text helps prevent confusion and improves customer satisfaction by making pricing dynamics transparent and understandable.

References:

• Salesforce CPQ User Experience Best Practices.
• Salesforce CPQ Developer Documentation on Pricing Adjustments.

In Salesforce Industries CPQ's Guided Selling, the vlcCart serves as both a persistent component and the shopping cart. As a persistent component, it maintains state across different user interactions within the session, ensuring that all cart-related data remains consistent as the user adds or modifies items. As the shopping cart, it is the central element that holds all the products and configurations the user is considering, managing calculations such as pricing and discounts dynamically.

In Guided Selling, to display the list of products, the Selectable Items element is used (B). This element allows users to view and select from a list of products that meet the criteria defined for the current step of the sales or configuration process. It is designed to integrate seamlessly with the cart and pricing logic, providing dynamic updates based on user selections.

References:

• Salesforce Industries CPQ Developer documentation on OmniScript elements.
• Practical examples of OmniScript configurations in Salesforce Industries CPQ.

The affectivity time frame for a product's pricing charge in Salesforce Industries CPQ: C. Can cause a pricing element to no longer be used: Affectivity dates define when a pricing element is valid. If the current date falls outside the defined affectivity period, the pricing element (like a specific charge or discount) becomes inactive and is not applied to transactions.

Affectivity time frames are critical for ensuring that pricing remains relevant and accurate, reflecting temporal changes in pricing strategies, such as promotions or seasonal adjustments.

References:

• Salesforce Industries CPQ Pricing Configuration Guide.
• Best practices for managing pricing affectivity in Salesforce Industries CPQ.

In Vlocity Cart, products with a default quantity cardinality of 0 are represented as a line item with a quantity of 0. This presentation method clearly indicates that no units of the product are initially included in the order, but it allows users to add the product by adjusting the quantity as needed.

• As a line item with a quantity of 0: This method provides visibility to the product while accurately reflecting its default state of not being included unless specifically added by the customer.

When using multiple price lists in Salesforce Industries CPQ, it is possible to assign more than one base price to the same product. This feature allows businesses to cater to different market segments, geographic locations, or customer types with varying pricing strategies. Multiple price lists enable different pricing structures under various scenarios, providing flexibility in how products are priced according to differing business needs and customer demands. This approach helps in targeting specific markets more effectively while maintaining coherent pricing strategies across the board.

In the Vlocity Cart within Salesforce Industries CPQ, the rules that are run in the cartline items panel to determine required or excluded products and/or compatibility are:

• Configuration Validation (Compatibility) Context Rules (D) - These rules are specifically designed to assess compatibility between products in the cartline. They are executed to ensure that the products added to the cart are compatible with each other based on predefined criteria.

In Salesforce Industries CPQ, components of a pricing element include: A. The price category: This categorizes the pricing logic applied, such as standard pricing, promotional discounts, or custom pricing. C. The charge (amount): This is the actual price or cost associated with the pricing element, whether it's a fixed amount, a percentage discount, or any other price adjustment.

These elements are critical in defining how prices are structured and applied within Salesforce Industries CPQ, ensuring clear pricing strategies are maintained across products and sales.

References:

• Salesforce Industries CPQ Pricing Configuration Guide.
• Detailed descriptions of pricing elements in Salesforce Industries CPQ documentation.

Vlocity Rule Builder, a tool within Salesforce Industries CPQ, facilitates the creation of various types of business rules that can be applied throughout the CPQ process. Here's what it allows you to create:

• A. Advanced rules using entity filters and rule actions - The Vlocity Rule Builder is specifically designed to create complex rules that include entity filters and define rule actions based on those filters. This functionality is integral to tailoring CPQ processes to specific business needs, ensuring that only valid and necessary data drives the CPQ logic.

When the Base Price property is checked for a price list entry in Vlocity CPQ, it indicates that the price list entry will be used as the starting price when the product is added to the cart. This base price serves as the foundational cost before any discounts, promotions, or additional configuration-based pricing adjustments are applied. It establishes the initial price point from which all other price calculations are derived during the sales and configuration process.

duct catalog, the next steps to ensure proper setup and integration into the existing system are:

• B. He must run the Refresh Pricebook job and then the Product Hierarchy Maintenance job: This sequence of actions ensures that the new product is correctly integrated into the price book, reflecting any pricing structures or rules. Following this, running the Product Hierarchy Maintenance job ensures that the product hierarchy includes the new product, maintaining data consistency and hierarchy integrity across the catalog. These steps are critical for ensuring that the product is available for use in quotes and orders without issues.

It is false that once a line item is configured in Vlocity Cart, products must be removed and re-added to change configuration. Users can modify configurations directly within the cart without needing to remove and re-add items, offering flexibility and efficiency in managing cart contents.

To ensure that context dimensions are cached and accessible to cacheable APIs in Salesforce Industries CPQ, the option that must be checked is "Cacheable Value". Marking a context dimension as cacheable improves performance by allowing these dimensions to be stored in cache memory. This speeds up data retrieval for frequently accessed information, reducing the load on the database and enhancing the overall responsiveness of the system.

When moving product catalog data containing product attributes between Salesforce orgs or setting up a new sandbox, specific tasks need to be handled to ensure the data integrity and functionality:

• A. Regenerate the attribute record ids stored in the JSONAttribute field: This is crucial because the unique identifiers associated with product attributes in one Salesforce org may not correspond to those in another. Regenerating these IDs helps prevent conflicts and ensures that attribute data aligns correctly within the new org or sandbox environment.
• C. Run the Product Hierarchy Maintenance batch job: This task is essential to maintain the integrity and structure of the product hierarchy in the new environment. The Product Hierarchy Maintenance job ensures that all relationships and dependencies within the product catalog are correctly established and maintained in the new org or sandbox.

• Removes the promotion, but nothing else: When a promotion is deleted with a "deep delete" in Salesforce Industries CPQ, it specifically targets the removal of the promotion itself from the cart or configuration without affecting other items, products, or unrelated promotions that are also present in the cart. This ensures that only the specific promotion and its direct effects are eliminated, maintaining the integrity of the remaining cart contents.

In Salesforce Industries CPQ, a price list: A. Is always associated with a price book: Price books contain one or more price lists, which in turn include specific pricing information for products. C. Contains price list entries: These are specific entries in a price list that define the price of products under various conditions. D. Can be a parent price list or child price list: This allows for hierarchical pricing structures where a parent price list can influence or control pricing in associated child price lists.

This structure supports flexible, multi-level pricing strategies that can adapt to different business needs and market conditions.

References:

• Salesforce Industries CPQ Pricing Documentation.
• Detailed guidelines on setting up and managing price books and price lists in Salesforce Industries CPQ.

When enabling the multi-language feature in Salesforce CPQ for a shared catalog, ensuring that the Russian translations display in the cart requires several checks:

• User's Locale is set to Russian: The user's locale determines which language settings the system uses to display UI elements and product information.
• Russian translations for the products exist in the StringTranslation object: Salesforce uses the StringTranslation object to store translations of various text elements in multiple languages. It's crucial that the product descriptions and other relevant text are available in this object.
• Users Language is set to Russian: This setting ensures that the system recognizes the user's preferred language for all interactions, including viewing product information in the cart.

These settings ensure that when a user who prefers Russian accesses the CPQ system, they see product descriptions and other relevant information in Russian, enhancing the user experience and ensuring clarity in communication.

To retrieve filtered products from the product catalog in Guided Selling, two effective methods are:

• Using a query to search for specific text in the product name. This method allows for dynamic searching based on user input or pre-defined criteria, making it versatile for a wide range of scenarios.
• Using DataRaptors to filter products by object type. DataRaptors are specialized tools in Salesforce Industries that manage data transformations and can be configured to filter and retrieve data based on specific attributes like object type.

These methods ensure that users can find products that meet specific requirements or preferences, enhancing the effectiveness of guided selling.

To ensure a perfect order in the cart, rules should execute in a sequence that maintains logical dependencies and data integrity. The correct sequence is:

• Context Rules Framework: First, establish the context for the transaction based on customer data and product selection. This sets the stage for more detailed rule application.
• Compatibility Rules Framework: Next, ensure that the selected products are compatible with each other. This prevents conflicts in the cart and helps in maintaining a coherent order structure.
• Advanced Rules Framework: Finally, apply advanced rules that may include dynamic pricing adjustments, promotions, or complex business logic. This layer refines the order to meet specific business objectives and customer needs.

This sequence ensures that each rule framework builds upon the data and decisions of the previous step, leading to a consistent and accurate order process in the cart.

The supported data types for context dimensions in Vlocity include Text, DateTime, and Integer. These data types are essential for defining the properties and characteristics that can be used to apply context rules:

• Text: Allows for the inclusion of alphanumeric characters which can be used for categorization or identification.
• DateTime: Useful for rules that depend on date and time conditions, such as promotions that are time-sensitive.
• Integer: Supports numerical values which are often used for quantitative conditions like thresholds or limits. These data types ensure that administrators can construct context rules that are capable of handling a variety of scenarios in a targeted and effective manner.

In Salesforce Industries CPQ, an Advanced Rule can have multiple filters to define its conditions and actions based on those conditions:

• B. 1 or more - Advanced Rules in Salesforce Industries CPQ can include one or more filters. These filters determine the conditions under which the rule applies. The ability to use multiple filters allows for complex rule configurations that can handle various business scenarios.

In Guided Selling within Salesforce Industries CPQ, the method putCartItems is used to update the items in the cart. This method is part of the cart's API that allows for the modification of cart items, such as updating quantities, changing configurations, or applying discounts. This functionality is crucial in ensuring that the cart reflects the most current selections and configurations chosen by the user or dictated by system logic.

The remote method postCartItems in Guided Selling is specifically designed to put items into the cart. This method handles the addition of selected products to the cart, allowing for further actions such as quantity updates, configuration changes, or removals. It is an integral part of managing cart operations dynamically within the guided selling process, facilitating user interactions and backend processes that reflect the current state of the cart.

In an attribute-based pricing matrix used in Salesforce Industries CPQ, the "Source Product Code" (A) is the key field used by the matching algorithm. This field uniquely identifies products, allowing the pricing matrix to apply the correct pricing rules based on the attributes associated with each specific product code.

References:

• Salesforce Industries CPQ Pricing Configuration Guide.
• Best practices for setting up attribute-based pricing in Salesforce Industries CPQ.

To avoid passing large sets of items to the configuration rules and the pricing engine in Salesforce Industries CPQ, the custom settings that need to be set to true are: B. Cache APIFields: Enabling this setting helps in reducing the data load by caching necessary API fields, thereby minimizing the data processed during configuration and pricing operations. D. DeltaValidate: This setting, when enabled, ensures that only delta changes are validated, reducing the processing load by not re-validating unchanged data.

These settings optimize the performance of the configuration and pricing engines by limiting the amount of data they need to process, thus improving efficiency and response times.

References:

• Salesforce CPQ Custom Settings Documentation.
• Performance Optimization Techniques in Salesforce Industries CPQ.

In Vlocity Context Rules, it is possible for multiple rule sets to apply to a single promotion. This flexibility allows for more granular and specific targeting of promotions based on different criteria set within each rule set. By designing the system this way, Vlocity allows administrators to create complex promotional structures that can adapt to various customer scenarios, thereby enhancing the effectiveness of promotional campaigns within the Vlocity CPQ environment.

• B. FetchAccountDetails: While the name might suggest it is for fetching details, in the context of Salesforce Industries CPQ, the FetchAccountDetails procedure can be responsible for creating accounts if configured to do so. This involves retrieving account details from an external system and updating or creating the account in Salesforce based on the retrieved data.

It is false that all Vlocity Picklist definition fields are not visible at run-time during order capture in Vlocity Cart. Vlocity allows for customization and configuration which can make picklist definition fields visible and accessible during order capture. These fields can be configured to appear based on specific criteria or processes defined within the cart and order capture configurations. This flexibility in visibility and accessibility ensures that the necessary information is available to users during the order process.

For a B2C website designed to handle high traffic and enable customers to purchase products online, the most appropriate API type to use is the Digital Commerce APIs. These APIs are designed specifically for digital commerce scenarios, supporting scalable, self-service interactions directly with customers through a digital channel. They handle product browsing, cart management, and checkout processes efficiently, even under the significant load of several million API calls, which can occur during new promotions. Digital Commerce APIs are optimized for high-volume, public-facing websites and applications, making them ideal for the scenario described.

To take 20% off the price of a child product in a promotion, you would use an "adjustment." Adjustments in Vlocity CPQ allow for the modification of prices by a percentage or fixed amount, directly influencing the price based on specific promotional rules or conditions. This method is highly effective for applying discounts in a dynamic and flexible manner, accommodating various promotional strategies.

In a Guided Selling OmniScript, the selectable items element has two primary functions:

• It retrieves filtered products from the product catalog. This is crucial for presenting users with options that are relevant to their needs or the criteria established in the guided selling process.
• It lists products retrieved by the remote action. After products are filtered and retrieved through a remote action, the selectable items element displays these products, allowing the user to select from the available options.

These functionalities make the selectable items element vital in managing product selection in a guided selling context, ensuring that users have access to appropriate and personalized options.

In the context of a promotion within Salesforce Industries CPQ, the time policy determines several temporal aspects of the promotion, specifically the duration and the end date. The duration defines how long the promotion will last from its start, while the end date specifies the exact calendar date when the promotion will conclude. These settings ensure that promotions are automatically managed according to the predefined temporal criteria, simplifying the administration of sales and marketing campaigns.

• C. Vlocity CMT Administration: To populate the API cache in Salesforce Industries CPQ, you typically use the Vlocity CMT (Cloud Management Tool) Administration interface. This tool provides the necessary functionalities to manage and configure API caching, allowing for efficient data handling and improved system performance.

• A. True: A promotional coffee mug is a typical example of a product that does not require asset tracking after it has been delivered to the customer. As such, it is a good candidate for non-assetization because it does not generally require ongoing service or updates.

To decide when to use a promotion instead of an offer to market products, consider these factors: A. Product is available to a limited set of customers: Promotions are ideal for targeting specific customer segments or demographics, allowing for more controlled and strategic marketing. C. Product is available for a limited time: Promotions are effective for creating urgency and driving sales within a specific timeframe, making them suitable for products available temporarily. D. Product needs to be sold quickly: Promotions can accelerate product uptake by offering timely incentives, which is crucial for moving inventory rapidly.

These criteria align with the strategic use of promotions to drive specific sales objectives, particularly when products require targeted marketing approaches or need to clear quickly due to time constraints.

References:

• Salesforce CPQ Promotions and Offers Documentation.
• Marketing and Sales Strategies in Salesforce Industries CPQ.

• A. Each promotion must apply to the same bundle: If you want multiple promotions to apply to the same bundle of products, each promotion must be configured to target that specific bundle. This allows the system to correctly identify and apply each promotion to the bundle as intended, ensuring that all applicable promotional discounts or benefits are properly accumulated or layered.

In the Vlocity Product Console, a facet refers to a navigational element that organizes different sections and section elements, appearing on the left-hand side of the console. This organizational structure facilitates ease of access and management of various configuration aspects of products within the console. The facet essentially acts as a guide for users to easily navigate through different functionalities available in the Product Console.

To indicate that a child product of a promotion is decreased by $5.00, you would use an "adjustment." An adjustment in this context refers to a direct modification of the product's price by a specific amount, in this case, reducing the price by $5.00. This type of pricing adjustment is straightforward and effective for applying specific monetary discounts to products within a promotion, providing clear and direct financial incentives to customers.

On the CMT Administration screen, the Product Hierarchy Maintenance job is designed to:

• A. It calls the ResolveProductHierarchyBatchJob, which serves the purpose of creating a streamlined version of the complete product hierarchy and then copying it into the data store sObject. This function is essential for maintaining an organized and efficient product hierarchy, especially in large catalogs where managing relationships between numerous products can become complex. It ensures that the hierarchy is accurate and reflective of the current product configurations and relationships.

From the Orders tab in Salesforce Industries CPQ and OM, the two statuses that are typically seen by default are the state of the Orchestration Plan itself and the Salesforce Industries Order Status. The Orchestration Plan status provides insights into where an order is in the overall process flow, which is crucial for managing complex order processes. The Salesforce Industries Order Status gives a clear indication of the current standing of the order within the Salesforce ecosystem, helping stakeholders understand the order's progress and any required actions.

• C. Opportunity, Account: For a rule targeting the launch of a new product specifically for existing S2B customers and only within opportunities, the appropriate context scope for the context mapping should include both 'Opportunity' and 'Account'. This combination allows the rule to evaluate conditions that pertain to the opportunity details as well as the customer account status, ensuring the rule applies only in the correct contexts of existing S2B customers involved in opportunities.

Adjusting the price of a product for a promotion in Salesforce Industries CPQ does not necessarily require you to run maintenance jobs to update the product hierarchy and platform cache. Price adjustments can typically be handled through configuration changes that are dynamically reflected in the platform without the need for such maintenance tasks. The system is designed to handle these changes efficiently, updating relevant data as required without manual intervention to maintain system performance and accuracy.

In Salesforce Industries CPQ, context rules allow customization of interactions based on specific conditions in the CPQ process. The correct use cases supported by context rules include:

• A. If a customer qualifies for a promotion: Context rules can be used to determine if specific criteria are met for a customer to qualify for a promotion based on their attributes or interaction history.
• D. Requiring another product when a product is added to the cart: This scenario is supported where a context rule can specify that adding a particular product to a cart triggers the requirement to include another specific product, ensuring bundle compliance or cross-sell opportunities.

In Salesforce Industries CPQ using Vlocity, a picklist can be linked to a Context Dimension. Context Dimensions in Vlocity CPQ represent a way to define and handle data dynamically within the CPQ process. By linking a picklist to a Context Dimension, users can effectively manage options that are dependent on certain contexts within the sales or quoting processes, making it versatile for adapting to various business scenarios.

In Salesforce Industries CPQ, when creating a custom pricing plan step for attribute-based pricing in the Default Pricing Plan, it is most effective to place the step between Sequence 30: Initialize Pricing Variables and Sequence 40: Apply Offer Adjustments. This placement allows the custom step to utilize initialized pricing variables effectively and apply these before any offer adjustments are made. By sequencing it in this manner, the custom pricing logic can accurately reflect the attribute-based conditions before the system calculates the final adjustments based on promotions or other pricing offers.

The Vlocity ProductConsole, a tool within Salesforce Industries CPQ, is designed to manage several aspects of product configuration, including:

• B. Product attributes: These are specific characteristics of a product, like size, color, or capacity, that can be managed directly within the ProductConsole.
• D. Products: Fundamental entities like products themselves are managed here, allowing for setup and modifications of product details.
• E. Attribute categories: These help in organizing attributes into logical groups, making them easier to manage and apply across various products.
• F. Configuration/Validation rules: These rules ensure that product configurations are valid and meet predefined criteria, critical for maintaining data integrity and business logic in product offerings.

These entities are crucial for effective product management and are centrally managed within the ProductConsole to ensure consistency and ease of access.

It is false that rules always execute if they are active. In Vlocity CPQ, active rules only execute under conditions for which they are specifically designed. This means that even if a rule is active, it requires certain triggers or conditions to be met for execution. This design prevents unnecessary rule processing and ensures that system resources are used efficiently by only applying rules when they are contextually relevant. This conditional execution is crucial for maintaining performance and accuracy in complex configurations like those in large product catalogs.

QUESTIONNO: 58

Which four of the following would require compatibility rules?

Note: This question displayed answer options in random order when taking this Test.

A. Apple iPhone requires SIM card

B. MetroE cannot be delivered to Consumer customers

C. VPN Access can only be delivered over high speed internet

D. Only DSL customers can purchase a modem

E. High Def set top box is required for High Def TV packages

Answer: A, C, D, E

In Salesforce Industries CPQ (formerly Vlocity), compatibility rules are used to ensure that certain products are compatible or require other products in order to function properly or meet certain conditions. Here's a breakdown of the answer:

• A. Apple iPhone requires SIM card - This is a direct compatibility rule where one product (iPhone) necessitates another product (SIM card).
• C. VPN Access can only be delivered over high speed internet - This is another compatibility rule that specifies a delivery condition based on the underlying service (high-speed internet).
• D. Only DSL customers can purchase a modem - This condition specifies that the purchase of one product (modem) is contingent on the customer having another product or service (DSL), which is a compatibility rule.
• E. High Def set top box is required for High Def TV packages - Similar to A, this specifies that to use one product (High Def TV packages), another product (High Def set top box) is required.

Option B, "MetroE cannot be delivered to Consumer customers," is more of an eligibility or exclusion rule rather than a compatibility rule.

In Salesforce Industries CPQ, a picklist name is not only used during the design-time for setup but can also play a role at runtime. While the name itself might not be directly visible to customers, the values it represents are crucial during runtime as they appear in the user interface. Customers interact with these picklist values when making selections or configuring products, hence it's incorrect to say the picklist name is used only at design-time.

For filtering product attributes in Salesforce Industries CPQ using Entity Filters, it is true that the API name of the JSONAttribute field must be specified in the Attribute Lookup Field Name. This is essential because the Entity Filter uses this field name to correctly identify and apply filters to the specific attributes within the product data structured in JSON format.

• D. Context Rule: For a developer managing a very large catalog, such as one with over 5 million products, implementing a Context Rule is often the easiest approach. Context Rules allow for broad application across multiple product categories based on specific criteria defined in the rule’s context, such as customer segment, geographic location, or other relevant factors. This can efficiently apply a single rule across an extensive catalog without the need to individually configure each product.

The statement "Product X requires Product Y" refers to a compatibility or inclusion rule rather than an eligibility rule:

• B. False - In the context of CPQ, eligibility typically refers to whether a customer or a specific scenario qualifies for a product or promotion based on defined criteria. In contrast, stating that one product requires another falls under compatibility or inclusion rules, which dictate that certain products must be sold or used together.

In Vlocity Cart, product images appear in the Product Details modal window. This placement ensures that users have a clear and focused view of the product visuals when they seek more detailed information about a product, without cluttering the main interface.

• Product Details modal window: This design choice enhances user engagement by providing a detailed look at the product when needed while maintaining an uncluttered primary interface, which improves overall usability and user experience during the shopping and configuration processes.

In this scenario, the discount offered by the customer service representative (CSR) to Sarah is a contract-based discount. This type of discount is applied as part of an agreement or contract renegotiation in response to a specific issue or to retain a customer, in this case, due to dissatisfaction with the service. The discount applies to future billing cycles (12 months), indicating it modifies the terms of the ongoing service contract rather than just a single order or account-wide policy.

In Salesforce Industries CPQ, when a product has both Context Rules and Advanced Rules configured, the Context Rules are enacted first at runtime. Context Rules are designed to assess and apply based on the broader scenario or context in which a product is being sold, such as customer segment or geographic region. These rules help determine the applicability and availability of products before more granular pricing or configuration logic via Advanced Rules is applied.

For Carole White who is relocating to a new address, the best action to assist in the relocation process in terms of managing her services would be:

• "Move" action on the selected Asset (A): This action is specifically designed to handle the transfer of services from one location to another, updating the service address and related billing and service details accordingly.

In Vlocity Cart, the action taken by the Submit Order button typically involves a complex process: D. Invokes an OmniScript, which calls an integration procedure to create assets, set the order status to activated and then navigate the user to account page. This process involves using OmniScript to orchestrate various backend operations including asset creation, order finalization, and navigation, efficiently integrating these steps into a seamless workflow for completing the order process.

To automatically adjust the price of a smartphone product within specified time frames, the appropriate setup involves: D. Multiple price lists with affectivity time frames: By configuring multiple price lists that have defined effective dates, the system can automatically apply different pricing for the smartphone as time progresses. This method leverages the system's capability to switch between price lists based on their affectivity, allowing for seamless price adjustments according to pre-set schedules.

In Vlocity, you can build a promotion using:

• A. An individual product: A single product can be the basis of a promotion, offering special pricing or conditions that distinguish it from the standard offering.
• B. A bundle of products: A group of products can be combined into a bundle, which itself can be offered as a promotion. This is common in scenarios where complementary products are sold together at a discounted rate.
• C. A bundle within a bundle: Nested bundles, or a hierarchy of product bundles, can also be used to create complex promotions that provide layered pricing structures or purchasing incentives.

These options provide flexibility in designing promotions that cater to diverse market needs and customer preferences, enhancing the effectiveness of sales strategies in competitive markets.

• A. True: Rules in Salesforce Industries CPQ (Configure, Price, Quote) are designed to ensure accuracy and compliance during the order process. These rules prevent users from submitting orders that do not meet business requirements or customer needs by checking for errors or inconsistencies before order submission. This includes validation of configurations, pricing, and terms, which helps reduce errors and improve efficiency.

The primary user interface components that make up the Vlocity Cart are:

• Cart Header, Product List, Cart Line Items, Total Bar (A): These components represent the main areas of interaction within the Vlocity Cart.

Promotions in Salesforce Industries CPQ are typically used to apply special pricing rules or sales conditions that enhance the sales strategy. Appropriate use cases for promotions include: B. The product's price should change based on the customer type: Promotions can be used to apply different pricing structures based on the category or type of customer, making them ideal for targeting specific customer segments with tailored pricing. C. The product should only be available to B2C customers: This allows for promotions that are exclusively available to business-to-consumer interactions, targeting specific market segments directly. E. Special pricing should only be available for a limited time: Time-limited promotions are common and can be used to drive sales within a specified period, such as during a sale event or seasonal promotion.

These use cases leverage the flexibility of promotions to target specific customer bases, adjust pricing dynamically, and drive sales strategies based on temporal factors.

To change the configuration of a line item in the Vlocity Cart, the following method is used: B. Click the cart line item Actions menu and select Configure. This option allows the user to modify the configuration of a product directly from the cart interface, adjusting attributes or selections as needed without having to delete and re-add the product.

The fields "Add Mode" and "Default Quantity" in Salesforce Industries CPQ are specifically designed to be used for auto-add or auto-replace product relationships. These fields dictate how products are automatically added or replaced in the CPQ configuration, such as adding a mandatory accessory when a main product is selected or replacing an existing product with a new version, ensuring that product configurations remain valid and complete.

In Salesforce Industries CPQ, Contract type discounts are typically used to apply negotiated discounts to customer orders under the framework of frame/pricing agreements. These discounts are predefined and are associated with specific contracts or agreement terms between the selling organization and the customer, allowing for the consistent application of agreed-upon pricing concessions across multiple orders or transactions.

If a promotion does not appear in the Promotions list of the cart in Salesforce Industries CPQ, several factors could be responsible:

• The Effective From date of the promotion is missing (A): A missing effective date means that the promotion does not have a defined start time, which can prevent it from appearing in the list.
• The Effective Until date of the promotion is in the past (B): If the effective until date is already past, the promotion is considered expired and will not be displayed.
• The promotion status is not active (C): For a promotion to be available and visible in the cart, its status must be set to active. An inactive status will hide the promotion from users.

These conditions are essential for managing the lifecycle and visibility of promotions within the CPQ system, ensuring that only current and relevant promotions are available for selection.

In the context of Configuration/Validation Advanced Rules within Salesforce Industries CPQ, the type of actions that can be used include: A. Restriction: This type of action is used to enforce certain conditions or constraints within the configuration process. Restrictions can prevent users from selecting incompatible options or configurations that do not meet certain criteria, ensuring the validity and operational feasibility of configured products.

• D. Attribute Lookup Field Name: When evaluating product attribute values within entity filters in Salesforce Industries CPQ, it is essential to set the 'Attribute Lookup Field Name'. This property specifies the exact attribute to be evaluated by the filter, enabling the system to correctly apply the defined conditions to the relevant product attribute.

It is true that the discount of a child product's price in a promotion can expire before the promotion ends. This scenario can occur if the discount terms are set with a specific expiration date that is earlier than the overall promotion end date. Such configurations allow for dynamic pricing strategies where discounts may be offered on a limited basis while the broader promotion may continue with different incentives or pricing structures.

To ensure a subscription ends at the end of the subscription plan, a developer can use "An Effective Until date." This date specifies the precise day on which the subscription will cease to be active. Setting an Effective Until date directly in the subscription setup allows the system to automatically terminate the subscription at the end of the specified period, ensuring accurate billing cycles and service durations without manual oversight.

In the Salesforce Industries CPQ framework, interactions with the cart, including adding or deleting items, trigger evaluations of applicable rules and pricing recalculations:

• A. True - Deleting an item from the Vlocity Cart does indeed initiate the re-evaluation of relevant CPQ rules and pricing engines. This ensures that any changes in the cart are reflected immediately in the pricing and that all rules are correctly applied based on the new cart composition.

• B. False: The context rules framework in Salesforce Industries CPQ does not use a single interface for all of its operations. Instead, it utilizes multiple interfaces and tools within the Salesforce platform to manage various aspects of context rules, such as creation, application, and monitoring. This is designed to provide flexibility and specialized functionality tailored to different stages of the context rule lifecycle.

The prices in the selectable Product List in the Cart for Salesforce Industries CPQ are calculated using active pricing rules and related calculation matrices. This approach allows for dynamic pricing that can adjust according to various factors such as quantity, customer segment, or specific promotional conditions. The use of pricing rules and matrices ensures that the pricing displayed is always accurate and relevant to the specific conditions and configurations of the customer's selections.

• A. True: A compound filter in Salesforce Industries CPQ does indeed chain together an internal evaluation filter with a qualification filter. This structure allows for complex filtering logic that first assesses internal criteria before applying external qualifications, enhancing the precision and effectiveness of the filtering process.

• B. By setting the Required attribute metadata property: To ensure that a user must enter a value for an attribute during order capture in Salesforce Industries CPQ, a developer should set the 'Required' attribute metadata property on the specific attribute. This setting enforces that the attribute cannot be left blank and must be filled out by the user, ensuring that essential data is captured during the order process.

In Vlocity, or Salesforce Industries CPQ, the cart configuration requires a Price List record ID to display a product list. This ID is crucial because it determines the pricing applicable to the products presented to the user based on the specific pricing configuration and eligibility. The cart leverages this ID to fetch the correct pricing information associated with each product, ensuring the displayed prices are accurate and tailored to the customer or the context of the sale. This process is integral to the dynamic pricing capability of Salesforce Industries CPQ.

The primary reason to apply an entity filter to an action in Vlocity Rule Builder is:

• A. To qualify each action applied during rule processing: Entity filters are used to define conditions under which specific actions should be executed during the rule processing phase. This ensures that actions are only taken when relevant, based on the specific attributes or status of entities involved in the process.

When Felix, the Vlocity CPQ Administrator, creates a new product attribute and it does not appear in the list for assignment to an object type, the most likely solution is to refresh the CPQ Partition platform cache. This action updates the system’s cache, which can sometimes lag behind real-time changes made in the configuration settings, causing newly created attributes to not immediately appear in relevant lists.

• Refresh the CPQ Partition platform cache: This step ensures that all recent changes are loaded into the system's active memory, allowing Felix to proceed with assigning the new attribute to the desired object type.

During the order capture process in Vlocity Cart, the Display Name of an Attribute Category is displayed at run-time. This field is used to present a user-friendly name of the category to the end user, which can differ from the technical name (or 'Name') used in system configurations.

• Display Name: This is crucial for improving user experience by providing understandable and relevant descriptors for the attributes being configured or adjusted during the order capture process.

In Guided Selling, to ensure portability of scripts from a development org to a production org, specifying the price list in the vlcCart settings is a recommended practice. By including the price list ID directly within these settings, the script remains independent of hard-coded identifiers, which might change between different Salesforce environments. This approach ensures that the cart can dynamically reference the correct price list ID, regardless of the deployment environment, thus maintaining consistency and reducing errors during migrations.

In Salesforce Industries CPQ, when pricing bundles, there are multiple strategies you can employ:

• Assigning the parent product a zero price and managing pricing entirely through the child products. This approach is often used when the value of the bundle is derived solely from its components.
• Assigning a price to the parent product and setting the prices of the child products to zero. This strategy might be used when the parent product's price encompasses the total value of the bundle, and the child products are considered included or complimentary.

These methods offer flexibility in how bundles are presented and priced, allowing businesses to tailor their pricing strategy to match their sales and marketing objectives.

When a new attribute is assigned to an object type in Vlocity, the attribute is propagated to all products linked to that object type dynamically through inheritance. This means that once the attribute is linked to the object type, all product instances that inherit properties from this object type will automatically receive the new attribute. This method ensures consistency across products and simplifies the management of product attributes, as updates need only be made at the object type level rather than individually across products.

To charge different prices for the same product within the context of different bundles, the pricing adjustments can be made in the price list where the price list entry is located. By managing different price list entries for the same product within different bundles, you can set unique prices that reflect the varying contexts in which the product is sold. This method provides the flexibility to tailor pricing based on the bundle’s specific market or customer segmentation strategies.

The Tightest Match calculation method in Salesforce Industries CPQ considers multiple conditions and applies the following rules:

• AND rule conditions: The weights of all met conditions are summed together. This aggregation is used to determine the overall applicability and strength of the rule when all specified conditions are met.
• OR rule conditions: The highest weighted value among the met conditions is selected. This approach is used when any of the specified conditions suffice for the rule to apply, prioritizing the condition with the greatest significance as indicated by its weight.

This method ensures that the rule application is both comprehensive and precise, appropriately reflecting the importance and impact of different conditions in complex decision-making scenarios.

Context rules can indeed be applied to order line items in Salesforce Industries CPQ. These rules assess the context in which products are sold and apply specific configurations or restrictions based on that context. This capability is crucial for ensuring that products and services are configured and priced correctly according to the specific circumstances of an order, enhancing accuracy and compliance in sales operations.

In the scenario where Felix, the Vlocity CPQ Administrator, needs to handle a new version of a wearable tech product with different available colors, the best approach is to create a new color picklist, and when creating the new product entry, override the attribute picklist that is inherited from its Wearable object type. This method allows for specific customization of the product without altering the existing setup for other products that share the same object type.

• Create a new color picklist and override the inherited attribute: This approach maintains the integrity of the existing products and allows new products to have unique attributes that reflect their specific variations.

In Salesforce Industries CPQ, when building an Advanced Rule using the Vlocity Rule Builder, the four components include:

• Rule Header (A) - This defines the basic information about the rule, including its name and description.
• Variables (C) - Variables are used to store data that can be reused within the rule. They help in making the rules dynamic and flexible.
• Rule Actions (E) - These are the actions executed when the conditions of the rule are met. Actions can modify data, trigger events, send messages, etc.
• Rule Filters (F) - Filters define the conditions under which the rule actions are executed. They specify the criteria that must be met for the rule to apply.

References: The components are standard in Salesforce Industries CPQ documentation on creating Advanced Rules with the Vlocity Rule Builder.

The key difference between a time plan and a time policy in Salesforce Industries CPQ is that a time plan's start can be delayed (C). This allows for greater flexibility in terms of when the pricing or terms associated with the time plan begin, accommodating scenarios where the start of service or the applicability of pricing needs to be aligned with specific events or dates.

References:

• Salesforce Industries CPQ Implementation Guide discussing time policies and plans.
• Customization and configuration options for time plans in Salesforce Industries CPQ.

Vlocity picklists can be assigned to attributes at the levels of Attributes, Object Types, and Products. This level of assignment flexibility ensures that picklists can be used effectively across various dimensions of the product configuration and sales processes, facilitating better data management and consistency across the platform.

• Attributes, Object Types, and Products: This broad applicability allows for comprehensive and cohesive data management strategies, aligning picklist values across multiple levels of product and service definitions.

In Guided Selling interactions within Salesforce Industries CPQ, retrieving products filtered by object type can efficiently be handled using a DataRaptor. DataRaptors are powerful tools designed to extract, transform, and load data specific to Salesforce and Vlocity. By setting up a DataRaptor to filter data based on the Type field or any specific criteria related to object types, users can dynamically pull relevant product sets into the guided selling process, enhancing both user experience and system performance.

• B. Simple: When adding a condition in the context rule framework of Salesforce Industries CPQ, the "Simple" option allows you to select a context dimension. This option facilitates the straightforward application of predefined criteria or attributes, making it easier to configure rules based on specific, easily defined parameters.