Additional Questions Flashcards
What features make-up the Attribution pricing framework?
- Business Rules Engine, and pricing matrices. You can also pass values between price plan steps, set attribute values and prices, and use attribute values in the pricing logic.
- The legacy option is to implement attribute-based pricing using pricing plans, calculation procedures, and standard calculation matrices
What is a Time Policy?
- A time policy indicates when the pricing starts and stops being applied. You can set a time policy for a base price, adjustment, or override.
- For example, you can determine that the pricing starts at the beginning of the month or cycle, or when the product is purchased. In the same way, you can set the pricing to end the last day of the month or at the end of the cycle.
- Time policy requires Start Policy(ex. first day of month, activation start) and End Policy(ex. Cycle end Date, last day of policy)
What is a Time Plan?
- A time plan defines the length of time that pricing applies to a product. Time plans apply to adjustments and overrides for products in bundles or promotions.
- For example, a 2-year subscription to cellular service has a 24-month time plan. Settings for a time plan include the total duration of time and the unit of measure for the duration of time, such as monthly or yearly.
- Time plan requires duration and effective date only
What is the sequence of events that occurs before a price is displayed in the cart?
All attribute pricing steps must occur before the Initialize Pricing Context step; therefore, the sequence must be before 10
What is context scope?
- Context scopes describe the relational path from a root sObject, such as an Order, to related sObjects. Context mappings use context scopes to identify the fields on the sObjects or computed data that is matched with context dimension variables. The Context Rule Service evaluates the information.
- Currently, Vlocity supports the following root context scopes:
- Order
- Opportunity
- Quote
- Asset*
- Any
What is context dimension?
- Context dimensions are variables that describe the possible values to use in a context rule condition. You can reuse context dimensions across multiple rule conditions. Context dimensions are linked to one or more context mappings. The rules engine compares them to the linked context mappings.
- Context dimensions must have aDomain Type, a property that specifies how the rule condition values appear when a user creates the rule condition. Valid domain types are:
- Object Lookup: Select a specific record from an sObject.
- Picklist: Select rule condition values from a Vlocity picklist.
- Type In: Type in free form string values.
What is context mapping?
Context mappings allow the rules engine to compare context dimensions to data stored in an sObject, calculated using a function, or entered during design time within a specified context scope
The context mapping for the AccountType
context dimension should have a Source Expression with no spaces, as shown below. RecordType.Name
What settings should be checked for translation in CPQ?
- Enable Translation in Workbench
- Choose User language - Locale and Language settings
What does the red clock icon indicate in the cart?
Retired products are products that have passed their end of life date, and they are indicated by a red clock icon
What does the yellow clock icon indicate in the cart?
Past products are products that have passed theirSelling End Datebut have not passed theirEnd of Lifedate. They are indicated by a yellow clock icon
What does the green clock icon indicate in the cart?
Future products are indicated with a green clock icon
How do you enable the the “Cost to Margin” feature?
- Enable the feature
- Create pricing element for a price
- Create pricing element for cost
- Configure the price for a product
- Stored in Price Lists
What is the “Cost to Margin” feature in CPQ?
- You can define margin ranges using the pricing plan so that the cost does not exceed the price. This is optional. If you do not set up a validation process, users aren’t notified when a margin range has been violated.
- Margins for each line item can be validated using a LoadMarginRange step in your pricing plan. The LoadMarginRange step invokes a calculation procedure and matrix. This is similar to how attribute-based pricing is implemented using pricing plans.
What are context rules?
- Use thecontext rules frameworkto determine what products, promotions, and prices appear in the Industries Cart. You can specify when to apply a penalty for cancellations and what the penalty will be.
- Qualification rules determine customer eligibility for products, promotions, price lists, price list entries, and pricing adjustments at run time
- Penalty rules determine whether a penalty applies and what the penalty is when a customer cancels a promotion or deletes or disconnects an asset linked to a contract during its commitment period
What are advanced rules?
-Design product compatibility rules based on conditions in order line items and related objects. You can also create advanced pricing, availability, and eligibility rules.
- Compatibility rules: Use product relationships to ensure products ordered in Industries Cart are compatible based on conditions in order line items and related objects. They are also known as Configuration or Validation rules.
- Pricing ruleschange standard pricing and operate on order line items in Industries Cart.
- Availability & Eligibility rulesare legacy rules that display or hide products in Industries Cart’s product list based on conditions in opportunity, quote or order header data or data in related objects such as Accounts or Assets. (Except in certain circumstances, these rules have been replaced by context rules.)
What is the Object Type architecture in Industries CPQ?
Designed as an “Is A” inheritance architecture, meaning you can create relationships between abstractions, where one object type is a subtype of another object type.
How many layers can be included in the product structure of a product or bundle?
Products are bundled using a “Has-A” Containment relationship as either a child or a realization. A product can have one or more product child items (or PCIs), and you can define cardinality for each. PCIs can be a single product or a product bundle, which allows you to create product bundles within product bundles.
What fields have to be populated to see a product in the cart?
- Name
-Product Code - Active = True
- Selling start date (within range)
- Price (assigned)
What background jobs have to be run to see products in cart?
- The Cart uses price lists and Industries CPQ rules to determine which products to display in the PRODUCTS list.
- The price list provides the base or list prices, and they appear in the PRODUCTS list on the left. Once the product is added to the cart, the Cart calculates the price for each item based on any active pricing rules or promotions that have been applied, and so the price in the cart may be
different than the base price.
When to use advanced rules vs context rules?
- Always prefer context rules unless key functionality is not supported.
-Use Advanced Rules to apply to a large number of products (in the thousands)
- Order Line item is not supported by Context Rules
- To automatically add products based on other products in the cart use Advanced Rules
https://help.salesforce.com/s/articleView?id=ind.comms_context_rules_or_advanced_rules__what_type_to_use_.htm&type=5
What is the sales catalog?
A sales catalog in this context refers to a repository or a collection of products or services that a company offers. In Salesforce Industries CPQ and Communications Cloud, the sales catalog is an important component as it holds all the products, services, and bundles that the sales team can use to create quotes for customers.
How to get attribute value to show depending on another attribute field?
- When you associate the attribute with an object type, child object types and products inherit the attribute but can override it.
-At the product level, you can only change the attribute value for a product that was created from the object type. For an attribute that uses a picklist, you can select a different value, but you cannot change or replace the picklist itself.
What is the naming convention for a Context Dimension?
You cannot use spaces in a context dimension name due to rules parsing engine requirements.
How do you modify the display text when there is a price adjustment?
- Product Pricing >Adjustments> Display Text / Display Name
-Display Name: Enter the name of the adjustment or override. This name is shown in the cart.
When should a promotion be implemented vs. a discount?
- Typically, promotions are product bundles with discounts applied to one or more products in the bundle. Designed for a limited time, limited customer group or limited subset of products
-Contractual discounts are typically tied to an account or contract and are used to change
product prices in both current and future orders based upon contracted discount
agreements, thereby maximizing sales intended to be executed in the future.
What is the CPQAppHandler?
CPQ functionality is managed by a global interface called CpqAppHandler. It includes a wide range of methods to perform CPQ processes in Industries CPQ Cart. (These methods are also available as a RESTful API, called the Cart-based APIs.) So, when you need to change the default behavior or processing of a CPQ operation, you create a custom implementation in the CpqAppHandler hook interface
What is the Product Hierarchy Maintenance job?
- This job builds a streamlined version of the product hierarchies in the Data Store sObjects, enabling theRefresh Platform Cache (Full), Refresh PricebookandRefresh Platform Cache (Incremental) job to use the hierarchy data
- After any changes to the product hierarchy or product cardinality in the Vlocity Product Console
- After upgrading Vlocity Communications
- After spinning a new org
- Before running theRefresh Platform Cache (Full) job.
What are some of the maintenance jobs available to an admin?
See picture
What are all of the pricing plan steps?
All attribute pricing steps must occur before the Initialize Pricing Context step;
therefore, the sequence must be before 10.
