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

In Vlocity Rules, a Qualification entity filter returns a Boolean true/false value. This type of filter is used to determine whether specific criteria are met for a product or a transaction, making it integral to defining eligibility or conditions within business rules.

• Qualification entity filter (B): This filter evaluates specific conditions related to a product or a customer scenario and returns a true or false value based on whether the conditions are met, aiding in decision-making processes such as product eligibility or special condition assessments.

In the context of Vlocity CME, to regenerate the JSON attribute fields for all products in your product catalog, the job to run is:

• A. EPCProductAttribJSONBatchJob: This job is specifically designed to handle the regeneration of JSON attribute fields within the product catalog. It can typically be accessed in training environments such as those provided by Vlocity University through the "Process Attributes" button. This job processes the attributes and ensures they are up-to-date and correctly formatted, which is vital for maintaining the functional integrity of product configurations.

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.

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.

• B. Compatibility: Compatibility rules in Salesforce Industries CPQ are specifically designed to ensure that valid combinations of products are added to the cart. These rules help to validate that selected products can function together or meet certain predefined compatibility criteria, preventing configuration errors and ensuring customer satisfaction.

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

The purposes of the CPQPartition platform cache in Salesforce Industries CPQ are multifaceted, focusing primarily on enhancing performance and efficiency. The cache stores a streamlined version of the product hierarchy, allowing for faster access and navigation within the CPQ tool, which is crucial during complex configuration processes. Additionally, it consolidates the product attribute list, which ensures good performance by minimizing the overhead needed to fetch these details repeatedly during product configuration sessions. This helps in maintaining a responsive user experience by speeding up read operations and reducing the time taken to load and interact with CPQ data.

The Vlocity Enterprise Product Catalog (EPC), part of Salesforce Industries, offers several benefits but particularly:

• A. Integrates the end-to-end ecosystem by combining a complete product, service, and resource model: EPC integrates these elements to create a comprehensive model that supports the entire lifecycle of products and services across different industries. This integration helps organizations manage their offerings more efficiently from a unified platform.
• B. Provides one user interface with common tools, allowing teams to collaborate and rapidly deliver products to market: The unified user interface of EPC facilitates collaboration across different teams by providing common tools that streamline the processes involved in product management, thus accelerating time to market for new and updated products.

These options reflect the core capabilities of Vlocity EPC in enhancing collaboration and integration across business functions.

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.

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.

To control the availability of attribute picklist values based on other attributes within a product configuration, a developer should use the Context Rules Framework. This functionality allows developers to set conditions and rules that include or exclude certain options based on the values of other attributes. For instance, selecting a particular attribute value can dynamically limit the choices available in another attribute, ensuring that only relevant and compatible configurations are possible.

When a developer prepares to test the rule by running the API cache job and it fails, the likely properties causing the issue are: A. Code: Incorrect or problematic code can lead to failures in the API cache job, as it might not be able to interpret or execute the commands correctly. D. Values for caching: If the values specified for caching are incorrect or not properly defined, it can cause the cache job to fail due to misconfiguration or data errors.

Ensuring that the code is correct and the caching values are appropriately set is crucial for the successful execution of API cache jobs in Salesforce Industries CPQ.

References:

• Salesforce CPQ API Developer Guide.
• Troubleshooting Common Issues in Salesforce CPQ.

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

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.

In Salesforce Industries CPQ, entity paths are not required for root scopes. Root scopes inherently refer to the highest level of data context in a model, from which all other scopes derive their context. Therefore, setting an entity path for root scopes is unnecessary as they are already at the highest or base level of the data hierarchy.

In Vlocity Guided Selling, the persistence of the cart is essential to ensure continuity throughout the selling process (B). This persistence means that as a customer or an agent navigates through different steps of the Guided Selling process, the cart retains all items and selections previously made, without needing to restart or lose data between steps. This feature supports a seamless, uninterrupted experience that is crucial for complex configurations and multi-step sales processes.

References:

• User experience design principles in Salesforce Industries CPQ.
• Technical implementation guides for Guided Selling 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.

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.

When using range attribute-based pricing in Salesforce Industries CPQ, the values for each pricing range are specified in the columns of the RangeAttributePricingMatrix. This matrix structure allows for detailed definition of pricing ranges based on specific attributes of a product. Each column can define a range or a specific attribute value, and corresponding pricing adjustments or base prices are defined alongside these values. This setup facilitates complex pricing strategies that vary according to a product's attributes, such as quantity, size, or custom specifications.

In Salesforce Industries CPQ, when performing a Move order from one account to another, certain line item actions are particularly relevant to ensure the correct handling of services or products across accounts. The two actions that will typically be available are: A. Disconnect: This action is used to terminate or disconnect a service from the original account before or after moving it, which may be necessary depending on the contractual or service conditions. C. Change: This allows modifications to the service or product configuration as part of the transfer process to adapt to the new account’s needs or requirements.

These actions help manage the continuity and customization of services or products when they are transferred between accounts.

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

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.

To allow a user to modify an attribute in the Cart's configuration window in Salesforce Industries CPQ, a developer must set the "Run-time Configurable property" for that attribute. This property enables the attribute to be edited during the configuration process within the cart, providing flexibility to the end-user to customize product specifications or choices directly from the cart interface. This is crucial for scenarios where product configurations need final adjustments before completing the order.

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.

In Vlocity Context Rules, when creating a source expression in a context mapping, the correct format to reference an sObject field is %%field%%. This format is used within the Vlocity platform to dynamically insert the value of a field from the context into the rule or mapping. This syntax allows the context rule engine to correctly interpret and retrieve the necessary data from the Salesforce object model, ensuring accurate and relevant rule processing based on the current transactional context.

Vlocity Picklists are used in context rules to specify defined values for context mappings during design-time. These picklists facilitate the setup of context rules by allowing designers to select predefined values from a list, which are then used to configure how rules should apply in specific scenarios. This approach simplifies the configuration process, ensures consistency in rule application, and reduces errors by limiting the values to those predefined in the picklist, thereby making the rules easier to manage and more predictable in behavior.

• D. Shows you where more details are needed to complete the order: The "take-me-there" feature in the Cart is designed to assist users by navigating them directly to areas within the order or configuration that require additional information or correction. This helps streamline the configuration process and ensures that all necessary details are provided before submission.

• B. Check the Do Not Assetize property in the Cart's line Item configuration window
• C. Check the Is Not Assetizable property: Both of these properties control whether a product becomes an asset upon purchase. The Do Not Assetize property can be configured in the line item configuration within the cart to prevent assetization for specific sales. Similarly, setting the Is Not Assetizable property at the product level ensures that the product cannot be assetized regardless of how it is sold or configured in orders.

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.

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 limit the duration of a discount on a child product's price within Salesforce Industries CPQ, you would use "The time plan on the child product's discount." This approach allows you to set specific start and end dates for the discount, directly linked to the child product. It provides a targeted and efficient way to manage promotional pricing on a per-product basis, ensuring that discounts are applied within the intended timeframe without affecting other products or overarching promotions.

In the context of Salesforce Industries CPQ's Guided Selling, ensuring items are updated in the cart typically involves interaction with the cart's API, particularly using methods like putCartItems. This API method is crucial for updating existing cart items with new or altered information as part of the guided selling process, enabling dynamic updates to the cart contents based on user selections or system-driven recommendations.

In Salesforce Industries CPQ, a context key is used primarily within Digital Commerce APIs to describe the customer during rules processing. This allows the system to tailor the application of business rules based on specific customer attributes or other contextual factors. Context keys serve as identifiers that influence rule execution to customize the experience or offerings for different customer segments, helping in dynamic adjustments such as pricing adjustments, visibility of certain product options, or promotions based on the customer's profile or behaviors.

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

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.

In Salesforce Industries CPQ, when viewing adjustments in the Price Details window of a cart line item, the elements that indicate the applied adjustments include: B. The display text of the pricing adjustment: This text shows any changes made to the line item's price due to discounts, promotions, or other pricing rules. C. The display text of the pricing override: This shows when the price has been manually overridden, different from the system-calculated price based on the standard pricing structure.

These display texts provide clear, direct evidence of any modifications to the pricing structure at the line item level, aiding users in understanding how the final prices were determined.

References:

• Salesforce Industries CPQ User Guide.
• Documentation on managing pricing adjustments in Salesforce Industries CPQ.

The Collapse Hierarchy flag when defining a product bundle in Salesforce Industries CPQ is used to:

• Collapse the product hierarchy data key value pairs, in order to improve performance for very large bundles: This flag simplifies the product hierarchy representation by collapsing it into fewer levels. This is particularly useful in enhancing performance by reducing the complexity and depth of product hierarchies during the configuration and pricing processes, especially in large, nested bundles.

By collapsing the hierarchy, the system can process large bundles more efficiently, leading to quicker load times and less strain on the system during complex configuration scenarios.

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

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.

• C. Both of the above: The Communications Cloud encompasses extensive business capabilities, including both order management and contract management.

When a child product's price has been adjusted and the display text is unclear in Salesforce Industries CPQ, the most likely consequence is: B. The price adjustment may not be understood: If the display text does not clearly communicate the nature of the price adjustment, it can lead to confusion about why the price differs from expectations or base pricing. This can affect the transparency and trust in the pricing process.

Ensuring clear and understandable display text for pricing adjustments is essential to maintain clarity and confidence in the sales process.

References:

• Salesforce Industries CPQ Best Practices for UI.
• Documentation on product pricing and adjustments in Salesforce Industries CPQ.

The "Take Me There" icon in Vlocity Cart is designed to streamline the configuration process within the cart. When a user clicks this icon, it navigates them directly to the Line Item Details Modal. This feature is particularly useful in complex configurations where specific line items require additional information or selection choices. The modal not only brings the user to the correct location for making these configurations but also highlights the specific lines that need attention, thereby reducing the effort and time required to identify and address configuration issues.

The persistent cart used in guided selling within Salesforce Industries CPQ is a specialized version of Vlocity Cart. This version is designed to remain active and retain user selections throughout the session, ensuring that data is not lost as users navigate through different stages of the guided selling process. It is tailored to support the dynamic nature of complex configurations and pricing adjustments that are characteristic of CPQ applications.

A layout section in the Vlocity Product Console functions as a Lightning user interface control. This means it serves as a structural component that can be used to organize and display information within the console effectively. Layout sections are part of the broader design and layout capabilities of the Lightning framework, allowing administrators to customize how data and options are presented to users in the Product Console, enhancing user experience and interface organization.

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, the Code field on a Vlocity Picklist is primarily evaluated programmatically by Vlocity CPQ or Vlocity Order Management. The code is a unique identifier used by the system to apply logic and make decisions programmatically:

• Code: Acts as the key identifier that the system uses to reference the selected picklist value in formulas, rules, and scripts. It is crucial for ensuring the correct application of business logic across different modules of the Salesforce Industries suite.

• B. Values for caching
• D. Default Value: These two properties are crucial when configuring a context dimension for a rule in a Digital Commerce guided selling experience. If either the values for caching are not set correctly or the default value is missing or improperly configured, it can lead to issues during the API cache job. Properly setting these properties ensures that the caching mechanism can correctly interpret and store the necessary data for the context dimension, supporting efficient rule execution.

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.

Product cardinality settings in Salesforce Industries CPQ can manage the following use cases: A. Product has a default quantity of 2: Cardinality can be set to specify a default number of products (default cardinality) when added to a cart or bundle, guiding the initial quantity set during the configuration. B. An optional product in a product bundle: Minimum cardinality can be set to 0, allowing a product to be optional within a bundle. This means the product does not have to be selected but can be added by the customer if desired.

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.

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.

In Salesforce Industries CPQ, particularly when working with Vlocity, you can create failure messages within the rule itself. These messages are designed to communicate specific issues to the user, particularly when a product or promotion becomes disqualified within the Vlocity Cart. The message setup in the Rule allows for immediate feedback to users based on the conditions set within the same rule.

Vlocity Cart displays the following five fields in the Line Item Cart pane:

• Quantity, Recurring Charge, Recurring Total, One Time Charge, One Time Total (A): These fields are crucial for providing detailed financial information about each line item:

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. Contract: The createCart method in Salesforce Industries CPQ is used to create a new shopping cart, which can lead to the creation of an Order, Quote, or Opportunity based on the user's progression and selections within the cart. However, it does not directly create a Contract, which typically requires additional steps and a different process or method to formalize the terms and conditions agreed upon between the seller and the buyer.

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

• C. By showing only available and eligible products for customer purchase: Salesforce Industries CPQ's order capture helps ensure a perfect order by displaying only those products that are available and eligible for the customer to purchase. This reduces errors and inefficiencies in the order process, ensuring that customers only see and can order products that meet their specific requirements and are currently available.

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.

In the context of Salesforce Industries CPQ (formerly Vlocity CPQ), the key technologies powering a guided selling experience include Vlocity OmniScript and Vlocity CPQ. OmniScript is a tool used to design digital interaction scripts that guide users through processes in a dynamic, data-driven way, suitable for creating complex guided selling flows. Vlocity CPQ is specifically tailored for configuration, pricing, and quoting processes, essential for a guided selling experience that requires dynamic pricing models and product configurations.

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.

To ensure that an attribute displays in Vlocity Cart's configuration window in Salesforce Industries CPQ, the Run-time Configurable flag needs to be set for the attribute in the Vlocity EPC. This flag makes the attribute available for configuration during the sales process, allowing sales representatives or customers to modify the attribute's value as per the business requirements during the configuration phase.

• Run-time Configurable flag: This is specifically designed to control the visibility and editability of attributes in the configuration window of Vlocity Cart, making it essential for dynamic product customization and configuration.

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.

The time policy for a promotion specifies when promotional pricing applies to the customer account. This determines the periods during which the terms of the promotion are effective, impacting the cost of products or services for the customer if purchased within that specific time frame.

• When promotional pricing applies to the customer account (A): The time policy helps manage the availability and applicability of promotional pricing, ensuring that promotions are only active during their intended timeframe, which is crucial for accurate billing and promotional management.

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.

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.

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

To ensure that the Installation service product's service level attribute is set appropriately based on the customer's SLA level, the correct type of rule in Salesforce Industries CPQ is:

• A. An advanced rule of type Configuration that includes an entity filter on Account.SLA and a product relationship of type Modify Attributes - This rule type allows Felix to configure the product attributes based on the customer's SLA by filtering on the Account.SLA attribute and modifying the product's attributes accordingly.

In Salesforce Industries CPQ, a time plan refers to a scheduling strategy that determines how a product or service is billed over a period of time. One key characteristic of time plans is that they can be prorated, which means the charges can be adjusted based on the actual duration of use within the billing period. This proration enables more flexible and accurate billing for customers who start or end their subscription mid-cycle, ensuring they are only billed for the portion of the service they actually use.

In Vlocity (Salesforce Industries CPQ), the "Rule Fail Level" setting is an option that can be configured within a Rule Set. This setting determines the severity of the response when a rule evaluation fails. Placing this setting within the Rule Set allows administrators to manage how rule failures impact the overall processing of rules in the context of the product configuration or pricing scenarios. This level helps in managing how errors are handled and propagated in the rule evaluation flow, ensuring that the system can gracefully handle different types of rule failures according to business needs.

References:

• Salesforce Industries CPQ Developer documentation on Rule Sets
• Training materials focusing on rule management in Salesforce Industries CPQ

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. Configure: Part of setting up products and services to meet customer needs.
• B. Basket: Represents the collection phase where customers add items they wish to purchase.
• D. Payment: Involves the transaction process where customers provide payment information.
• E. Submit: The final confirmation and submission of the order.
• F. Checkout: The phase where the customer finalizes their selections and proceeds to payment and order submission.

In Salesforce Industries CPQ, the "Done Action Element" (E) in an OmniScript is used to conclude the script and typically has the option to redirect users back to the originating page or another specified endpoint. This ensures that after completing the guided selling process, users can be seamlessly returned to their starting point, maintaining a fluid user experience and integrating the guided process into broader user workflows.

References:

• OmniScript Designer Guide in Salesforce Industries CPQ.
• Training material on user flow integration using OmniScript in Salesforce Industries CPQ.

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

In the line item configuration window of Vlocity Cart, the information that can be modified includes:

• Service account (A) and Billing account (B):

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.

To require a user to select a value for a product attribute during order capture in Salesforce Industries CPQ, the attribute metadata flag Run-time Configurable must be set via the Vlocity Product Console. This setting enables the attribute to be editable at the time of order, allowing the user to specify a value as part of the configuration process.

• Run-time Configurable: This flag is critical for enabling real-time customization of product attributes during the sales process, enhancing flexibility and customer satisfaction by allowing personalized configurations.

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.

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.

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

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 Vlocity, which is now part of Salesforce Industries, object types often utilize an IS-A type of inheritance architecture. This type of architecture is used where a subclass inherits from a parent class, signifying that an object of the subclass is a type of the parent class object. For example, in Salesforce Industries CPQ, you might find that product options inherit characteristics from a generic product class, which allows them to maintain some base functionalities defined in the parent class while adding specific attributes or behaviors unique to the subclass. This IS-A relationship is foundational in object-oriented p

rogramming and is employed within the Salesforce platform to enhance modularity and reusability.

To set a subscription that starts on the purchase date and ends at the end of the cycle in Salesforce Industries CPQ, you need to create a "Time Plan." A Time Plan defines the duration and timing of services or subscriptions, effectively managing how these services are billed or activated over a specific period. This tool allows for precise control over the subscription period, ensuring that it aligns with the purchase and cycle end dates as required.

Attribute-based pricing in Salesforce Industries CPQ can be implemented using the following Vlocity components:

• Pricing Plans: These define how products are priced based on various attributes and conditions, allowing for flexible pricing adjustments based on specific product features or customer selections.
• Calculation Procedures: These are used to define complex pricing logic that can take multiple attributes into account, performing calculations that adjust prices based on predefined rules and conditions.
• Calculation Matrices: These provide a grid-like structure where prices can be set based on combinations of different attributes, offering a straightforward method to manage complex pricing scenarios where multiple variables affect the final price.

These components work together to enable dynamic and flexible pricing strategies that respond to specific product attributes, meeting the diverse needs of businesses and their customers.

Context rules in Salesforce Industries CPQ can indeed determine whether a customer is qualified or disqualified for a promotion. This capability is integral to the CPQ process as it ensures that promotions are only applied to customers or orders that meet specific predefined criteria. This qualification/disqualification process is governed by the rules set up in the CPQ configuration, allowing businesses to automate and enforce their promotional policies effectively.

The Vlocity Cards Framework provides a versatile set of UI components that include cards, layouts, and templates. These components are designed to enhance the visual presentation and usability of data across different Salesforce applications. By using this framework, developers can create highly customizable interfaces that improve user experience and data interaction, particularly in complex configurations such as those found in Salesforce Industries CPQ.