Download PDF
Download page Version_15.2090 (June '23).
Version_15.2090 (June '23)
New Features
The following features are new to CPQ in this release.
Copy Bill To and Ship To Accounts from Assets to Renewal Quotes and Renewal Agreements
When Renewal Execution Mode = Auto, renewal quotes and renewal agreements now inherit the Bill To and Ship To account values from the parent quotes and parent agreements.
Display Error Messages from Constraint Rules as Hyperlinks on Configuration Page or Cart Page
For constraint rules where Action Type = Exclusion and Product Scope = Product, CPQ now displays validation error messages from constraint rule actions as hyperlinks on the Configuration page or Cart page.
Control Lines Items Sent in the Custom Revalidation Request Object
CPQ introduces a new admin setting APTS_CustomRevalidationLinesThreshold to control line items sent in the custom revalidation request object. This setting allows you to handle revalidation with callback when the cart has a large number of line items for revalidation.
Enhancements
The following section describes the existing features that are changed (or are no longer supported) in this release.
Updated Pages Used as Default in Flow Settings
The default pages available for you to define a user interface flow for CPQ are now updated.
Validate Min and Max Price at Price List Item in CPQ Admin
While creating a price list item, after entering minimum price (Min Price/Net Adj %) and maximum price (Max Price/Net Adj %) both, when you click Save, CPQ validates whether the maximum price is greater than the minimum price. If this validation passes, CPQ allows you to save the details. Otherwise, CPQ displays an error message "Max Price/Net Adj % cannot be less than Min Price/Net Adj %".
Removed Non-Supported Values from the Adjustment Applies To Field of a Price Rule
The non-supported picklist values are no longer visible on the Adjustment Applies To drop-down while defining a price rule. This field displays only "Base Price" and "Base Extended Price" options now.
Removed Non-Supported Values from the Min/Max Price Applies To field of a Price List Item
The non-supported picklist value of "Base Extended Price" is no longer visible on the Min/Max Price Applies To drop-down while defining a price list item. This field displays only "Base Price" and "Extended Price" options now.
However, the administrator must manually remove the "Base Extended Price" value from Setup > Create > Objects > Price List Items (object) > Min/Max Price Applies To (field).
Use Attributes from PAV Extension for Defaulting Price and Quantity
In the CPQ Admin UI, administrators can now use attributes from the out-of-the-box product attribute value (PAV) extension objects for defaulting price and quantity. When the administrators select "Product Attribute" from the Default Quantity From or Default Price From drop-down, they can select any field defined on the PAV extension objects from the:
- Default Quantity Field drop-down for defaulting quantity
- Default Price Field drop-down for defaulting price
CPQ does not support custom PAV extension objects.
Display Adjustments Applied on PLIs with Negative Pricing on the Cart
If a price list item has negative pricing and the sales representative applies an adjustment at the line-item level or summary level on the cart, CPQ displays the actual adjustment applied on the product with negative pricing on the Adjustment column. Earlier, CPQ displayed the adjustment applied on the product with negative pricing on the Adjustment column as 0.00.
For example, the cart has the following products:
Product | Net Price | Base Price |
---|---|---|
P1 | (USD 100.00) | (USD 100.00) Note: The PLI of this product has negative pricing. |
P2 | USD 250.00 | USD 250.00 |
If the sales representative applies 10% discount on both products, CPQ displays the updated price details as follows:
Product | Net Price | Base Price | Adjustment |
---|---|---|---|
P1 | (USD 110.00) | (USD 110.00) | -10.00 |
P2 | USD 225.00 | USD 250.00 | -10.00 |
Prevent Users from Finalizing a Cart If Bundle Configuration Does Not Honor Min Options for an Option Group
CPQ can now prevent sales representatives from finalizing the cart if the bundle configuration does not honor the Min Options configured for an option group of that bundle. This feature is useful when:
- Min Options is defined for an option group.
- The option group is hidden because the options under it do not have any active price list items.
- Sales Representative finalizes the cart when there are no active products in an option group to fulfil the minimum number of options.
CPQ introduces an admin setting APTS_ExecuteMinMaxRulesOnInactiveOptions to execute this feature. When this admin setting is set to True, CPQ displays an error message that configuration is pending for the bundle that has the option group (where options have inactive PLIs). Thus, CPQ prevents Sales Representatives from finalizing such carts.
Enhanced Logic to Define Precedence for Defaulting the Quantity of Option Products
The default quantity of an option product defined by the bundle structure takes precedence now over the default quantity defined at the price list item of that option product. The administrators can define the default quantity of an option product at the price list item level and at the bundle structure level. Also, the Sales Representatives can enter a quantity for the option product on the Configuration page. In such a scenario, the precedence for calculating the default quantity is as follows:
- Transactional input provided by the Sales Representative on the in Configuration page
- Default quantity defined at the bundle structure level
- Default quantity defined at the price list item level
Create a Collaboration Request for Auto-Included Products
CPQ displays the collaboration icon () next to an auto-included standalone or bundle line items if the APTS_EnableCollabForAutoIncludedLines is set to True. If you initiate a collaboration request for the parent product, CPQ automatically adds auto-included products as part of the collaboration. You can also create a collaboration request for auto-included products independent of the parent product.
Mandatory Validation to Consider Cancelled Options While Changing or Renewing Assets
CPQ performs a mandatory validation now to consider cancelled option line items while changing or renewing assets. If you deselect the required options on the Configuration page, CPQ displays an error message and selects the options back after the pricing calculation is complete. Thus CPQ ensures that you cannot finalize the cart without the mandatory options.
Renew Bundle Assets without Adding Asset Net Price of Cancelled Options
While renewing a bundle asset (both ramped lines and non-ramped lines), if the Sales Representative deselects an option, CPQ does not add the asset net price of the option to the rollup line of the bundle. CPQ displays that option as Cancelled on the cart with the asset start date and end date.
Apply Price Escalator on New Ramp Lines During ABO Operations
CPQ now applies Price Escalator on new ramp lines created during ABO operations regardless of the Default Asset Pricing Indicator? setting (true or false). A new ramp line always gets its value from the PLI and it honors the price escalator defined for its period. If price escalator is not defined for the particular new ramp period, it will fetch the value of the PLI of the product.
Support for Price Ramps
When the TurboEngines is enabled, you can perform Create, Update, and Delete price ramps for the standalone products, bundles, and options. You can also apply the auto price ramps on the cart line items.
To use this feature, you must enable the price ramps in the price list item associated with the line item.
Support for Auto Ramp Creation
When the TurboEngines is enabled, you can also apply the auto price ramps on the cart line items. This feature allows you to auto-generate ramp line creation based on general information, like Start Date, End Date, and Term.