About Release Notes
Apttus Release Notes contain the following information about CPQ Spring 2020 Patch 4 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)
(Required if you are using Approvals)
|11.0.0114 | 11.114|
Conga Base Library
(Required if you are using Conga Configuration & Pricing)
18.104.22.168 | 1.40.1
Conga CLM Configuration Integration
(Required if you are using CLM)
|12.0.0130 | 12.130|
|Conga Configuration & Pricing (New)|
12.0.1719.9 | 12.1719.9
Spring 2020 Patch 4
|Conga Contract Lifecycle Management||11.0.0519 | 11.519|
|Conga CPQ Api||12.0.0100 | 12.100|
Conga CPQ Approvals
(Required if you are using Approvals on CPQ objects)
|11.0.0016 | 11.16|
Conga CPQ Setup
(Required if you are using CPQ Admin Console)
|22.214.171.124 | 12.54.2|
Conga Deal Maximizer Setup
(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
|9.0.0055 | 9.55|
Conga Quote Configuration Integration
(Required if you are using CPQ and Proposal Management)
|12.0.0324 | 12.324|
Conga Quote DocuSign Integration
(Required if you are using DocuSign)
|4.0.0021 | 4.21|
Conga Quote EchoSign Integration
(Required if you are using Adobe Sign)
|2.0.0014 | 2.14|
Conga Quote Management
(Required if you are using Proposal Management)
|10.0.0210.2 | 10.210.2|
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.
There are no new features in this release. Keep checking the Apttus Documentation Portal for new updates.
There are no new enhancements in this release.
Data Model Changes
There are no data model changes in this release.
The following table lists the issues resolved in this release.
|Case Number||Apttus Internal ID||Description|
|00098905||CPQ-43728||When the action product of an auto-inclusion constraint rule was part of an option group with radio buttons, CPQ triggered the constraint rule once or twice only. When you deselected and selected the condition products more than twice or thrice, CPQ did not auto-select the action product.|
|00098796||CPQ-43491||When you selected options in quick succession, CPQ did not create Related Line Items for the options.|
|00101658||CPQ-43265||You faced an issue with an inclusion constraint rule during the swap asset action in client mode.|
|00101160||CPQ-43078||After you revalidated an already configured Service Cart, CPQ displayed the spinning wheel continuously and you could not perform anything on the Cart.|
|00099757||CPQ-42946||You faced an issue with an inclusion constraint rule when the same rule was applied on a swapped asset.|
|00100668||CPQ-42900||In CPQ Admin, the OPTION tab was not visible between the DETAILS and MATRICES tabs in the Advanced functionality of price list item of bundles.|
|00098486||CPQ-42161||When you used the cloneBundleLineItems api, the line item sequence field (Apttus_Config2_LineSequence_c) was not updated in the cloned line item.|
|00096285||CPQ-41427||On the Related Line Item popup, when you changed Weightage Type to Amount and Weightage Amount = 0 and if you clicked Reprice, CPQ displayed the error "Failed to Reprice: Divide by 0" on the Cart.|
|00087652||CPQ-37826||Cloning an option on the configuration page was leading to an infinite spinner and console errors.|
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-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.
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: CPQSFSPR20P4RNREVA20200723