Salesforce Industries-CPQ-Developer Salesforce Certified Industries CPQ Developer (SU24) Exam Practice Test

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

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

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

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

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

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

When a search is performed on the product list in the Vlocity Cart, typically the fields that are queried include: A. Product Name: This is a common search field as it allows users to find products based on their names. B. Product description: This field helps in searching for products based on descriptions which might contain key features or benefits. C. Product Code: Often used for searching, especially when users know the specific code or SKU of the product they are looking for.

These fields are commonly indexed and searched to facilitate quick and efficient product lookup in dynamic sales environments.

=======================

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

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.

• C. By clicking the Price Details icon on the line item: Users can understand changes to pricing applied in the cart by clicking the Price Details icon associated with each line item. This action reveals a detailed breakdown of the pricing, including any adjustments, discounts, or special charges that have been applied, providing transparency and clarity on how the final price was calculated.

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

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.

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

In the context of Salesforce Industries CPQ and OM, when an order is canceled and a supplemental order needs to be created, this is done similarly to creating any new order. However, the specific distinction for a supplemental order lies in setting the OrderType field to "Supplemental" from the picklist. This categorization helps in managing and tracking these orders separately, ensuring they are handled correctly through the order fulfillment and management process.

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

• B. False: In Salesforce Industries CPQ, you can have more than one implementation active per interface. This flexibility allows organizations to tailor the CPQ system to different business units, geographic regions, or product lines, each with its own specific settings and customizations.

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.

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.

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

Vlocity Guided Selling is used for enhancing the sales process by guiding sales agents or customers through a streamlined, step-by-step sales journey. This tool is instrumental in reducing average call handling times and training requirements for agents (A), improving the overall customer experience by providing a more interactive and directed sales process (B), and including helpful instructions that aid agents during the sales process (F). Additionally, it's used in training environments to prepare agents before they use the regular Vlocity Cart, ensuring they are familiar with the sales processes and system functionalities (E).

References:

• Salesforce Industries CPQ documentation on Guided Selling.
• Training materials for Salesforce Industries CPQ Guided Selling features.

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.

When an existing customer like Carole White decides to add a new product to her current subscription, such as the Smart Cloud Security product, the action status of the existing subscription (Family Simple Choice Plan) in the Salesforce Industries CPQ context typically updates depending on the nature of the change:

• B. Change - Since Carole is adding a product to her existing plan, the line item action status for the Family Simple Choice Plan will be marked as "Change." This status indicates that the existing asset is being modified rather than being newly added or merely existing without modifications.

In scenarios where a product's price may vary based on its configuration, the most effective way to inform the user about the variable pricing is by changing the display text of the price list entry. This approach ensures that when users are selecting or configuring products, they are clearly aware that the price displayed is subject to change based on their choices of product options and configurations. This method helps set the correct expectations regarding pricing directly on the product page or during the configuration process.

To configure a product bundle where a TV service is included by default but can be removed by the customer, the developer should set the cardinality as follows: D. Minimum Cardinality = 0; Default Cardinality = 1; Maximum Cardinality = 1: This configuration ensures the TV service is automatically included when the bundle is added to the cart (default cardinality), but the customer has the option to remove it (minimum cardinality), and cannot add more than one (maximum cardinality).

In Vlocity Context Rules, the rule type such as Qualification, Penalty, etc., is set at the level of the individual Rule. This setting defines the nature of the rule and its purpose within the broader context of rule sets where multiple rules may interact. The designation of the rule type at this level allows for precise control over how each rule behaves and interacts with others, facilitating a modular and scalable approach to rule management within Vlocity CPQ systems.

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

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.

• E. All of the Above: The Product Console in Salesforce Industries CPQ allows for the management of various entities, including Picklists, Product Attributes, Object Types, and Products. This comprehensive tool is designed to centralize product management tasks, making it easier to update and maintain product-related information.

Evaluation entity filters are not used merely as "internal filters" for qualification entity filters. Instead, evaluation entity filters and qualification entity filters serve different roles within Salesforce Industries CPQ. Evaluation filters are used to process and evaluate data across different contexts and entities based on specific criteria, while qualification filters determine eligibility or appropriateness of specific entries for tasks or promotions, functioning independently of evaluation filters.

In Salesforce Industries CPQ, to indicate the type of price that will be assigned to a product, you create a "Price List Entry". This component specifies the actual price of a product or service within a specific price list. Each price list entry defines one price for a product in a given context, such as a specific market or customer segment. It directly ties the product to its pricing under certain conditions, ensuring accurate billing and quoting.

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

During the order capture process in the Cart within Salesforce Industries CPQ, the attribute category field that displays at run-time is: B. Display Name: This field is used to present a user-friendly name for an attribute category during configuration, helping users understand the options and choices available more clearly. The display name is designed to be visible and informative during the configuration steps in the cart.

These answers provide a verified understanding based on typical configurations and functionalities within Salesforce Industries CPQ.

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.

To differentiate pricing for a product like a smartphone between B2B and B2C customers, the best approach is to assign the product to a pricebook and create two pricebook entries. This strategy allows for distinct pricing structures to be maintained within the same organizational framework, using separate pricebook entries to specify the $999 price for B2B customers and the $900 price for B2C customers. This setup leverages Salesforce’s native functionality to manage differentiated pricing strategies efficiently within its CPQ system.

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 Vlocity Rules, an Advanced Rule - Eligibility can evaluate order line items. This type of rule is specifically designed to assess whether certain criteria are met for products or services within the order, determining their eligibility based on predefined business logic.

• Advanced Rule - Eligibility (C): Such rules are crucial for enforcing business constraints and eligibility criteria on products and services at the line item level, ensuring compliance with business rules and policies.

Vlocity Cart can be invoked for the following sObjects in the order capture process:

• Account, Quote, and Order (D): These sObjects represent key stages and elements of the sales process where the Vlocity Cart is applicable. The cart can be used to manage product selections and configurations directly related to accounts, prepare quotes, and finalize orders.

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

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

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

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.

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.

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

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

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

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.

• 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 (Vlocity) document templates, document sections can be conditionally included based on Advanced Entity Filters and Merge Codes. Advanced Entity Filters allow the template to include or exclude sections based on specific data points or criteria related to the entities being used in the document (e.g., customer data, product types). Merge Codes are placeholders in the template that dynamically pull in data or content based on the underlying data model and specific conditions, allowing for highly customized and relevant document generation.

To ensure that a new product is properly displayed in the shared catalog and can be added to the cart, the following conditions must be met: A. The product must have a price list entry: This is crucial for the product to have a defined price which is necessary for purchase. B. The Active property must be checked: This property ensures that the product is currently active and available for sale. C. The Orderable property must be checked: This indicates that the product can be ordered, which is essential for the product to be added to the cart.

These conditions ensure that the product is correctly set up in the catalog and can be interacted with by customers through the cart system.

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.

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

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

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.

Vlocity CME (Communications, Media, and Energy) offers robust order management functionalities that are essential for handling complex customer interactions:

• A. Asset Based Ordering (ABO) - This functionality allows for management and modification of customer assets directly from the order interface, facilitating the management of existing services and equipment.
• B. Move/Add/Change/Delete or Disconnect (MACD) orders - Vlocity supports MACD functionality, which is crucial for managing lifecycle changes in a customer’s services and subscriptions, allowing for flexibility in service management.

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.

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

• B. Opportunity to quote to order to asset: The correct flow in the order capture process within Salesforce Industries CPQ involves moving from an opportunity, where potential sales are identified, to creating a quote, which outlines the terms and pricing. Once the quote is accepted, it is converted into an order, and finally, once the order is fulfilled, the products involved in the transaction are recorded as assets in the customer's account.

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

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

To apply a flat price to a bundle in Salesforce Industries CPQ, the following steps can be taken: A. Change the child product prices to zero: This ensures that the individual components of the bundle do not contribute additional cost beyond the flat price set for the bundle. D. Change the price of the parent product to the total price of the bundle: This sets the overall price for the bundle, ensuring that the entire package is sold at the intended flat rate.

These steps allow the bundle to be sold as a single unit with a predefined price, simplifying the pricing structure and making it easier for customers to understand the total cost.

References:

• Salesforce Industries CPQ Configuration Guide on Bundles.
• Training materials on managing bundle pricing in Salesforce Industries CPQ.

For Product A with the given dates, by November 22, 2021, the product is past its Selling End Date but has not yet reached its End of Life Date. Therefore, the product cannot be added to a cart or modified since it's no longer available for new sales, but it can still undergo service-related actions. The appropriate action that can be taken is "Disconnect," as this action pertains to service or subscription-based changes, such as terminating or disconnecting a service that has been previously sold or activated, but is not yet at its end of life.

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

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

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

Salesforce Industries CPQ provides various configuration and validation frameworks to ensure the correct application of product rules and relationships. Among the options listed:

• B. DefaultRulesImplementation - This is a basic validation implementation that applies predefined rules in standard scenarios.
• C. ProductRelationshipValidationImpl - This focuses on validating relationships between products as defined in the CPQ setup, ensuring that product dependencies and compatibilities are respected.
• E. DefaultProductValidationImplementation - This implementation provides default validation for product configurations, ensuring that product selections meet predefined criteria without custom coding.

Options A, D, and F are either mislabeled (misspellings in the options) or not standard parts of Salesforce Industries CPQ as known functionalities.

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.

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

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.

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

To troubleshoot issues related to API cache jobs in Salesforce Industries CPQ, the developer should: A. Run Refresh Platform Cache: This clears and refreshes the cache, which can resolve issues stemming from stale or corrupted cache data. D. Run Load API Metadata: This action ensures that all necessary metadata for APIs is correctly loaded and up-to-date, which is crucial for the proper functioning of API-dependent processes.

These actions help in ensuring that the platform's backend processes are synchronized and functioning correctly, thereby resolving issues related to API performance or data integrity.

References:

• Salesforce Industries CPQ System Maintenance Guide.
• Best Practices for API Management in Salesforce CPQ.

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

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.

• A. True: Once an entity filter is created in Salesforce Industries CPQ, it becomes available for use across any rules that need it. This allows for the reuse of filters in different rule scenarios, streamlining the rule creation process and ensuring consistency across various rule applications.

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

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

Before you can create a product attribute in Vlocity, it is necessary to create an attribute category first. Attribute categories organize attributes into logical groups, making it easier to manage and apply them across various products. This categorization is crucial for maintaining structure and relevance in attribute management, especially when dealing with a large number of attributes across different products in Vlocity CPQ.

To ensure that a subscription ends at the end of the subscription plan, you would use a time plan in Salesforce Industries CPQ. A time plan helps in defining the duration and terms of a subscription, including its start and end dates. By specifying these parameters within a time plan, you can accurately control when a subscription should begin and conclude, ensuring that it aligns with the agreed-upon subscription period.

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.

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.

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

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

For the CPQ Partition in Salesforce CPQ, it is recommended to allocate a minimum of 1GB of space. The CPQ Partition is an important component that handles data processing and storage needs specific to CPQ functionalities. Allocating at least 1GB ensures that there is sufficient space to manage the configuration data, price calculations, and other process-intensive operations that are typical within CPQ workflows. This allocation helps in maintaining performance levels and ensuring that the CPQ system can handle the volume of data typically processed during quoting and pricing calculations efficiently.

Before building a promotion, it is crucial to answer the following questions:

• A. How long is the subscription commitment for the promotion?: Understanding the duration of the subscription commitment helps in defining the terms of the promotion and ensures that promotional offers align with customer expectations and business goals.
• C. What billing system is used for each product?: Knowing the billing system for each product included in the promotion is essential for seamless integration and operation. It ensures that all transactions are processed correctly and aligns the promotional terms with the capabilities and constraints of the billing system in use.

These questions help in structuring promotions that are not only attractive to customers but also viable and sustainable from a business operation perspective, ensuring they can be supported by the existing technical and administrative frameworks.

In Vlocity Enterprise Product Catalog (EPC), to allow a user to modify an attribute within the Vlocity Cart’s configuration window, the Run-time Configuration flag must be set for that attribute. This flag enables the attribute to be editable at the point of configuration, facilitating dynamic adjustments by users directly in the cart interface. It essentially marks the attribute as configurable during the sales process, allowing for custom inputs or selections based on customer preferences or requirements.

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 Vlocity's Guided Selling, to set the price list ID for the cart, you need to edit the JSON configuration of the remote action containing the createCart remote method (C). This setup is necessary to define which price list the cart should use right from the beginning, ensuring that all pricing calculations within the cart are based on the correct price list as soon as items are added.

References:

• Salesforce Industries CPQ Developer Guide detailing cart setup.
• Configuration practices for setting up carts in Salesforce Industries CPQ.

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

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

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

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

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