Free Salesforce Industries-CPQ-Developer Practice Exam with Questions & Answers | Set: 5

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.

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

Product cardinality within Salesforce Industries CPQ controls aspects related to product configuration quantities, specifically:

• Is optional (A): This controls whether a product must be included in a configuration or if it can be optionally chosen by the customer.
• Has a default quantity of 2 (D): This sets a predefined quantity for the product when it is added to a configuration, streamlining the process and ensuring consistency for standard orders.

These controls are crucial for defining how products are presented and managed within the CPQ process, influencing both the user experience and the internal logic of product configurations.

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

In the example API call provided (vlocity_cmt/v3/catalogs/Phones/offers?context={"Status":"Active"}), the type of parameter being used is specifying a context. This parameter type is critical for filtering API responses based on specific conditions or contexts, in this case, filtering to include only those phone offers where the status is "Active". This allows the API to return more relevant data tailored to the needs of the application or user.

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

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