Industries-CPQ-Developer Questions and Answers

The explanation for the discounted price of a child product within a promotion is determined by the display text associated with the price adjustment or override. This text typically provides details about why the price has been adjusted or overridden, such as a specific promotion or discount offer. This feature is crucial for transparency, helping customers understand the pricing changes and the value offered through the promotion.

• A. True: Compatibility rules in Salesforce Industries CPQ indeed use product relationships as their rule action. These rules leverage the relationships defined between products to apply business logic, ensuring that products added to the cart are compatible with each other based on predefined criteria.

To limit the ordering of a product bundle to the specific dates between January 5th and January 31st, the following configuration is most appropriate: C. Set the Selling Start Date to January 5 and the Selling End Date to January 31: This configuration directly restricts the availability of the product for purchase to between these specific dates, aligning precisely with the product manager's requirements.

The buttons in the top right of the cart header in Vlocity Cart are configurable elements within the Salesforce Industries CPQ setup:

• C. Buttons defined in the cpq-cart-setup template - These buttons are defined within the cart setup template, allowing for customization according to specific business processes or user interface needs. This setup ensures that the buttons can perform the required actions directly from the cart, enhancing user experience and functionality.

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.

Rules in Salesforce Industries CPQ are triggered when the "Validate Cart" button is clicked. This mechanism ensures that all the business rules and validations are enforced at a critical point in the transaction process, specifically when finalizing the configurations and selections in the cart.

• When the "Validate Cart" button is clicked (D): This trigger is crucial for ensuring that the cart meets all business, product, and regulatory requirements before proceeding to checkout or final approval, providing a safeguard against incorrect or incomplete configurations.

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.

The cardinality of a promotion's child product in Vlocity allows you to set:

• A. The minimum amount of the product that can be purchased: This sets a lower limit on the quantity of the child product in the promotion, ensuring that a certain number is always included in the purchase.
• B. The maximum amount of the product that can be purchased: This sets an upper limit, controlling the maximum quantity of the child product that can be included in the promotion.
• D. Whether the product is optional for purchase: Cardinality can specify whether the inclusion of the child product in the promotion is mandatory or optional, providing flexibility in how promotions are structured and offered to customers.

Cardinality settings are critical for defining the purchasing rules associated with promotional bundles, allowing businesses to tailor promotions to meet specific sales strategies and customer needs.

When creating a quote from an existing asset in Salesforce Industries CPQ, the status of the corresponding line item will typically be set to "Change". This status indicates that the line item is being modified or revised from its original configuration, reflecting the new terms or conditions specified in the quote. This status helps in tracking how assets are being adjusted or repurposed through the sales and quoting process, ensuring clarity in transaction histories and customer records.

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.

The statement that enabling CPQPartition platform cache is not required for smaller deployments is false. Regardless of the deployment size, enabling the CPQPartition platform cache can significantly improve performance by reducing the load times and improving the responsiveness of the CPQ system. This cache plays a critical role in managing data efficiently, especially in environments where multiple product configurations and pricing calculations are frequent. It ensures that smaller deployments can still benefit from optimized data handling and system performance, akin to larger implementations.

QUESTIONNO: 103

What tasks must be done when new product bundles are added to the product catalog? (Choose TWO)

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

A. Clear the platform cache

B. Refresh Pricebook, which runs the ProductHierarchyBatchProcessor job

C. Run the Product Hierarchy Maintenance batch job

D. No manual action is required

Answer: B, C

When new product bundles are added to the product catalog in Salesforce Industries CPQ, specific tasks must be performed to ensure the system recognizes and correctly processes these additions. Firstly, running the Product Hierarchy Maintenance batch job is crucial as it updates the system on the new hierarchical relationships introduced with the new bundles. Secondly, the Refresh Pricebook task, which includes running the ProductHierarchyBatchProcessor job, is essential to update and ensure that all pricing data is accurate and reflects the latest catalog changes. These steps are vital for maintaining data integrity and functionality in CPQ processes, ensuring that new products are fully integrated and operable within the system.

Entity Filters in Salesforce Industries CPQ (formerly Vlocity CPQ) are not exclusively tied to a single Advanced Rule. Instead, they can be associated with multiple rules, depending on the complexity and needs of the configuration. This flexibility allows Entity Filters to be reused across different rules, enhancing efficiency and reducing redundancy in rule setup.

• False (B): Entity Filters are designed to be modular and reusable, allowing them to be applied across various scenarios and rules within the Salesforce Industries CPQ environment.

Picklist entities in Vlocity EPC (Enterprise Product Catalog), which is part of Salesforce Industries CPQ, are indeed globally reusable Salesforce picklists. These picklists can be managed through the Vlocity Product Console or the Salesforce Setup. This feature allows for centralized management of picklist values which can be used across various Salesforce and Vlocity applications, enhancing consistency and maintainability of data.

A time policy on a promotion primarily determines the temporal scope of the promotion, specifically:

• The duration of the promotion (A): This defines how long the promotion will be active, from start to finish.
• The end date of the promotion (C): This explicitly sets when the promotion will conclude.

These elements are critical for defining the availability and lifecycle of a promotional offer, ensuring that it aligns with strategic marketing plans and business objectives.

The Lightning web component in Salesforce Industries CPQ that allows the user to submit their payment details is dcCheckoutPayment. This component is specifically designed to handle payment processing within the CPQ system, providing a secure and user-friendly interface for customers to enter and submit their payment information as part of the checkout process. It ensures the secure handling of sensitive financial data and integrates seamlessly with payment gateways and financial systems.

The Communications Cloud in Salesforce Industries operates with a distinct architecture and feature set:

• A. Is based on a three-tier communications data model: This is true as the Communications Cloud utilizes a comprehensive data model specifically designed to manage the complexities of the telecommunications industry. This model includes layers for managing customer information, service subscriptions, and network inventory.
• B. Includes a shared product catalog: The Communications Cloud features a shared product catalog that allows for consistent product information management across different channels and customer segments, facilitating a unified approach to product offerings.

To create a quote from an existing asset in Salesforce Industries CPQ, you can utilize the "Change to Quote" action button. This feature is designed to streamline the process of generating new quotes based on existing assets, thereby facilitating upselling, contract renewals, or modifications. This action converts the details and configurations of an existing asset into a quote, allowing for efficient re-use of existing data and ensuring consistency in customer engagements.

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 meet the requirements specified by Felix, the easiest and most effective solution is to use the Auto-Add and No Delete flags for the child product within a product bundle. By setting the Auto-Add flag, the child product is automatically added to the cart whenever the parent product is selected. The No Delete flag prevents users from removing the child product from the bundle once it is in the cart. This combination ensures the child product is always included and retained in the bundle as required, without needing complex configuration rules.

It is true that the prices of all child products roll up to the promotion total, except for optional products that are not being purchased. This means that within a promotion, any child product that a customer chooses to add to their purchase will contribute to the total promotional price. However, if the product is optional and the customer decides not to purchase it, its price will not be included in the final rolled-up total. This setup allows for flexibility in promotions, offering customers choices while maintaining clarity in pricing structure.

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.

The affectivity date for a product's price list entry in Salesforce Industries CPQ controls whether the product displays in the Products list of the cart. This date defines the period during which a specific price list entry is valid. If the current date falls within the affectivity date range, the product and its associated pricing are considered active and will display in the cart's product list. This helps manage the availability of products for sale based on temporal pricing strategies or promotional periods.

Asset-based ordering capabilities in Salesforce Industries CPQ are primarily powered by "FlexCards and OmniScript." FlexCards provide a flexible, configurable interface for displaying asset data, while OmniScript facilitates the scripting of interactive processes that manage and guide the user through asset-based ordering activities. Together, these features allow for dynamic and visually rich asset management and ordering processes, supporting complex business logic and user interactions effectively within the CPQ solution.

When encountering issues with Digital Commerce APIs, such as returning incorrect or no results, the most likely cache to refresh is the VlocityMetadata cache. This cache manages the metadata configurations that underpin the operation of Salesforce Industries applications, including Digital Commerce. Refreshing this cache can resolve issues where outdated or corrupted metadata might be affecting the API responses, ensuring that the most current configurations are used in API operations.

In Salesforce Industries CPQ, product images typically appear in the Cart's Line Item pane. This placement allows users to visually confirm the products they are selecting as they build their order within the cart. Displaying images here enhances user experience by providing a clear and immediate visual reference for each product as part of the order summary and detail review process.

To assign a price to a product in Salesforce Industries CPQ, you must create a price list entry. A price list entry directly associates a specific price with a product and can include details such as currency, discounts, or specific pricing conditions. This is an essential step in setting up products in CPQ because it ensures that each product has a definable, manageable price that can be used in quotes and calculations within the CPQ system.

• D. All of the above: Context Dimension Domain Types in Salesforce Industries CPQ include a variety of formats such as Picklist, Object Lookup, and Type In. These types provide different ways of defining and accessing data for context dimensions, offering flexibility in how rules are configured and how they interact with data within Salesforce.

In Salesforce Industries CPQ (formerly Vlocity), a context mapping is defined as the relational path from a root sObject, such as an Order, to related sObjects, such as Account. This allows the CPQ tool to understand how different data elements relate to each other within the context of the application, enabling dynamic behavior based on relationships between data stored across multiple sObjects. This is crucial for setting up rules that operate based on the broader context of a transaction or customer interaction, rather than isolated data points.

References:

• Salesforce Industries CPQ Developer Guide
• Contextual data modeling in Salesforce CPQ training materials

The component that uses a child catalog code to call APIs and retrieve a response with the appropriate products in Salesforce Industries CPQ is the dcCatalog. This component is specifically designed to interact with product catalogs, using child catalog codes to fetch relevant product information. This enables dynamic and targeted product offerings based on predefined criteria, enhancing the flexibility and responsiveness of the product selection process in guided selling scenarios.

The statement that the Recurring Total and One Time Total prices displayed in the Cart Line Items pane are calculated by any active pricing rules or promotions that have been applied is true. In Salesforce Industries CPQ, pricing rules and promotions are designed to dynamically adjust the prices of products and services based on a variety of factors, such as customer segment, quantity, or promotional offers. These adjustments are reflected in the cart, providing the customer with the most up-to-date pricing information. This capability is critical for accurate pricing communication and ensuring that promotional or contractual pricing is applied correctly at the point of sale.

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

A context scope in Vlocity Context Rules is defined as the relational path from a root sObject (like an Order) to related sObjects (such as Account). This scope determines the extent and reach of the context rule within the Salesforce data model, enabling rules to be applied based on relationships and hierarchies inherent in the data structure. This structure is pivotal in ensuring that rules are applied accurately and relevantly based on the specific relational dynamics of the data involved.

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.

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

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

When Vlocity Cart builds the product list, the type of rule that is processed first is:

• Advanced Rule - Eligibility (C): This type of rule determines whether a customer is eligible for a product based on certain criteria such as customer attributes or service qualifications. Processing eligibility rules first ensures that only relevant and permissible products are presented to the user, streamlining the product selection and configuration process.

In the context of Vlocity's Salesforce CPQ, a context dimension is a design element that links to data stored in sObjects. This link can be direct or calculated using a function, or it can be manually specified during the design-time of the CPQ setup. This feature allows context rules to dynamically adjust to data changes and complexities by using real-time data or predefined criteria.

To automatically decrease the price of a new smartphone over time within Salesforce Industries CPQ: D. Using price list entries with effectivity time frames: This method allows for setting different prices for the same product that automatically become effective at predefined times. By creating multiple price list entries for the smartphone each with different prices and specific start dates, the system can automatically update the price based on the current date.

This approach simplifies managing price reductions over a product’s lifecycle, making it efficient to implement and transparent to users.

References:

• Salesforce Industries CPQ Implementation Guide.
• Examples of using effectivity time frames in Salesforce Industries CPQ price management.

For a developer creating a website to display products for selection by anonymous users, the appropriate API to use is: A. Digital Commerce API - Get Offers By Catalog (getOffersByCatalogCode): This API is designed to retrieve a list of offers, typically product offerings, based on catalog specifications. It is suitable for situations where products need to be displayed publicly, as it can be accessed without requiring user authentication, making it ideal for use with anonymous users.

This API facilitates the easy display of product options to users who are not logged in, supporting scenarios typical in e-commerce and digital marketing platforms.

References:

• Salesforce Industries API Documentation.
• Developer guide on using Salesforce Digital Commerce APIs.

• B. The price category
• D. The charge (amount): Parts of a pricing element in Salesforce Industries CPQ include the 'price category', which classifies the type of pricing or charge being applied (like base price, discount, surcharge), and the 'charge' itself, which is the specific amount of money associated with the pricing action. These components are critical for defining and applying pricing logic in the system.

When the data element is specific to a product or a class of products within Salesforce Industries CPQ, it should be created as an "Attribute". Attributes in CPQ are used to define specific characteristics or properties of a product that can vary based on customer selections or product variations. This enables a more dynamic configuration process where product offerings can be tailored according to specific customer requirements or market segments.

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.

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 statement that the Vlocity Product Console does not support the creation of custom EPC (Enterprise Product Catalog) objects is false. The Vlocity Product Console allows administrators and developers to create and manage custom objects within the EPC. This flexibility is essential for tailoring the product catalog to meet specific business requirements and integrating with other processes in Salesforce Industries CPQ.

Configuration/Validation Rules in Salesforce Industries CPQ do not strictly define relationships between two products, rather, they are used to ensure that the configurations within a quote or cart are valid. These rules are applied to validate individual product options or combinations, but do not establish direct relationships between separate products. Therefore, the statement is false.

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.

In Guided Selling, the HTML template is crucial for controlling the visual layout of the cart, specifically its vertical or horizontal appearance. This configuration affects how products and options are displayed to the user, impacting the user experience and interface design. By customizing the HTML template, developers can ensure the cart aligns with the overall design and usability goals of the Guided Selling process, making it easier for users to navigate and interact with their selections.

When encountering issues with the persistent cart not updating in a Salesforce Industries CPQ guided selling interface, the usual fix involves ensuring that the remote action fetching the cart data correctly targets the expected node in the response JSON. By setting the Response JSONNode to "vlcCart_Top" in the remote action that invokes the getCarts method, Felix can ensure that the correct segment of the JSON is updated with cart details, which should resolve the display issue of showing "0 items in Cart" and missing totals.

In Salesforce Industries CPQ, root entity context scopes are crucial as they define the main entities that can have context rules applied to them. These root entities include Order, Opportunity, Quote, Asset, Account, and Contract. The context scope defines the environment or the entity for which the rule is applicable, acting as the starting point in the hierarchy for evaluating conditions and enforcing rules.

To ensure that a new commercial product appears in Vlocity Cart's product list, several key steps must be taken:

• A. It must have a price: This is fundamental as the product needs to have a price assigned to it in order to be listed and purchasable in the cart.
• E. The Orderable field must be checked: This indicates that the product is available for ordering and is a critical flag for the product's visibility in the cart.
• F. The Active field must be checked: This ensures that the product is currently active and available for selection and purchase in the cart.

These steps ensure that the product is properly configured and recognized by the system as available for inclusion in sales processes.

Vlocity Product Attributes cannot be managed interchangeably through both the Vlocity Product Console and the Salesforce Classic (Aloha) interface. The Vlocity Product Console is specifically designed to handle the complexities and specific features of Vlocity CPQ, including product attributes. Managing these attributes through the Vlocity Product Console allows for utilization of specific Vlocity tools and features that are not available in the traditional Salesforce Aloha interface. Thus, management of Vlocity attributes typically requires using the specialized interface provided by the Vlocity 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.

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.

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.

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

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 create a bundle of products with child products that are discounted in Salesforce Industries CPQ, you would typically manage the discounts at the price list level where the price list entries of those child products are located. By adjusting the pricing directly in the price list entries, you can apply specific discounts to each child product individually. This approach allows for centralized control of pricing and ensures that the discounts are consistently applied regardless of how the bundle is configured or where it is sold.

• A. Update scope setting in the promotion: To manage and potentially delete multiple promotions applied to a bundle in the Cart, the "update scope" setting within the promotion configuration needs to be enabled. This setting allows for the adjustment or removal of individual promotions from a bundle without affecting other applied promotions, providing flexibility in how promotional effects are managed within the cart.

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.

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.

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.

To change the time plan or time policy of a child product in a promotion, it should be adjusted in the pricing element associated with that product. The pricing element is where various terms including durations and conditions related to pricing are configured. Adjusting the time plan or policy here allows these terms to be specifically tailored to individual products within a promotion.

• The pricing element (D): This component of the pricing structure in Salesforce Industries CPQ is crucial for setting and managing temporal terms of pricing adjustments or conditions.

The available product relationship types when creating a Vlocity Configuration/Validation rule include:

• A. Requires: This relationship type specifies that the selection of one product necessitates the selection of another, creating a mandatory linkage between products.
• B. Excludes: This type indicates that the selection of one product precludes the selection of another, enforcing mutual exclusivity in product configurations.
• C. Recommends: This type suggests additional products that may complement or enhance the main product selected, though not mandatory.

These relationship types are key in defining how products interact with each other within a configuration, guiding users towards optimal and compatible product combinations while preventing conflicts.

The best use case for utilizing the Discounts functionality in Salesforce Industries CPQ is to manage quantity-based discounts. This functionality allows for automatic application of discounts when the quantity of a product ordered reaches certain thresholds. This is particularly useful for incentivizing bulk purchases and efficiently managing pricing adjustments based on volume, which is common in both B2B and B2C scenarios.

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.

• C. Includes a configure-price-quote component: The Communications Cloud offers a robust configure-price-quote (CPQ) component, which is integral to managing the complex pricing and configuration needs typical in the telecommunications industry. This CPQ solution supports multi-layered product configurations, bundled offers, and dynamic pricing, essential for both consumer and business segments.

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.

The Discount Duration field is applicable to a contract-based discount. This field is used to specify the length of time a discount will be applied under the terms of a contract. It helps in managing promotions or discounts that have a finite duration, ensuring that they automatically cease after the specified period. This setup is critical for maintaining accurate billing and revenue recognition practices over the duration of a customer contract.

The context scope "Any" allows for the creation of Account and Contract scopes that are agnostic with regard to the root context scope. This means that these scopes can be applied universally, regardless of the specific root context (such as Opportunity, Order, Quote, etc.). This flexibility is crucial for scenarios where Account and Contract details need to be accessed or utilized across various sales processes and stages without dependency on a specific sales context.

QUESTIONNO: 289

Context mappings can be configured from the context dimension or the context scope.

A. True

B. False

Answer: A

Context mappings in Salesforce Industries CPQ can indeed be configured either from the context dimension or the context scope. This dual configurability allows for a more versatile application of context settings, making it possible to adjust mappings based on the specific requirements of dimensions or scopes within the data model. This flexibility is essential for tailoring the system to meet complex business rules and scenarios.

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.

To change the base price of a child product in a promotion to a different price, you would use an "override". Overrides allow you to set a specific price for a product within a promotion, disregarding its listed base price. This functionality is essential for promotions where special pricing is a key aspect of the sales strategy, providing flexibility to offer promotional pricing that may differ significantly from the standard pricing.

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

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.

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.

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.

• D. The display text to show the starting price: When you want to show a starting price for a bundle that includes optional child products, the most straightforward adjustment you can make is to the display text associated with the bundle's pricing. This allows you to communicate to customers that the price shown is the base or starting price, which may increase depending on the selected options or configurations of child products.

The Product List in Vlocity Cart is a dynamic tool that supports effective product management and sales processes. Here are its features:

• B. It is based on a specific price list - The products displayed in the Vlocity Cart can be filtered or determined based on a specific price list, ensuring that the sales team presents the correct pricing and product options to the customer.
• C. It uses Vlocity Rules to display available and eligible products - Vlocity's rules engine can determine which products are shown in the Product List, ensuring compatibility and eligibility based on customer data and other contextual factors.

Explicitly defining a context scope in Vlocity Context Rules, rather than using the ANY context scope, primarily serves to increase rule maintainability. By specifying a particular scope, administrators can better manage and understand the application and impact of context rules. This targeted approach reduces complexity and enhances the clarity of the rule structure, making it easier to update, modify, and audit rules as business requirements evolve. This specificity helps prevent

• A. True: In Salesforce Industries CPQ, rule sets rather than individual context rules are typically applied to products or promotions. This allows for the collective application of multiple rules under a unified framework, facilitating more organized and scalable rule management. Rule sets enable a structured approach to applying business logic across various scenarios, enhancing consistency and control.

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.

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.

In Salesforce Industries CPQ (formerly Vlocity), to make a product not assetizable, two main settings can be adjusted within the Vlocity Enterprise Product Catalog (EPC) and Vlocity Cart:

• Check the Not Assetizable flag in Vlocity EPC: This option directly specifies that the product is not to be treated as an asset post-purchase, thereby excluding it from asset management processes.
• Check the Do Not Assetize flag in Vlocity Cart's line item configuration window: This flag can be set per transaction in the cart configuration, providing flexibility to override the default assetization behavior for specific sales scenarios.

These settings ensure that the product does not get converted into an asset in the Salesforce Industries CPQ system, which is crucial for items that are either consumed upon use or do not require ongoing service management.

• A. True: The expression mode set for a rule set in Salesforce Industries CPQ determines how multiple child rules within that set are applied. The expression mode can dictate whether the rules are applied in an "all must pass," "any can pass," or other logical configurations, affecting how the rules interact and the outcomes of their application.

• A. Products can be set as non-assetizable: In Salesforce Industries CPQ, products can be configured as non-assetizable. This means they do not become customer assets upon purchase. This setting is used for products that do not require post-sale services or tracking as assets, such as disposable items or those that do not require installation or maintenance.

• A. Pricing element adjustment: A pricing element adjustment often involves calculations that directly utilize the base price of a product. These adjustments modify the base price to finalize the selling price based on various factors such as customer segment, purchase volume, or promotional offers.

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

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.