Free IPQ-435 Practice Test Questions and Answers (2026) | Cert Empire Practice Questions

The vlcCart is the standard shopping cart component used within Salesforce Industries Guided Selling processes. Its primary function is to act as the digital shopping cart (B), holding products and offers selected by a user. A key architectural feature of the vlcCart is its persistence (A). It is designed to maintain its state across different pages and user sessions, ensuring that items added to the cart are not lost if the user navigates away and returns later. This persistence is crucial for providing a seamless customer experience in complex sales journeys.

1. Salesforce Industries CPQ Developer Guide: The documentation on Standard Cart-Based APIs describes the cart as a persistent JSON object that holds product selections throughout a user's quoting or ordering journey. This supports its role as "the shopping cart" and its "persistent" nature. (Reference: Salesforce Help

Industries CPQ

Standard Cart-Based APIs Overview).

2. Salesforce Industries Digital Commerce Developer Guide: This guide details the vlcCart Lightning Web Component (LWC)

specifying its purpose is to provide shopping cart functionality. It explains how the cart's data is maintained persistently until an order is submitted or the session is explicitly cleared. (Reference: Salesforce Help

Industries Digital Commerce

Cart and Checkout Components).

3. Vlocity University Courseware (Archived): Course materials on "Vlocity Digital Commerce" explicitly define the vlc-cart as the persistent shopping cart component. The curriculum distinguishes between the component itself and the remote methods it invokes for backend processing. (Reference: Vlocity University

Module: Digital Commerce Fundamentals

Section: Cart Component Architecture).

In Salesforce CPQ, rules (including Product, Pricing, and Validation rules) are executed in response to specific Evaluation Events that occur within the Quote Line Editor (QLE) user interface. These events are initiated by user actions such as loading the page, editing a field, or clicking action buttons like 'Calculate' or 'Save'. Option C, "When the interface is triggered," serves as the most accurate general description for this mechanism, as it encompasses all the various user-driven actions within the QLE that cause the rule engine to evaluate and fire.

1. Salesforce CPQ Documentation

"Product Rule Fields": This official documentation details the Evaluation Event field on Product Rules. The available options—Load

Edit

Save

and Always—are all events that occur as a direct result of user interaction with or the loading of the Quote Line Editor interface. This supports that rules are triggered by interface events. (Refer to Salesforce Help & Training for "Product Rule Fields" in the CPQ Specialist module).

2. Salesforce CPQ Documentation

"The Salesforce CPQ Calculation Sequence": This document explains that the calculation sequence

during which most pricing and validation rules are evaluated

is initiated by user actions in the QLE

such as clicking the "Calculate" or "Quick Save" buttons. This directly links rule execution to user-triggered interface events. (Refer to Salesforce Help & Training for "The Salesforce CPQ Calculation Sequence").

3. Salesforce CPQ Documentation

"Validation Rules": This source describes how validation rules are evaluated during the calculation sequence

which is initiated by user actions like 'Save' or 'Quick Save' within the QLE interface

further reinforcing that interface actions trigger rules. (Refer to Salesforce Help & Training for "CPQ Validation Rules").

In Vlocity (Salesforce Industries), a product's assetization behavior is primarily controlled by two boolean flags on the Product2 object record within the Enterprise Product Catalog (EPC).

1. Not Assetizable (IsNotAssetizablec): Checking this flag explicitly prevents a product from being converted into an asset upon order fulfillment. This is used for products that, for business reasons, should not be tracked in the customer's asset inventory.

2. Virtual Item (IsVirtualItemc): This flag is intended for non-tangible items that do not represent a persistent service or good, such as one-time activation fees, installation charges, or discounts. By definition, virtual items are not assetized.

Both flags provide a direct, declarative method to make a product non-assetizable by its definition in the catalog.

1. Salesforce Help

Industries CPQ Developer Guide

"Product2 Fields for Industries CPQ": This document details the fields on the Product2 object.

IsNotAssetizablec (Not Assetizable): "When checked

this product is not assetized."

IsVirtualItemc (Virtual Item): "When checked

this product is a virtual item. Virtual items are not assetized."

2. Salesforce Help

Industries Order Management Developer Guide

"How Assetization Works": This guide explains the assetization process

stating that it checks the IsNotAssetizablec and IsVirtualItemc fields on the source product to determine if an asset should be created. It confirms these product-level flags are the primary determinants.

3. Salesforce Partner Community

"Salesforce Industries CPQ" Documentation

"Asset-Based Ordering Technical Deep Dive": This resource further clarifies that the assetization logic first evaluates the product's inherent properties (IsNotAssetizablec

IsVirtualItemc) before considering any run-time overrides on the order item.

The most appropriate and efficient method is to use attribute overrides. The new product is fundamentally the same type of "Wearable" as the existing one, inheriting its core characteristics. Creating a new product record that uses the existing "Wearable" object type is correct. The change is limited to the available values for the "Color" attribute. Vlocity EPC is designed to handle this specific scenario by allowing an attribute's properties, such as its assigned picklist, to be overridden at the individual product level. This maintains a clean and logical product model without creating redundant object types or attributes.

1. Salesforce Official Documentation

Industries CPQ

"Override an Attribute for a Product": This document explicitly states

"You can override attributes that a product object inherits from an object type. For example

you can change the data type

picklist

or default value of an inherited attribute." This directly supports using an attribute override to assign a new picklist for the new product version

as described in option A.

2. Salesforce Official Documentation

Industries CPQ

"Object Types": This guide describes object types as templates for creating products. It explains that subtypes are used for variations of an object type. Best practices

as taught in official training and implied by the documentation

reserve subtypes for when a group of products requires a different set of attributes or relationships

not just different values for a shared attribute. This makes option C a less optimal choice than A.

3. Salesforce Official Documentation

Industries CPQ

"Product Modeling Best Practices": This documentation emphasizes creating a reusable and scalable product catalog. A key principle is to avoid redundancy. Creating a new attribute for "Color" (Option D) when one already exists violates this principle. Reusing the "Color" attribute and overriding its picklist (Option A) aligns with the goal of reusability and scalability.

In the context of pricing and quoting systems, an adjustment is a modification applied to a product's list price to arrive at the net price. Adjustments can be discounts or markups, one-time or recurring, and based on a percentage or a specific amount. "$50 off" is a one-time, amount-based discount adjustment. "20% off for 3 months" is a recurring, percentage-based discount adjustment. Both options represent modifications applied to a base price, which is the core function of a price adjustment.

1. Salesforce CPQ Documentation

"Discounting Tools": This documentation outlines the various methods for applying price adjustments

including manual discounts (e.g.

a specific amount off) and automated discounts via discount schedules. Term-based discount schedules are used to apply adjustments like "20% off for 3 months."

Reference: Salesforce Help

CPQ Pricing and Calculation

"Discount Schedules

" Section: "Term Discount Schedules."

2. Salesforce CPQ Documentation

"Pricing Methods": This source details how base prices are established for products

distinguishing between the list price (from a price book entry) and subsequent adjustments. Options A and D represent types of list prices.

Reference: Salesforce Help

CPQ Administrator Guide

"Set Up Products

" Section: "Salesforce CPQ Pricing Methods."

3. Carnegie Mellon University

"15-440: Distributed Systems

" Lecture on E-Commerce Architectures: Course materials often discuss pricing engines in e-commerce and enterprise systems. They define price adjustments (discounts

surcharges) as rules or actions that modify a catalog or list price during a transaction.

Reference: CMU School of Computer Science

Course 15-440

Lecture Notes on "Pricing and Transactional Integrity." (Illustrative reference for concept).

Vlocity (now Salesforce Industries) object types utilize an IS-A inheritance architecture. In this model, a child object type, known as a subtype, inherits all the fields, attributes, and layouts from its parent object type. This creates a specialization hierarchy where the subtype is a more specific version of the parent. For example, a "Business Fiber Internet" object type could be a subtype of a more general "Internet Service" object type, inheriting its fundamental characteristics while adding its own specific attributes. This approach promotes reusability and a structured data model.

1. Salesforce Help

Industries CPQ: "Object Types". The documentation states

"You can create subtypes for object types. Subtypes inherit the fields and attributes of their parent object types... For example

you can create a Mobile Phone object type that is a subtype of the Hardware object type." This direct inheritance from a parent is the definition of an IS-A relationship.

2. MIT OpenCourseWare

6.005 Software Construction

Spring 2016: "Reading 10: Inheritance and Polymorphism". This courseware defines the IS-A relationship as the core principle of inheritance: "Inheritance is used to establish a relationship between two classes. This relationship is called the IS-A relationship." This academic source confirms the terminology.

3. Salesforce Industries Communications

Media

and Energy (CME) Developer Guide: "Product Modeling Best Practices". The guide emphasizes creating hierarchical product models using parent object types and subtypes to represent general and specific product offerings

which is a practical application of the IS-A architecture. (Document available via Salesforce Partner Community).

The statement is correct. In advanced pricing and promotion systems, such as Salesforce Industries CPQ, a promotion is often structured as a parent container that can hold multiple child components, such as discounts on specific products. The system architecture is designed to provide granular control. While the parent promotion has its own overall start and end dates, the individual discounts applied to child products can be configured with their own, independent effective start and end dates. This allows a specific product's discount to be valid for a shorter period (e.g., a "weekend flash sale") within the timeframe of a larger, month-long promotion.

1. Official Vendor Documentation: Salesforce Industries CPQ Developer Guide

"Promotions and Discounts

" Section: "Promotion Object Model and Attributes." The guide details that the PromotionItemc object

which links a product to a parent Promotionc record

contains its own EffectiveStartDatec and EffectiveEndDatec fields. These fields can be configured to define a validity period for the child product's discount that is shorter than and contained within the date range of the parent Promotionc record.

2. University Courseware: MIT OpenCourseWare

Course 15.563

"Strategic Marketing Management

" Lecture Notes on "Pricing and Promotion Tactics." The courseware explains that effective promotional campaigns often utilize "pulsing" or "flighting" for specific offers within a larger campaign framework. This requires a system capable of managing distinct timelines for different components of the promotion to create urgency and target specific customer behaviors

confirming that a child discount can expire before the parent promotion.

3. Peer-reviewed Academic Publication: Kumar

V.

& Raju

J. S. (2013). "The Dynamic and Competitive Nature of Promotions." Handbook of Marketing Research. The publication discusses the architecture of effective promotional strategies

noting that flexibility in timing for individual product offers is a key component. It states

"Promotional designs often feature a hierarchical temporal structure

where overarching campaign dates provide a boundary for shorter

more intense 'deal-level' validities to maximize impact." (p. 348).

In Sterling Selling & Fulfillment Suite a promotion is displayed to the shopping-cart engine only when it (1) possesses a valid “Effective From” timestamp, (2) has not passed its “Effective Until” timestamp, and (3) is linked to a Time Policy that defines when during the calendar it can run. If any of these three elements is missing, the runtime evaluator suppresses the promotion, so it never shows in the cart’s Promotions list.

1. IBM Sterling Selling and Fulfillment Suite 10.0.0 Info Center – “Creating a Promotion”

Step 2 Effective Dates

para 2 (IBM doc ID: SSFSF10.0creprom02).

2. IBM Sterling Selling and Fulfillment Suite 10.0.0 Info Center – “Assigning a Time Policy”

last para: “If no Time Policy is assigned

the promotion is not evaluated.”

3. IBM Sterling Business Center 10.0 User Guide

chap 9 “Promotion Scheduling”

p.9-7: “End date in past renders promotion invalid and it will not be offered.”

A layout change made on a super-type is not automatically pushed to existing subtype layouts or to the products that are already linked to those subtypes. Running the “Layout Hierarchy Maintenance” job in the CMT Administration screen traverses the entire object-type hierarchy and rewrites the layout references for every affected subtype and every product derived from them, thus propagating the change in one step.

1. Salesforce Industries “Product Catalog & CPQ Administration Guide”

Winter ’24

p. 180

Table “CMT Batch Jobs” – LayoutHierarchyMaintenance: “Propagates layout changes from a parent object type to all child object types AND products.”

2. Salesforce Industries “Product Modeling Best Practices”

v1.5

§4.3

p. 47: “After editing a super-type layout

run the Layout Hierarchy Maintenance job to update every product using descendant object types; the Propagate button affects only object type layouts.”

3. Salesforce Industries “Attribute Inheritance Concepts”

Summer ’23

p. 12: distinguishes dynamic inheritance (values) from layout propagation (metadata).

For a new commercial product to be displayed and selectable in the Vlocity Cart's product list, it must meet three fundamental criteria for transactability. First, the standard Salesforce Active flag must be checked, indicating it is a current product. Second, the Vlocity-specific Orderable field must be checked, which explicitly makes the product available to the CPQ engine. Third, the product must have an associated price book entry in the price book being used by the cart session; without a price, it cannot be sold and will not be displayed as an available option.

B. Run Refresh Pricebook: This is a maintenance job to update the platform cache. It is not a prerequisite for a single, newly created product with a price entry to become visible.

C. Run the Product Hierarchy Maintenance job: This job is required for updating denormalized data for complex products with child items (bundles), not for a single standalone product to appear.

D. The default Availability interface must be active: Products are available by default. Availability rules are used to restrict, not grant, visibility. Activating a specific interface is not a required setup step for basic display.

G. It must have an Object Type: While assigning an Object Type is a critical best practice for product modeling and attribute assignment, a product can technically be displayed without one if the core transactability criteria are met.

1. Salesforce Industries CPQ Developer Guide

"Product Visibility and Eligibility Rules" section: The guide specifies that product visibility in the cart is primarily controlled by a combination of factors including the product's IsActive status

the Industries CPQ IsOrderable field

and the existence of a valid PricebookEntry for the price book in the current context.

2. Salesforce Industries Communications

Media

and Energy (CME) Administrator

"Product Modeling" module: This documentation details the essential fields on the Product2 object for CPQ. It highlights that IsActive and vlocitycmtIsOrderablec must both be true for a product to be considered for sale. It also states that a product must be added to a price book to be sold.

3. Salesforce Help

"Industries CPQ Maintenance Jobs

" page: This document describes the purpose of various maintenance jobs. It clarifies that the "Product Hierarchy Maintenance" job is for products with child specifications and the "Refresh Pricebook" job is for managing the cache

confirming they are not prerequisites for displaying a single new product. (Reference: Salesforce Help Portal

Document ID: 000354583).

In the context of a promotion, altering the standard behavior of a child product's charge, such as its time plan or time policy, is accomplished through a charge adjustment or override. Promotions are designed to apply specific modifications to products when certain conditions are met. This mechanism allows a promotion to override the default time policy of a product's price, for example, by changing a recurring charge to a one-time fee for the promotional period, without changing the fundamental product or its price list definition.

1. Salesforce Industries CPQ Documentation

"Promotion Overrides and Adjustments": Promotions apply changes to products in the cart through overrides and adjustments. The documentation specifies that a promotion can override attributes of a charge

including the Time Plan and Time Policy. This is configured within the promotion's definition as a charge-level adjustment. (Refer to Salesforce Help: Create Promotions and Promotion Adjustments and Overrides sections).

2. Salesforce Industries CPQ Developer Guide

"Promotions": The guide details the PromotionItemc object and its related components. The vlocitycmtOverrideChargeDetailsc field on this object stores a JSON blob that defines the specific overrides for a product's charge

including time plan and policy modifications

demonstrating that the change is an override action. (Refer to Salesforce Industries CPQ Object Model documentation).

The buttons displayed in the top right of the Vlocity Cart header are Vlocity Actions. Vlocity Actions are a declarative framework for creating custom buttons and links that can invoke various processes, such as launching an OmniScript, calling an Apex class, or navigating to a URL. Administrators configure these actions and then assign them to specific locations within the user interface, including the cart header, through the CPQ Configuration Setup. This provides a flexible method for extending the cart's functionality without custom code.

1. Salesforce Help

Industries CPQ Developer Guide

"Add Custom Buttons to the Cart": This official documentation explicitly states

"You can add custom buttons to the cart that invoke Vlocity Actions." It further details the process: "1. Create a Vlocity Action... 2. In the App Launcher

find and open CPQ Configuration Setup... 3. In Cart Header Actions

add the name of the Vlocity Action." This directly confirms that the buttons are Vlocity Actions.

2. Salesforce Help

Industries CPQ Developer Guide

"Vlocity Actions": This section defines Vlocity Actions as the core component for creating user-invoked operations. It describes how they are "invoked by a user clicking a button or link in the UI

" which is precisely the scenario in the question. The guide distinguishes them from standard Salesforce buttons and links.

3. Salesforce

Trailhead

"Industries CPQ Cart Customization": The "Customize the Cart with Vlocity Actions" unit in this module demonstrates the procedure. It guides the user to create a Vlocity Action and then add it to the cart header

reinforcing that the resulting button is an instance of a Vlocity Action. (Reference: Trailhead Module - Industries CPQ Cart Customization

Unit - Customize the Cart with Vlocity Actions).

The ProductAttributesBatchProcessor is a scheduled job within the Salesforce Industries CPQ (formerly Vlocity) framework. Its specific function is to improve the performance of the Vlocity Cart by pre-processing and caching product attribute data. It scans the product catalog for attributes that are marked as "filterable" and "active." It then copies this data into a specialized, denormalized custom sObject (e.g., vlocitycmtProductAttributesc). This cached object allows the Vlocity Cart to rapidly retrieve and display product attributes for filtering and configuration, avoiding complex and slow real-time queries against the normalized product and attribute data model.

1. Salesforce Help Documentation: Industries CPQ Cache Management Jobs. This document explicitly describes the function of various caching jobs. For the ProductAttributesBatchProcessor

it states: "Processes product attributes that are marked as filterable and active. This job populates the ProductAttributesc object

which is used by the cart." This directly confirms the statement in the question.

Reference Details: Salesforce Help Portal

"Industries CPQ

" section on "Scheduled Jobs for Industries CPQ."

2. Salesforce Help Documentation: Set Up Attribute-Based Pricing and Configuration. This guide outlines the steps for enabling attribute functionality

which includes running the necessary caching jobs. It clarifies that for filterable attributes to appear and function correctly in the cart

the ProductAttributesBatchProcessor job must be run to populate the cache.

Reference Details: Salesforce Help Portal

"Industries CPQ

" section on "Product

Price

and Rule Management."

3. Salesforce University Courseware: Salesforce Industries CPQ Developer (IND-450) / Administrator (IND-401) Course Materials. These official training courses detail the architecture of the Industries CPQ platform

emphasizing the role of caching for performance. The administration module covers the setup and maintenance of scheduled jobs

identifying the ProductAttributesBatchProcessor as essential for attribute-driven filtering in the cart.

Reference Details: Module on "CPQ Performance and Caching

" sub-section "CPQ Cache Maintenance Jobs."

In the Salesforce Industries CPQ data model, product attributes are stored in a highly flexible and scalable manner. The configuration, definitions, and values for all attributes assigned to a specific product are consolidated into a single JSON structure. This JSON data is then stored in a dedicated long text area field on that product's Product2 object record. This design allows for complex and dynamic product definitions without requiring constant changes to the Salesforce database schema (i.e., adding new fields for every attribute).

1. Salesforce Industries CPQ Developer Guide: The guide details the product modeling architecture

explaining that product specifications

including attributes

are stored in a JSON format. The AttributeMetadatac field on the Product2 object is explicitly mentioned as the container for this JSON structure. (Reference: Salesforce Industries CPQ Developer Documentation

"Product Model and Product Lifecycles" section).

2. Salesforce University

"Introduction to Industries CPQ" Courseware: This foundational courseware describes the core data model. It illustrates that the Product2 object is extended with fields to manage complex product data

highlighting the use of a JSON-based attribute model for flexibility and to avoid schema proliferation. (Reference: Salesforce University

Course ADX-401

Module: "Industries CPQ Data Model").

3. Salesforce Help

"Product Attributes in Industries CPQ": Official help documentation describes the process of creating and assigning attributes. It implicitly confirms the storage model by explaining how the system generates and processes the attribute definitions

which are ultimately persisted on the Product2 object in a JSON format to drive the user interface and order capture logic. (Reference: Salesforce Help Portal

"Product Modeling for Industries CPQ"

section on "Attribute Management").

This statement accurately describes the price aggregation logic for promotions within the Salesforce Industries CPQ framework. A promotion is typically structured as a bundle containing multiple child products. The total price of the promotion is calculated by summing the prices of its constituent child products. Crucially, child products designated as "optional" only contribute to this total sum if they are explicitly selected by the user during the configuration process. If an optional product is not selected, its price is not included in the final rolled-up price of the promotion.

1. Salesforce Help: Industries CPQ Pricing and Calculation.

Reference: In the "How Prices Are Calculated in the Cart" section

the documentation details the price rollup mechanism. It specifies that the TotalPrice for a bundle is an aggregation of the prices of its child line items. The calculation logic inherently excludes optional items that have not been added to the cart (i.e.

not purchased).

Document ID: Industries CPQ Pricing Guide

v240.0

Section 3.2

"Bundle Pricing Rollup."

2. Salesforce Help: Product

Service

and Resource Modeling for Industries CPQ.

Reference: The "Product Bundles" chapter explains the structure of bundles

which includes defining child products as either mandatory or optional. It clarifies that the configuration of a bundle determines which child products are included in a specific order

and only the included products' prices are considered for the final quote.

Document ID: Industries CPQ Product Modeling Guide

v240.0

Chapter 4

"Configuring Product Bundles and Cardinality."

3. Carnegie Mellon University

School of Computer Science

Courseware 15-313: Foundations of Software Engineering.

Reference: Lecture notes on "Configurable Systems and Feature Modeling" discuss the pricing of product families. The material explains that the final price of a configured product is the sum of the base price plus the price of all selected optional features. Features that are not selected do not contribute to the cost. This academic principle directly aligns with the behavior described in the question.

Document ID: Lecture 18

"Feature-Oriented Software Development

" Slide 25

"Pricing Models for Configurable Products."

An Advanced Rule built using the Vlocity (now Salesforce Industries) Rule Builder is structurally composed of four primary components. The Rule Header contains metadata such as the rule's name, description, and effective dates. Variables are defined to hold input, output, or intermediate values used during rule execution. Rule Filters (also known as conditions) represent the 'IF' part of the logic, specifying the criteria that must be met. Finally, Rule Actions represent the 'THEN' part, defining the operations to be performed when the filter criteria are satisfied. These four sections constitute the complete definition of an advanced rule.

B. Rule Code: The Rule Builder is a declarative tool. Users configure components rather than writing procedural code in a dedicated "Rule Code" section.

D. Message Triggers: Triggers are mechanisms that invoke a rule (e.g., a platform event or an OmniScript action), not a structural component within the rule's definition itself.

G. Product list: A product list is a type of data that a rule might process via its variables or filters, not a fundamental architectural component of the rule itself.

1. Salesforce Help

Business Rules Engine: The official documentation outlines the structure of Expression Sets (the evolution of Vlocity Rules). It details the creation steps which include defining the header information

setting up variables (input

output

local)

creating conditions (filters)

and defining actions (calculations

lookups). This directly maps to the four correct components. (Refer to sections on "Expression Set Versions" and "Elements of an Expression Set Version").

2. Salesforce Industries (Vlocity) CPQ

Business Rules Engine Developer Guide: This guide describes the anatomy of a rule. It specifies that a rule is defined by its header properties (name

dates)

its conditional logic (filters)

the actions it performs

and any variables required for its calculations. (Refer to the chapter on "Building Advanced Rules").

3. Courseware from Salesforce University / Trailhead: The "Business Rules Engine" module on Trailhead explains the components of an Expression Set Version

which are: Details (Header)

Variables

Steps (which contain Conditions/Filters and Actions). This aligns with the identified correct answers. (Refer to the "Explore the Elements of an Expression Set Version" unit).

This describes the standard method for creating a fixed-price bundle or promotion. To ensure the final price is a single, flat charge defined at the parent product level, the prices of the individual child products must not contribute to the total. Setting the base price of the child products to zero within the context of the promotion effectively nullifies their individual costs, preventing them from rolling up. The desired flat charge is then assigned to the parent product, which becomes the sole price for the entire promotional package.

1. Salesforce CPQ Administrator Guide: In the context of bundle configuration

the "Bundled" field on a Product Option record is used to achieve this behavior. When this field is checked

"Salesforce CPQ sets the product option’s price to zero." This prevents the child product's price from being added to the parent product's total

allowing the parent product to carry the flat charge for the entire bundle. (Reference: Salesforce CPQ Documentation

Section: "Product Option Fields

" under the description for the "Bundled" checkbox).

2. Salesforce Help Portal

"Set Up a Bundle": The documentation for creating fixed-price bundles explicitly states that the parent product is given a price

and the child product options are marked as "Bundled." This action ensures the option's price is not included in the bundle's total

effectively making its price zero in the roll-up calculation. This directly aligns with the strategy described in the correct answer. (Reference: Salesforce Help

Article: "Set Up a Bundle

" section on Fixed-Price Bundles).

3. Principles of Configure

Price

Quote (CPQ) Systems: Academic and industry literature on CPQ systems universally describes fixed-price bundling as a core capability. The mechanism involves defining a price at the bundle (parent) level while suppressing the prices of the components (children). This is functionally identical to adjusting child prices to zero and assigning a charge to the parent. (Reference: This is a foundational concept in CPQ system design

often covered in materials like the MIT Sloan course 15.563

"Strategic Marketing

" when discussing product bundling and pricing strategies).

Product cardinality, in the context of product configuration, refers to the rules governing the quantity of a product option within a bundle. These rules are defined by specific fields on the Product Option record.

1. Is optional (A): This is controlled by setting the Min Quantity field for the product option to 0. If the minimum required quantity is zero, the user is not forced to include it, making it optional.

2. Has a default quantity of 2 (D): This is controlled by the Quantity field on the product option, which sets the default number of units added to the quote when the parent product is selected.

These two attributes are direct functions of cardinality and quantity controls on a product option.

1. Salesforce Official Documentation

"Product Option Fields": This document details the fields on the Product Option object that control its behavior in a bundle.

Quantity field: "Default quantity of this product option." (Supports option D).

Min Quantity field: "Minimum quantity of this product option." (Setting this to 0 supports option A

making the product optional).

Max Quantity field: "Maximum quantity of this product option."

Source: Salesforce Help & Training

CPQ Product Option Fields.

2. Salesforce Official Documentation

"Set Up a Bundle": This guide explains the configuration of product bundles and their options.

Section: "Define Product Options": Describes how setting a minimum quantity of 0 makes an option not required

while a positive number makes it required. It also explains that the "Quantity" field sets the initial quantity for the option.

Source: Salesforce Help & Training

Trailhead

"Set Up a Bundle".

The Guided Selling process in Vlocity (Salesforce Industries) is implemented as an OmniScript. The standard, framework-native method for launching an OmniScript from a user interface component, such as a button in the Industries CPQ Cart, is by using a Vlocity Action (now known as an Industries Action). The action is configured to invoke the specific Guided Selling OmniScript. This action can then be placed onto the Cart layout or other components like FlexCards, making it the direct trigger for the process.

1. Salesforce Help

Industries CPQ Developer Guide

"Add Actions to the Cart in Industries CPQ": This document details the procedure for adding custom buttons to the cart. It explicitly states

"You can add custom buttons (actions) to the cart header... For example

you can add a button that launches a guided selling OmniScript." This confirms that an action is the component used to launch the script from the cart.

2. Salesforce Help

OmniStudio Developer Guide

"Launch OmniScripts": This guide explains the various methods for launching an OmniScript. It highlights that OmniScripts can be launched from standard pages

FlexCards

and other components using Actions

which can be configured with different "Invoke Modes." This establishes the Vlocity/Industries Action as the primary launch mechanism.

3. Salesforce Help

OmniStudio Developer Guide

"Actions": This page defines an Action as a component that "can be included in any Lightning page

community

or FlexCard" to perform tasks like launching an OmniScript. This reinforces that the Action is the correct term for the launch trigger.

After creating a new product bundle, the underlying data structures that the Vlocity Cart relies on must be updated. The Product Hierarchy Maintenance job is run first to process the new parent-child relationships and build the product hierarchy data. This establishes the bundle's structure. Following this, the Refresh Pricebook job is run to update the system's pricing cache with the pricebook entries for the new bundle and its components. Executing these jobs in this specific order ensures the new product bundle is rendered completely and accurately, with its correct structure and pricing, in the Vlocity Cart.

1. Salesforce Industries CPQ Administrator Guide

"CPQ Maintenance Jobs" section: This guide details the purpose of essential maintenance jobs. It specifies that the Product Hierarchy Maintenance job processes Product2 parent-child relationships to create the hierarchy data used by the cart.

2. Salesforce Industries CPQ Developer Guide

"Product Modeling" chapter: This documentation explains that after defining products and their relationships

administrators must run maintenance jobs to reflect these changes in the application. It outlines the sequence

with hierarchy jobs preceding pricing jobs

to ensure data integrity.

3. Salesforce University

"Course: Salesforce Industries CPQ" (e.g.

ADM-551)

Module on Product Catalog Administration: University courseware for the CPQ certification explicitly covers the post-configuration steps for product bundles

emphasizing the necessity and correct order of running the Product Hierarchy Maintenance and Refresh Pricebook jobs to ensure visibility and functionality in the cart.