About Release Notes
Apttus Release Notes contain the following information about CPQ Spring 2020 Release on Salesforce.
Packages: Lists packages that are required to upgrade to this release of the product
- System Requirements and Supported Platforms: Lists requirements and recommendations for installing this release
New Features: Provides high-level descriptions of new features introduced in this release, with links to more detailed information
- Enhancements: Provides high-level descriptions of enhancements to existing features
- Data Model Changes: Lists changes to the data model
- Resolved Issues: Lists customer-reported issues that are resolved in this release or known issues resolved from previous releases
- Known Issues: Lists known issues that are applicable in this release
This documentation may contain descriptions of software features that are optional and for which you may not have purchased a license. As a result, your specific software solution and/or implementation may differ from those described in this document. Please contact your CSM or AE for information on your specific features and licensing.
The following packages and dependent packages are required to upgrade to this release to utilize all the new features of this release. These are the minimum required versions; later versions are also supported. Separate prerequisites for each feature can be found in the respective guides. The packages marked as (New) are new packages in this release.
Latest Certified Version
(Version Name | Version Number)
Conga Approvals (New)
(Required if you are using Approvals)
|11.0.0114 | 11.114|
Conga Base Library (New)
(Required if you are using Conga Configuration & Pricing)
1.0.40 | 1.40
Mandatory package to be installed in the Spring 2020 release.
Conga CLM Configuration Integration (New)
(Required if you are using CLM)
|12.0.0130 | 12.130|
|Conga Configuration & Pricing (New)|
12.0.1719 | 12.1719
|Conga Contract Lifecycle Management (New)||11.0.0518 | 11.518|
|Conga CPQ Api (New)||12.0.0100 | 12.100|
|Conga CPQ Approvals (New)|
(Required if you are using Approvals on CPQ objects)
|11.0.0016 | 11.16|
Conga CPQ Setup (New)
(Required if you are using CPQ Admin Console)
|12.0.54 | 12.54|
Conga Deal Maximizer Setup (New)
(Required if you are using Deal Maximizer)
|7.5.0046 | 7.46|
|Conga Order Management||1.0.0000 | 1.0|
(Required if you are using Promotions)
|1.0.0000 | 1.0|
|Conga Quote Approvals||6.5.0004 | 6.4|
|Conga Quote Asset Integration||6.5.0014 | 6.14|
Conga Quote CLM Integration (New)
|9.0.0055 | 9.55|
Conga Quote Configuration Integration (New)
(Required if you are using CPQ and Proposal Management)
|12.0.0324 | 12.324|
Conga Quote Management (New)
(Required if you are using Proposal Management)
|10.0.0210 | 10.210|
Before installing or upgrading Apttus managed packages, you must review the dependency matrix for each managed package. You can refer to the package dependency matrix at Managed Packages Dependency Matrix.
System Requirements and Supported Platforms
The following table lists the minimum requirements for installing and using CPQ on Salesforce.
|System Requirement||Minimum Supported Version|
|Operating System||Standard Salesforce.com requirements. See Salesforce PDF.|
Apttus supports the following browsers:
Apttus recommends the latest stable version of the browser for the best performance.
Internet Explorer is not supported.
Apttus recommends the latest Microsoft Office Suite for the best performance.
For more information on the prerequisites and post-upgrade tasks, see Upgrading Apttus CPQ in CPQ on Salesforce Spring 2020 Administrator Guide.
The following features are new to CPQ in this release.
Ability to Sort Products on the Catalog Page
In this release, CPQ allows you to sort products on the Catalog page based on predefined fields in Product Sorting Fields custom setting. You can sort products in ascending or descending order of the field defined by the administrator. When you click the sort icon (), you see the options Product Name Ascending and Product Name Descending in the Sort pop-up by default.
Revalidation Callback Class
In this release, CPQ introduces a new callback class, Revalidation Callback. This callback provides you a mechanism to implement custom revalidations for products based on custom criteria. You can define custom criteria based on which the products are identified by CPQ for revalidation. The callback allows you to define a custom logic to be applied on the line item along with revalidation. You can also define a custom product version when the line item is created.
For more information, refer to Revalidation Callback Class in CPQ on Salesforce Spring 2020 Administrator Guide
The following section describes existing features that are changed (or are no longer supported) in this release.
Apttus User Experience Analysis
With this release, in order to better understand and analyze feature usage and the user experience, Apttus is adding a user experience analysis component to its solution with the assistance of Pendo. The analytics component allows Apttus to tailor improvements and new features to help meet your business requirements and improve the user experience. No action is required on your part and there will be no impact to any existing product features, system functionality, or configured workflows. No personally identifiable information (PII), nor any other proprietary, confidential, or sensitive data will be collected by the analytics component.
During Apttus Base Library installation, if you see an “Approve Third-Party Access” prompt, this refers to the Apttus User Experience Analysis component. Click Continue to proceed with the installation. For more information, see Installing the Apttus CPQ Packages.
Ability to Open the Cart in Read-only Mode
In this release, CPQ allows you to open your product configuration in read-only mode. In read-only mode, you can only see the line items in the cart, but you cannot edit any fields. All action buttons are disabled in a read-only cart. You can create and use filters and cart views in a read-only cart. When the pricing is pending, only the line items with complete pricing are displayed on the cart in read-only mode with a progress bar with the status of the ongoing pricing process.
For more information, refer to Opening Cart in Read-only mode in CPQ on Salesforce Spring 2020 User Guide.
Ability to Use Numeric Expressions to Create CPQ Formula Fields
CPQ allows you to create an expression using the Apttus Numeric Expressions Framework while creating CPQ formula fields so that you can use them for configuring prices and adjustments.
For more information, refer to Managing CPQ Formula Fields in CPQ on Salesforce Spring 2020 Administrator Guide.
Ability to Define UOM in Price Rule Entry
In this release, CPQ allows you to enter the UOM for the price rule entry so that CPQ applies the UOM conversion rate if the price rule entry and the line item have different UOMs.
For more information, refer to Creating Price Rules in CPQ on Salesforce Spring 2020 Administrator Guide.
Ability to Select Effective Dates in Price Rule Entry
In this release, CPQ allows you to select Effective Date and Expiration Date for price rule entry.
For more information, refer to Creating Price Rules in CPQ on Salesforce Spring 2020 Administrator Guide.
Ability to Define Currency for Price Ruleset
In this release, CPQ allows you to define the currency for price ruleset. The value of currency in a price ruleset is inherited to price rules.
For more information, refer to Creating Price Rulesets in CPQ on Salesforce Spring 2020 Administrator Guide.
Flow-Based Defer Pricing
In this release, CPQ allows you to selectively turn on or off Defer Pricing at a flow level. You must set the deferPricingUntilCart parameter to True in the URL that you have configured on the Configure Products field of the respective quote.
Ability to Selectively Skip Totaling on the Cart
In this release, CPQ allows you to selectively skip the totaling of pricing of products on the Cart, at a flow level. You must set the isCartTotalingDisabled parameter to True in the URL that you have configured on the Configure Products field of the respective quote.
Ability to Selectively Skip Approval of the Cart
In this release, CPQ allows you to selectively skip approval of the Cart, at a flow level. You must set the isCartApprovalDisabled parameter to True in the URL that you have configured on the Configure Products field of the respective quote.
Ability to Selectively Skip Deal Guidance
In this release, CPQ allows you to selectively skip Deal Guidance, at a flow level. You must set the isPricingGuidanceDisabled parameter to True in the URL that you have configured on the Configure Products field of the respective quote.
Improved Scalability in Deal Guidance
In this release, Deal Maximizer has made the deal guidance process a lot more scalable than it was earlier. The improvements include:
- Support for thousands of rules and rule entries. For example, 5000+ rules with approximately 10 rule entries in each rule can now be made available in your org.
- A single query giving output up to 1000+ rule entries which are successfully applied into the cart.
- Restricted limit for seamless execution of the cart page to 1000 rule entries per cart. If you have some advanced criteria and scope for the rule entries and the limit of 1000 rule entries per cart has reached, then the pricing process on the cart page fails and an error message is displayed.
- The rules are associated with the Product Groups and the Product Families.
For more information, see Define Deal Guidance Rules in Deal Maximizer on Salesforce Spring 2020 Administrator Guide.
Editable Custom Currency Field on Cancelled Lines
In this release, CPQ allows users to edit a currency field while terminating an asset. The currency field must be a custom field and not based on a formula.
Enhanced Asset Renewal Custom Callback Class
In this release, CPQ allows you to populate a selective set of parameters with corresponding values on a renewal quote (with the same data as the original quote) during renewal automation.
For more information, refer to Asset Renewal Custom Callback Class in CPQ on Salesforce Spring 2020 Administrator Guide.
Enhanced User Experience while Collecting Input for Working with Assets
In this release, the default date in the Effective Date field is the farthest start date, while merging assets. If you enter a date that is lesser than the farthest start date, an error message is displayed on the Merge popup. For more information, refer to Merging Assets in CPQ on Salesforce Spring 2020 User Guide.
In this release, CPQ allows administrators to configure the logic to default a date for users while swapping assets, using the Asset Line Item Callback Class. For more information, refer to Asset Line Item Callback Class in CPQ on Salesforce Spring 2020 Administrator Guide.
In this release, CPQ allows administrators to configure the logic to default a date for users while terminating assets, using the Asset Line Item Callback Class. For more information, refer to Asset Line Item Callback Class in CPQ on Salesforce Spring 2020 Administrator Guide.
Hidden Fields on the Related Line Items Popup for Relationship Type Merger
In this release, the Add/Remove, Save, and Split buttons are hidden for Merger relationship type when you merge assets.
For more information, refer to Merging Assets in CPQ on Salesforce Spring 2020 User Guide.
Ability to Dynamically Sort Assets with a Visual Indicator
In this release, the Installed Products page lists all assets for the account in decreasing order of the values in the Created Date column by default. You can sort assets dynamically, a single column at a time, by clicking the column header.
For more information, refer to Managing Assets in CPQ on Salesforce Spring 2020 User Guide.
Disabled Farthest Asset End Date for Single Asset Selection
In this release, the Farther End Date option is hidden during asset renewal:
- If the asset has only one renewable charge type
- If the selected asset has multiple renewable lines with the same end date
For more information, refer to Renewing an Asset in CPQ on Salesforce Spring 2020 User Guide.
Ability to Selectively View Data During Swap
In this release, CPQ allows administrators to define which fields must be displayed to users on the Intermediate page while swapping assets.
Ability to Prevent Editing End Date for Cancelled Lines (Merge Assets)
In this release, CPQ allows administrators to prevent users from accidentally editing the end date for cancelled lines while merging assets.
For more information, refer to Merging Assets in CPQ on Salesforce Spring 2020 User Guide.
Renewal Processing for Merged Assets with the Same Purchase ID
In this release, when the user merges two assets with the same purchase identifier, the merged line is associated with the same renewal quote that contained the original lines.
For more information, refer to Use Case: Renewing Merged Assets with the Same Purchase Identifier in CPQ on Salesforce Spring 2020 User Guide.
Billing Preference Validations
In this release, the supported values in Billing Preference fields are validated. The fields are Proration Period Treatment, Billing Day of the Month, and Billing Cycle Start.
For more information, refer to Impact of Asset actions on Billing Schedules in CPQ on Salesforce Spring 2020 User Guide.
Enhanced Account Hierarchy Performance
In this release, CPQ provides an enhanced Account Hierarchy performance. The APTS_AccountHierarchyBatchSize admin property is converted to the Account Hierarchy Batch Size custom setting under Installed Product Settings.
Support for Match in Assets in Inclusion Type Client-Side Constraint Rule
In this release, CPQ supports Match in Assets Match Conditions in Constraint Rule Actions in Client-Side Constraint Rules. When you select Match in Assets, CPQ checks if the product in constraint rule action exists as an asset on installed products. Only if the asset does not exist the action is executed. Otherwise, CPQ does not take action. Match in Asset is only supported for Inclusion type Constraint Rules for action intents Auto Include and Prompt.
For more information, refer to Creating Constraint Rule Actions in CPQ on Salesforce Spring 2020 Administrator Guide.
Enhanced Is Optional Checkbox Behavior
In this release, CPQ allows you to edit is Optional checkbox for all options and sub-bundles. Now, you can mark options or sub-bundles as optional even when they are added using rules or if they are required. Also, when you mark a bundle as optional or clear the is Optional checkbox, the action is cascaded down to all options and sub-bundles as well. That means if you select is Optional checkbox for the bundle, all the associated options and sub-bundle are also marked optional. The price of the optional line item is not included in the total price.
For more information, refer to Configuring a Product from the Catalog in CPQ on Salesforce Spring 2020 User Guide.
Support for Related Line Items for Service Bundle Options in Reconfigured Quote
In this release, CPQ displays related line items for options in a Service bundle on the Configuration page after you reconfigure saved or finalized quote. Previously, CPQ did not display related line items next to the service options added after reconfiguration. However, the related line items that are displayed next to the service bundle options reflect the related line item of the parent bundle.
For more information, refer to Configuring Service Products in CPQ on Salesforce Spring 2020 User Guide.
Flow Specific CSS Override Availability
In this release, CPQ now supports CSS overrides for a specific flow. Now, you can define unique CSS overrides for your flows. CPQ continues to support global CSS override if you don’t need flow specific CSS overrides. You must create a separate dataset of Config System Properties for your flow and define the CSS Override field. Leave the CSS Override field blank in System Properties.
For more information, refer to Configuring Custom Settings in CPQ on Salesforce Spring 2020 Administrator Guide.
Disabling Product Configuration Versioning
In this release, you can disable cloning of the product configuration after you reconfigured a finalized cart. When you disable Product Configuration versioning, only one product configuration is created on the Quote Details page. If you reconfigure a cart after finalizing it, the existing product configuration is updated.
For more information, refer to About Product Configuration in CPQ on Salesforce Spring 2020 User Guide.
Ability to Display Refine Your Search Options in Picklist
In this release, CPQ allows you to define a limit exceeding which the options of Refine Your Search on the Catalog page are displayed in the picklist. The options are displayed as checkboxes when the number of options are less than the limit. Define Refine Search Checkbox Limit in Config System Properties.
For more information, refer to Configuring Custom Settings in CPQ on Salesforce Spring 2020 Administrator Guide.
Enhancement to CPQ Admin
The following enhancements are introduced for the CPQ Admin user interface.
Managing Option Groups
In this release, CPQ moved the Manage Option Groups button from the Catalog menu to the Products menu. You can search, open, update, and, create shared option groups on the Manage Option Group page. For more information, refer to Creating Option Groups in CPQ on Salesforce Spring 2020 Administrator Guide.
In this release, CPQ introduced a dedicated page to manage rollups. The Manage Rollups page (Products menu > Manage Rollups) allows you to search, open, update, and, create rollups. For more information, refer to About Manage Rollups Page in CPQ on Salesforce Spring 2020 Administrator Guide.
Managing Field Expressions
In this release, CPQ introduced a dedicated page to manage field expression. The Manage Fields Expression page (Products menu > Manage Field Expression) allows you to search, open, update, and, create field expressions. For more information, refer to About Manage Field Expressions Page in CPQ on Salesforce Spring 2020 Administrator Guide.
In this release, CPQ introduced a dedicated page to manage rules. The Manage Rules page (Products menu > Manage Rules) allows you to search, open, update, and, create rules which includes Constraint Rules, Product Attribute Rules, Attribute Value Matrix. For more information, refer to About Manage Rules Page in CPQ on Salesforce Spring 2020 Administrator Guide.
Searching Associated Products in Product Group
In this release, CPQ enables you to search for products that are associated with product groups. On the Associated Product page (Products menu > Manage Product) you can select a product group and search for a specific product using the search bar in the center pane. For more information, refer to Associating Products to a Product Group in CPQ on Salesforce Spring 2020 Administrator Guide.
Progress Bar During Mass Update
In this release, CPQ displays a progress bar on the Cart page when you apply mass updates on the line items. A message is also displayed with the progress bar with the status of the process to apply the mass update.
Progress Bar on Mini-Cart
In this release, CPQ displays a progress bar in the Mini-Cart after you add products to the cart. A message is also displayed next to all the line items in the mini-cart with the status of the process to calculate pricing. The progress bar is also displayed on the Catalog page when you click Configure.
Support for Multiple Benefit Products for Buy X Get Y Promotions
In this release, CPQ supports multiple benefits for Buy X Get Y promotions, where users can choose to provide benefits either on all listed products or only the first product on the Cart.
For more information, refer to Defining the Benefits of a Promotion in CPQ on Salesforce Spring 2020 Administrator Guide.
Deprecated Fields on Billing Preference
In this release, CPQ deprecated the following fields on the Billing Preference object:
- Preference Level
- Billing Interval
- Billing Day of Month
- Additional Invoice CC Address
- Allow Preference Override?
- Allow Payment Term Override?
- Order Line Item
- Asset Line Item
- Cart Line Item
For more information, refer to Setup Billing Preference in Billing Management on Salesforce Spring 2020 Administrator Guide.
Managed Package Visualforce Pages (Deprecated)
The CPQ managed package Visualforce pages (classic pages) such as the Catalog, Cart, Configuration, and Installed Products pages are discontinued.
Angular User Interface (Deprecated)
Apttus CPQ ended support for the Angular user interface since the Summer 2019 release. CPQ no longer supports any feature on the Angular user interface. Customers must use the Cart Grid user interface.
Cart Themes (Deprecated)
Cart themes are discontinued since the Summer 2019 release. Now, a standardized theme is implemented which is displayed on the cart regardless of the cart theme defined in the Config System Properties. CPQ only supports a standardized look and feel.
Data Model Changes
The following objects and fields are introduced to or changed in the system or data model in this release.
|Date Exchange Rate||Holds dated currency exchange rates||New|
|Currency Code (Internal)||Currency Code for Internal Use||System||New|
|Exchange Rate||The exchange rate||User||New|
|Next Start Date||The next exchange period date||User||New|
|Rate Type||The exchange rate type||User||New|
|Start Date||The current exchange period date||User||New|
|Expression||The formula expression. Either use field or expression.||User||New|
|Quote/Proposal||ID of the associated quote/proposal||User||New|
|Configuration Effective Date||The configuration effective date||New|
|Price Rule Entry||Changed|
|Adjustment Uom||The adjustment unit of measure||User||New|
|End Date||The period end date. The entry becomes ineffective after this date/||User||New|
|Products Oper||The products criteria operator.||User||New|
|Start Date||The period start date. The entry becomes effective on this date.||User||New|
|Enable Currency||Indicates whether the currency is enabled for amount based price adjustments. Only applicable in a multi-currency org.||User||New|
|Enable Date Range||Indicates whether date range is enabled for the rule or benefit entries.||User||New|
|Pricing Date||The default pricing date. The line items are defaulted with this date.||User||New|
|Configuration Effective Date||The configuration effective date.||System||New|
|Disable Cart Versioning||Indicates whether cart versioning is disabled for the quote/proposal.||User||New|
|Apttus UI Component Configuration||Object Records holds stored configurations for configurable higher-order components.||New|
|Class name for data provider||The class name of the Custom Data Provider Class (implemented by the consuming application).||System and User||New|
|Component Config Id||The ID of the record Config Component.||System and User||New|
|Component Type||Defines the component type, for example, Catalog, Grid, and Panel.||System and User||New|
|Config||The stored configuration that has state and renders directives for the component.||System and User||New|
|Data Provider||Stores the reference to Provider Instance.||System and User||New|
|Description||Description of the configuration record.||System and User||New|
|Package name for data provider||Package Name (or namespace) of the application that implements the Provider.||System and User||New|
|Published||Indicates if the configuration is locked or not. Once the configuration is published it may not be deleted or modified.||System and User||New|
|Template||The Lightning Web Component template associated with the configuration or component.||System and User||New|
|Apttus UI Component Provider||The object records store the information about Providers of all types that are implemented by consuming applications||New|
|Description||The description of the Provider||System and User||New|
|External Id||External Id referenced by Configuration Object||System and User||New|
|Is Application Manifest||Indicates if the type of provider is Manifest. This is an implementation of the Provider Factory pattern where all types of providers in an application are defined in a single manifest class.||System and User||New|
|Is Standard||Indicates if this is a system-defined provider.||System and User||New|
|Object||The system will define a provider (Data or Action) for this Object, only if the Is Standard field is true.||System and User||New|
|Package Name||The package name (or namespace) of the consuming application that defines the provider class implementation||System and User||New|
|Provider Class Name||Name of the provider implementation class in the consuming application||System and User||New|
|Configuration Action Provider||Junction Object to Correlate Configurations to Action Provider(s)||Deprecated|
|Action Provider||Reference to the Action Provider||System and User||Deprecated|
|Class name for data provider||The class name of the Provider Implementation||System and User||Deprecated|
|Configuration||Refernce to the configuration record||System and User||Deprecated|
|External Id||The External Id used by the Configuration record||System and User||Deprecated|
|Package name for data provider||The package name (or namespace) of the consuming application that defines the provider class implementation||System and User||Deprecated|
|Configuration Action Provider 2||Junction Object to Correlate Configurations to Action Provider(s)||New|
|Action Provider||Reference to the Action Provider||System and User||New|
|Class name for data provider||The class name of the Provider Implementation||System and User||New|
|Configuration||Refernce to the configuration record||System and User||New|
|External Id||The External Id used by the Configuration record||System and User||New|
|Package name for data provider||The package name (or namespace) of the consuming application that defines the provider class implementation||System and User||New|
|Account||ID of the associated account||System||Deprecated|
|Additional Invoice CC Address||A comma-separated list of additional email addresses to copy the invoice to.||User||Deprecated|
|Allow Payment Term Override?||Indicates whether payment term may be overridden at lower levels||User||Deprecated|
|Allow Preference Override?||Indicates whether preference may be overridden at lower levels||User||Deprecated|
|Asset Line Item|
ID of the associated asset line item
|Billing Day of Month||The billing day of the month. Specific Day of Month, Account Creation Day, First Order Day, End of Month, etc.||User||Deprecated|
|Billing Interval||The billing interval||User||Deprecated|
|Cart Line Item||ID of the associated cart line item||System||Deprecated|
|Location||ID of the associated location||System||Deprecated|
|Order||ID of the associated order||System||Deprecated|
|Order Line Item||ID of the associated order line item||System||Deprecated|
|Preference Level||The level associated with the billing preference||System||Deprecated|
The following table lists the issues resolved in this release.
|Case Number||Apttus Internal ID||Description|
|NA||CPQ-37930||CPQ did not allow you to define flow specific CSS overrides.|
|NA||CPQ-37947 / CPQ-39731||CPQ did not allow you to edit the Is Optional checkbox for options that were auto-included based on constraint rules when the condition option or the parent bundle were optional themselves.|
|00025920||CPQ-38093||On the Favourite catalog, when you open the drop-down next to the Add to Cart button for a product, the drop-down did not collapse even if you moved to a different page.|
|NA||CPQ-38795 / CPQ-41350||When you defined multiple benefit products in Buy X Get Y type promotion, CPQ did not apply that promotion on the line item and displayed an error on the Cart page.|
|CPQ-40246||When you created Product Translations for a product, the product name was not displayed on the Catalog page.|
|NA||CPQ-40592||When you renewed asset line item with the option Farthest Asset End Date, CPQ use the date based on the renewal term instead of the farthest date.|
|NA||CPQ-40632||You were unable to merge duplicate assets without manual intervention.|
|NA||CPQ-40635||When you selected two assets with the same purchase identifier and merged them, the renewal quote did not retain the merged line item.|
When you generated a renewal quote, CPQ did not retain proposal header fields except for the mandatory fields like Account, Price List, resulting in incorrect price calculation on the cart.
|CAS-09996-H8W3V1||CPQ-41334||Deal Guidance stopped responding in use cases where there were >=50 line items because each line had its own Deal Guidance rules. You received a SOQL query error for reaching the threshold and could not recover the cart.|
|00095640||CPQ-41415||When you created a standalone option group, changes in one bundle reflected in other bundles, similar to a shared option group.|
|00097586||CPQ-41714||When you activated an order, CPQ displayed a null pointer error. This happened when the Term Start Date field was blank.|
The following table lists the known issues resolved from the previous release.
|Apttus Internal ID||Description|
|ASSETS-3054||On Confirm Termination page, Apttus CPQ does not display the correct value in Billing Difference fields. However, the difference is calculated correctly after the termination|
The following table provides the cumulative list of known issues up to this release.
|Apttus Internal ID||Description|
|ASSETS-1636||After you have renewed an asset with a one-time primary line when you perform Change: Config action, an incorrect Delta Price and Net Price are calculated on the cart.|
|ASSETS-1724||Config asset pricing criteria are not functioning on a single ramp renewed line (renew one ramp = true).|
|ASSETS-2574||Values are not proper for flat price incremented and merged lines on the user interface popup for the Projected Asset Value API.|
|ASSETS-2970||CPQ does not cascade the option quantity during split actions to the options on the Cart page.|
|CPQ-11829||If the option group is single-select and requires the selection (min:1, max:1), you cannot make it optional from the configuration page but can make it optional from the cart. You can notice the same behavior when options required by default.|
|CPQ-37247||When you renew service and add new equipment, Apttus CPQ displays 0 as Weightage Amount on the related line item pop-up.|
|CPQ-37251||Unit Of Measure conversion is not working for Price Ramps.|
|CPQ-37257||In the Service CPQ flow, when you reconfigure a finalized service cart, Apttus CPQ does not display the info message regarding service products auto-included via an inclusion constraint rule.|
|CPQ-37233||Apttus CPQ does not disable the products that are already associated with the category from the all products list on the Associated Product section in Catalog.|
|CPQ-37437||When you click the name of the parent category from the left-hand side panel on the Catalog page, you are redirected to the home screen of the Catalog page instead of the parent category.|
|CPQ-37445||Apttus CPQ does not update the price of an option when the price is based on an attribute value until you select another option.|
|CPQ-38515||If the options in a sub-bundle are auto-included based on the value of an attribute using the inclusion type constraint rule, Apttus CPQ does not remove the options from the sub-bundle when you change the value of the attribute and constraint condition is no longer valid. This happens when Is Bundle Context is selected.|
|CPQ-38642||On the exclusion prompt to exclude options, when you select options and click Remove Option, Apttus CPQ does not remove the selected options from the exclusion prompt and displays an error on the configuration page. However, the selected options are cleared on the Configuration page. This happens when constraint rules are executed on the server-side.|
|CPQ-39427||When you define Min/Max Applies To field as Base Price, Apttus CPQ restricts the net adjustment instead of the Base Price.|
|CPQ-39362||In Client-Side Constraint Rule, only one condition statement with product scope is supported on the client-side when you enabled Repeat Inclusion in Match in Condition.|
|CPQ-39699||When you select Enable Auto Reprice in Config System Properties, you are unable to apply % Discount Effective, % Markup Effective, and Price Factor Effective adjustments on totals on the Cart page.|
|CPQ-39772||Apttus CPQ does not execute constraint rules properly when Is Bundle Context is selected and the bundle and its sub-bundle have the same options.|
|CPQ-39900||If the options in a sub-bundle are disabled based on the selection of another option using the exclusion type constraint rule, Apttus CPQ does not enable the options when the condition is no longer valid. This happens when Is Bundle Context is selected.|
|CPQ-39972||When you configure an option in a bundle that is not a part of the Price List associated with the quote, Apttus CPQ does not display the price for that option. This happens specifically when the options price depends on the price list item of the bundle that belongs to a different price list then the price list associated with the quote.|
|CPQ-40101||Min/Max adjustment fields are not available on the CPQ Admin user interface.|
|CPQ-40128||Apttus CPQ does not reprice the cart after the inclusion type constraint rule is deactivated and the auto-included products are removed from the cart. You are able to finalize the cart with an incorrect price.|
|CPQ-40173||Match in Cart Options for exclusion type constraint rules are not working on the server-side.|
|CPQ-40238||When you add a product again in the inclusion prompt after removing it once and if the product belonged in a Product Group, Apttus CPQ does not allow you to finalize the cart.|
When you clone a quote using the Clone (with Line Item) button right after you finalize the cart, the newly cloned quote page does not load.
Workaround: In buttons like Configure Products and Clone(with Line Items), add a validation check in the formula of the buttons to disable or hide these buttons till the IsTaskPending flag is set to false.
CPQ does not calculate the Base Price of the service bundle option on the cart page according to the price matrix you defined on the price list item. The price is correct when you updated the quantity are reprice the cart.
When you define a price list item with Price Method as Related Price and define values in the Related Pricing section on the Price List Item Details page, CPQ does not calculate prices according to the values in Related Pricing on the cart.
Workaround: Use the fields Related Adjustment Amount, Related Adjustment Applies To, and Related Adjustment Type on the Price List Item Details page to define the related pricing.
Apttus Copyright Disclaimer
DOC ID: CPQSFSPR20RNREVB20210224