These Release Notes contain the following information about Conga CPQ Winter20.04.16 Release.

For more information on new features, enhancements, and document improvements refer to

  • What's New in Conga CPQ Winter '20 User Guide or
  • What's New in Conga CPQ Winter '20 Administrator Guide or
  • What's New in Conga CPQ Winter '20 SOAP API Guide
  • What's New in Conga CPQ Winter '20 REST API Guide
  • 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
(Required if you are using Approvals)
11.2.0190.7 | 11.190.7

Conga Base Library (New)

(Required if you are using Conga Configuration & Pricing) | 1.123.6

Conga CLM Configuration Integration
(Required if you are using CLM)
12.2.0146.13 | 12.146.13
Conga Configuration & Pricing (New)

12.2.1839.69 | 12.1839.69

Conga Contract Lifecycle Management11.2.0582.20 | 11.582.20
Conga CPQ Api12.2.0111 | 12.111
Conga CPQ Approvals
(Required if you are using Approvals on CPQ objects)
11.2.0019 | 11.19
Conga CPQ Setup
(Required if you are using CPQ Admin Console) | 12.83.3
Conga Deal Maximizer Setup
(Required if you are using Deal Maximizer)
7.5.0050 | 7.50
Conga Order Management1.0.0000 | 1.0
Conga Promotions
(Required if you are using Promotions)
1.0.0000 | 1.0
Conga Quote Approvals6.5.0004 | 6.4
Conga Quote Asset Integration6.5.0014 | 6.14

Conga Quote CLM Integration

9.2.0066.5 | 9.66.5
Conga Quote Configuration Integration 
(Required if you are using CPQ and Proposal Management)
12.2.0344.15 | 12.344.15
Conga Quote Management (New)
(Required if you are using Proposal Management)
10.2.0227.10 | 10.227.10

Before installing or upgrading Conga 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.

For more information on installing Conga managed packages, refer to Installing CPQ Packages. For more information on upgrading Conga managed packages, refer to Upgrading CPQ.

System Requirements and Supported Platforms 

The following table lists the minimum requirements for installing and using Conga CPQ.

System RequirementMinimum Supported Version
Operating SystemStandard requirements. See Salesforce PDF.
CPQ supports the following browsers:
  • Microsoft Edge Chromium
  • Google Chrome

Conga recommends the latest stable version of the browser for the best performance.

Internet Explorer is not supported.

Microsoft Office
  • Microsoft Word 2007 with Service Pack 2 plus hotfix package 976477 (Word 2007 version number must be greater than 12.0.6520.4999)
  • Microsoft Word 2010 (32-bit & 64-bit)
  • Microsoft Office 2019, 2016, 2013, and desktop version of Office 365

Use the latest Microsoft Office Suite for the best performance.

Upgrade Notes

For more information on the prerequisites and post-upgrade tasks, see Upgrading CPQ in Conga CPQ Winter '20 Administrator Guide.

New Features 

There are no new features in this release. Keep checking the Conga Documentation Portal for new updates.


The following section describes an existing feature that is changed (or are no longer supported) in this release.

Ability to Manage Renewal Rerun Based on Asset History

In this release, when you are using the OnDemand Renewal mode, you can execute the CreateRenewAssetsGroupJob multiple times to include incremental assets without impacting the TempRenewAssetGroups that are already generated.

Get Started

For more information, see Renewing Assets in OnDemand Renewal Mode in Conga CPQ Winter '20 User Guide.

Data Model Changes

There are no data model changes in this release.

Resolved Issues 

The following table lists the issues resolved in this release.

Case NumberConga Internal IDDescription
NACPQ-49378After you performed the Change ABO operation, if you updated the attribute value on option line items and added new options, the line status of recurring line became Existing instead of Amended.
00113531CPQ-49345After you saved the configuration in a quote, when you clicked Configure Products where launchState=assetsgrid, CPQ redirects you to the Installed Products page, instead of the Cart page.
00113466CPQ-48968If you have defined constraint rule to add a product that is not in the price list, CPQ did not add the line item.
00113581CPQ-48967The LPAD function was not working in attribute field expression.
NACPQ-48964For Quick Launch, when launchState=assetsGrid, configuring a quote did not redirect you to the Cart page for saved quote.
NACPQ-48761In the Change ABO operation, the price of an option line item did not change when you updated the attributes of the bundle (cascade attribute shared=true).
00112709CPQ-48688After you added the second asset, when you opened the RLI pop-up of the bundle on the cart, CPQ displayed the components of both the assets you added. But when we opened the RLI pop-up of the options, CPQ displayed the components of all assets there also.
00112022CPQ-48018In a Product Attribute Value field of type Pick List, when there were more than one picklist values with a special character ('), only the value was visible for selection if there was a Product Attribute rule with the ALLOW action.
NACPQ-47945Asynchronous document generation was facing a heap size error for Split Cart. The admin entry APTS_LargeDocSObjects has been enhanced to resolve this issue.

If you modified an asset after creating TempRenewAssetGroups using the OnDemand Renewal mode, CPQ created unwanted TempRenewAssetGroups when you executed the CreateRenewAssetsGroupJob batch job.

00111317CPQ-47759When you returned to the Catalog after all cart approvals were completed, CPQ still displayed the Reprice button as Primary, even though the cart status was Approved and there were no line items pending approval on the Cart.
00110621CPQ-47557Constraint rules related to other products already added in the cart were appearing in the configuration screen for a completely unrelated product.
00106359CPQ-45810CPQ displayed wrong net price when you closed the Multiple Adjustments window.
00104023CPQ-45155When you renewed assets that had ramps and multiple PLIs, an asset line item was not getting attached to a specific line item.

Known Issues 

The following table provides the cumulative list of known issues up to this release. 

Conga Internal IDDescription
ASSETS-1636After 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-1724Config asset pricing criteria are not functioning on a single ramp renewed line (renew one ramp = true).
ASSETS-2574Values are not proper for flat price incremented and merged lines on the user interface popup for the Projected Asset Value API.
CPQ-11829If 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-37247When you renew service and add new equipment, CPQ displays 0 as Weightage Amount on the related line item pop-up.
CPQ-37251Unit Of Measure conversion is not working for Price Ramps.
CPQ-37257In the Service CPQ flow, when you reconfigure a finalized service cart, CPQ does not display the info message regarding service products auto-included via an inclusion constraint rule.
CPQ-37233CPQ 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-37445CPQ does not update the price of an option when the price is based on an attribute value until you select another option.
CPQ-38515If the options in a sub-bundle are auto-included based on the value of an attribute using the inclusion type constraint rule, 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-38642On the exclusion prompt to exclude options, when you select options and click Remove Option, 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-39427When you define Min/Max Applies To field as Base Price, CPQ restricts the net adjustment instead of the Base Price.
CPQ-39362In 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-39699When 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-39772CPQ does not execute constraint rules properly when Is Bundle Context is selected and the bundle and its sub-bundle have the same options.
CPQ-39900If the options in a sub-bundle are disabled based on the selection of another option using the exclusion type constraint rule, CPQ does not enable the options when the condition is no longer valid. This happens when Is Bundle Context is selected.
CPQ-39972When you configure an option in a bundle that is not a part of the Price List associated with the quote, 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-40101Min/Max adjustment fields are not available on the CPQ Admin user interface.
CPQ-40128CPQ 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-40238When you add a product again in the inclusion prompt after removing it once and if the product belonged in a Product Group, CPQ does not allow you to finalize 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 AmountRelated Adjustment Applies To, and Related Adjustment Type on the Price List Item Details page to define the related pricing.

CPQ-43117CPQ is not applying the Min/Max Price to price ramps.
CPQ-43510On the cart page, CPQ displays incorrect values of the amount in parentheses that are converted based on the Dated Currency Exchange Rate.
CPQ-43701When you reconfigure a finalized quote and modify adjustments and reprice, CPQ displays a revalidation warning.

When you reprice product with Cummulative Range Line Item matrices, CPQ displays null object error.

CPQ-44113When you change the Selling Frequency or Selling UOM and then click Reprice, if the Frequency or UOM conversion rate is not defined for any field, CPQ does not display any error message.
CPQ-44268In TurboPricing flow, after you attempt to finalize a cart with a pending price, the Finalize button and the "Cannot finalize; Pending Reprice" message are displayed.

When you apply Advanced Filter with Select All Qualified Lines enabled, CPQ overrides any manual selection changes you made if you leave and navigate back to the page. This happens because the filters are processed every time the page is loaded.

CPQ-46133In TurboPricing flow, CPQ does not display a revalidation message when you perform revalidation after deleting a price list item.
CPQ-46346You are getting the console error "Apttus_Config2:Too many query rows: 50001" on Advance Search of Incentive Criteria.
CPQ-46124With a single renewal option, you can navigate to the Confirm Renewal intermediate page when the renewal association alert message is displayed.
CPQ-46304In TurboPricing flow, when you select and clear option selection multiple times, CPQ displays an error.
CPQ-46393In TurboPricing flow, when you define the Adjustment Amount Source with formula and leave the field used in the formula is blank, CPQ does not consider the Adjustment Amount value on the Cart page.
CPQ-46324In TurboPricing flow, when you enable Allocate Group Adjustment for options and reprice the cart after configuration, CPQ does not re-distribute the adjustments among options.
CPQ-48846When you add more line items after applying advanced filter, CPQ does not display the newly added line items.
CPQ-49591When you click Submit and Go to Proposal for a regular cart, the configuration remains in the New status and hence your data is lost.

If you change some value for the second time on the Advanced page of a price list item and save it, CPQ does not save the second change. However, CPQ saves the first change without any issues.

Workaround: Refresh the Advanced page before you make the second change, and then update the value and save it.