Download PDF
Download page February '23 Release Notes.
February '23 Release Notes
In these release notes, you can find packages, requirements, features, enhancements, fixed issues, and known issues for the CPQ February '23 release. For documentation updates, see What's New in CPQ Documentation.
This documentation may describe optional features for which you have not purchased a license; therefore your solution or implementation may differ from what is described here. Contact your Customer Success Manager (CSM) or Account Executive (AE) to discuss your specific features and licensing.
Packages
The following packages and dependencies are required to upgrade to this release and use its new features. These are the minimum required versions; later versions are also supported. Prerequisites for each feature can be found in its documentation. Packages marked (New) are new for this release.
You can register your org for the Conga Upgrade Program. Conga Upgrade Program is an automated tool that upgrades packages available in your Salesforce org (Production or Sandbox) to the latest versions. In addition, it also ensures all the Conga published managed packages are on the latest versions for your registered orgs. For more information, see Registering for Conga Upgrade Program.
| Package | Latest Certified Version Name | Latest Certified Version Number |
|---|---|---|
| Conga Approvals (New) (Required if you are using Approvals) | 13.2.365 | 13.365 |
Conga Base Library (New) (Required if you are using Conga Configuration & Pricing) | 4.0.243 | 4.243 |
Conga Billing (New) (Required if you are using Conga Billing) | 9.0.319 | 9.319 |
| Conga CLM Configuration Integration (New) (Required if you are using CLM) | 15.0.0178 | 15.178 |
| Conga Configuration & Pricing (New) | 15.0.2062 | 15.2062 |
| Conga Contract Lifecycle Management (New) | 14.0.696 | 14.696 |
| Conga CPQ Api (New) | 15.0.0131 | 15.131 |
| Conga CPQ Approvals (New) (Required if you are using Approvals on CPQ objects) | 13.2.25 | 13.25 |
| Conga CPQ Maximizer | 8.0.0029 | 8.29 |
| Conga CPQ Setup (New) (Required if you are using CPQ Admin Console) | 15.0.133 | 15.133 |
| Conga Deal Maximizer Setup (Required if you are using Deal Maximizer) | 8.0.0052 | 8.52 |
| Conga Deal Maximizer | 7.0.0007 | 7.7 |
| Conga DocuSign Api (New) | 8.1.142 | 8.142.5 |
| Conga Order Management | 1.0.0000 | 1.0 |
| Conga Promotions (Required if you are using Promotions) | 1.0.0000 | 1.0 |
| Conga Quote Approvals (New) | 7.0.9 | 7.9 |
| Conga Quote Asset Integration | 6.5.0014 | 6.14 |
Conga Quote CLM Integration | 11.1.0082 | 11.82 |
| Conga Quote Configuration Integration (New) (Required if you are using CPQ and Proposal Management) | 15.0.0396 | 15.396 |
| Conga Quote DocuSign Integration | 4.1.22 | 4.22 |
Conga Quote Echosign Integration (You must install the latest Adobe Sign package to use this package) | 3.1.17 | 3.17 |
Conga Quote Management (New) | 13.0.0263 | 13.263 |
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
For information pertaining to the requirements and recommendations you must consider before you proceed with the installation of the Conga product, see System Requirements and Supported Platforms Matrix.
Upgrade Notes
For more information on the prerequisites and post-upgrade tasks, see Upgrading CPQ.
Before you upgrade the CPQ packages in your org to February '23 release, please note the following points:
If the CPQ package in your org is on any of the following releases, you must upgrade it to the Winter '20 patch (Winter20.02.26) before upgrading it to February '23 release:
Release Package Spring '20 or earlier release
Packages older than 12.0.1719 | 12.1719 Summer '20 patch older than Summer20.02.26
Packages older than 12.1.1787.99 | 12.1787.99 Winter '20 patch older than Winter20.02.26
Packages older than 12.2.1839.48 | 12.1839.48 If the CPQ package in your org is on any of the following releases, you can directly upgrade it to February '23 release:
Release Package Latest Summer '20 patch (Summer20.02.26 or later)
12.0.1719 | 12.1719 or later Latest Winter '20 patch (Winter20.02.26 or later)
12.2.1839.48 | 12.1839.48 or later Spring '21 and any Spring '21 patches
13.0.1882 | 13.1882 or later Summer '21 and any Summer '21 patches 13.1.1921 | 13.1921 or later December '21 and any December '21 patches 13.2.1969 | 13.1969 or later May '22 and any May '22 patches 14.0.1995 | 14.1995 or later September '22 and any September '22 patches 14.1.2038 | 14.2038 or later February '23 and any February '23 patches 15.0.2061 | 15.2061 or later
New Features
The following feature is new to CPQ in this release.
Ability to Decrease Asset Quantity
You can now decrease the quantity of an asset during the current term when the original quantity is no longer required. During the sale of these decrement licenses, CPQ merges the decrement quantity with existing assets (you can change the start date of the assets).
For more information, see Managing Asset Decrement with Coterminate Lines and Use Case: Asset Decrement with Cotermination Lines.
Enhancements
This section describes the existing features that are changed in this release.
Display a Spinner on the Service Catalog on Click of the Add to Cart Button
CPQ introduces an admin setting APTS_EnableBlockingCallsOnServiceCatalog to display a spinner on the Service Catalog upon the click of the Add to Cart or Update buttons. When the admin setting is enabled, CPQ displays the spinner to ensure that the creation of related line items is completed for service products (Product Type = Service) before you navigate away to a different page or click another button. Earlier, if you quickly navigated away from the Service Catalog after clicking Add to Cart, CPQ did not create related line items for service products.
For more information, see Configuring Admin Settings.
Support for Sorting Order of Generated Documents on the Doc Gen Page
CPQ now enables you to sort the generated documents in descending order of Created Date on the doc gen page using Sort Documents Descending proposal system property. If this setting is not enabled, the documents are sorted in ascending order of creation date, by default. In addition, enabling the Sort Documents Descending proposal system property, CPQ previews the document that was generated last instead of previewing first document everytime.
If you are upgrading from the May '22 or September '22 to February '23 release of CPQ, you must remove the APTS_SortDocumentsDesc admin setting. The admin setting is no longer supported. For more information, see .Configuring Admin Settings.
For more information, see Performing the Post-Upgrade Tasks, Configuring Document Generation for Quote, Using Proposal Document Generation, Proposal System Properties, and Configuring Admin Settings.
Display Auto-Adjustment Lines in Read-Only Mode on the Multiple Adjustments Pop-Up
CPQ now displays auto-applied adjustments in read-only mode on the multiple adjustments pop-up. You cannot make any changes to auto-applied adjustments. CPQ enables the Save button only after you make any change to a manual adjustment line item.
For more information, see Config System Properties, Enabling Multiple Adjustments at the Line-Item Level, and Applying Multiple Adjustments on Line Items in the Cart.
Restore Asset Values on Reselection of Cancelled Options During ABO Operations
CPQ introduces a new custom setting Asset Restore Fields to restore asset values for the option line item when you reselect an option on the Configuration page. When you deselect an option and reselect it on the Configuration page during any ABO operation, CPQ restores asset values for the fields added in the Asset Restore Fields setting, for the option line item on the Cart page. However, there is an exception to restoring start and end dates during the Renew operation. CPQ restores the renewal start date and end date on reselection of an option (not the asset start and end dates) during the Renew operation.
For more information, see Installed Products Settings, Renewing Assets Manually, Use Case: Restoring Asset Values on Reselection of Cancelled Options During Renewal, Changing Configurable Bundle Assets, and Use Case: Restoring Asset Values on Reselection of Cancelled Options During Change.
Create a Default View for Each Flow on the Installed Products Page
The sales representative can now create a default view for each flow on the Installed Products page or from the Admin Assets View page. Earlier, there was only one default view regardless of the flow.
For more information, see Managing Views for Assets Grid.
Identify the ABO Action Performed on the Cart Line Item
CPQ can now identify which exact ABO action happened, through the Comments field on the cart line item. When you hover your mouse on the Comments field, CPQ displays the ABO action that resulted in a specific line status of the cart line item.
CPQ introduces the ABO Action field on the Config Asset Pricing Default custom setting to associate ABO actions with specific line statuses and the Default Asset pricing Indicator value. This allows you to override the default asset pricing configured through the global Default Asset Pricing Indicator? setting in Config System Properties and switch between asset price and PLI price based on the ABO actions and line statuses.
Multiple ABO actions can result in the same line statuses for cart line items. For example:
| ABO Action | Line Status |
|---|---|
Renew and Change (for line items when Price Type = One Time and Enable One Time Change = False) | Existing |
For the line status Existing, you can now switch between asset price for Renew and PLI price for Change. Earlier, switching between asset price and PLI price based on the same line status for different ABO actions was not possible.
For more information, see Overriding the Default Asset Pricing for Line Statuses and Use Case: Switching Between Asset Price and Price List Item Price.
Data Model Changes
The following objects and fields are introduced to or changed in the system or data model in this release.
Object | Fields | Description | System/User | New/Changed |
|---|---|---|---|---|
| Asset Line Item | Represents a product or service asset line item. In February '23, do not use the following new fields, which are added in preparation of a future functionality:
| User | Changed | |
| Billing Term | The billing term associated with the product or service. | User | New | |
| First Billing Date | The first day of billing for the asset. Primarily used for legacy assets. | User | New | |
| Is Legacy For Billing | Indicates whether the asset is considered a legacy for billing. | User | New | |
| Remaining Billable Amount | Indicates how much is remaining to be billed for the asset. The field is updated every time the Status of a billing schedule changes from Pending Billing to Invoiced or from Invoiced to Pending Billing. | User | New | |
| Asset Line Item History | Represents a product or service asset line item history. In February '23, do not use the following new fields, which are added in preparation of a future functionality:
| User | Changed | |
| Billing Term | The billing term associated with the product or service. | User | New | |
| First Billing Date | The first day of billing for the asset. Primarily used for legacy assets. | User | New | |
| Is Legacy For Billing | Indicates whether the asset is considered a legacy for billing. | User | New | |
| Remaining Billable Amount | Indicates how much is remaining to be billed for the asset. The field will be updated every time the “Status” of a Billing Schedule changes from “Pending Billing” to “Invoiced” and vice versa. | User | New | |
| Billing Preference | Represents a functional preference for billing purposes | User | Changed | |
| Ignore Renewal Proration Setting | When enabled, the custom setting “No Proration on Renewal” is ignored by the billing engine. | User | New | |
| Payment Term | Represents a payment term associated with a quote, order, or an agreement | User | Changed | |
| Offset Early Invoice Date (Days) | Offset in days to determine the ready-for-invoice date | User | New |
Fixed Issues
The following table lists the issues fixed in this release. If any actions are required, they will be listed in this table.
| Case Number | Conga Internal ID | Description |
|---|---|---|
| 00814267 | CPQ-61544 | In Service CPQ, while relating a standalone product, if you click Add to Cart and quickly navigate away from the Service Catalog, CPQ does not create related line items for the standalone product. Resolution Info: CPQ introduces an admin setting APTS_EnableBlockingCallsOnServiceCatalog to resolve this issue. When this admin setting is set to true and you click Add to Cart or Update on the Service Catalog, CPQ displays a spinner while the network calls in the background are completed. This prevents you from doing any other action after clicking Add to Cart or Update that can impact the network calls due to which CPQ will not create related line items for standalone service products. For more information, see Enhancements. |
| NA | CPQ-59809 | Update the help text for Billing Start Date and Billing End Date fields on the Billing Plan object. For more information, see Preparing for Upgrade. |
| 00796403 | CPQ-59660 | Copying a product in the cart page does not copy the usage tiers from the source product to the copied product. |
| NA | CPQ-59599 | CPQ does not load the Cart page when you enable the "Enable JsonAccess Annotation Validation for the Visualforce JavaScript Remoting API" feature from the latest Salesforce release. |
| 00811352 | CPQ-59525 | Clicking the name of the product on the cart page opens the attribute details of the product, wherein instead of the picklist name, the API name is displayed. |
| 00810588 | CPQ-59407 | In the TurboPricing flow, even when the product option price setting is selected as Read-only, the quantity is still editable on the cart page. |
| 00787695 | CPQ-58732 | The Apex Jobs page is displaying the UsageDataJobScheduler job as failed with the following error when the Conga Base Library package was installed: Scheduler: failed to execute scheduled job: jobId: 7075e00000UaQ4a, class: common.apex.async.AsyncApexJobObject, reason: Dependent class is invalid and needs recompilation: Class Apttus_Base2.UsageDataBatchJob : Dependent class is invalid and needs re... Resolution: CPQ no longer supports the UsageDataJobScheduler job, you must delete it from Scheduled Jobs before you upgrade the Conga Base Library package to release. This job was scheduled by the older version of the Conga Base Library package. For more information, see Preparing for Upgrade. |
00803104 | CPQ-57149 | If the administrator has not defined any usage matrix on the price list item, after the sales representative reprices the cart, CPQ deletes price tiers. This issue happens only in the Classic CPQ. |
00799458 / PST-2376 | CPQ-55729 | After you recall approval of a quote, if you navigate to the cart and reprice it, CPQ does not trigger the Approval Required icon on the line item. Resolution Info: Modified the reconfiguring process to identify lines with Approval Status as Cancelled and then trigger the approval evaluation again. |
00784670 | CPQ-52497 | CPQ does not execute constraint rules when there are multiple constraint rule conditions defined. |
| 00774647 | CPQ-52037 | Reselection of cancelled options during asset renewal was restoring the asset start and end dates for the option line item on the Cart page instead of restoring renewal start and end dates. Resolution Info: CPQ introduced a new custom setting Asset Restore Fields to restore asset values for the option line item when you reselect an option on the Configuration page. If the administrator has added at lease one asset field to the Asset Restore Fields setting, during Renew operation, CPQ restores the renewal start and end dates by default (not the asset start and end dates) and restores the rest of the fields from the asset. |
| 00104268 | CPQ-44591 | In lightning mode, clicking on a custom button on the cart that opens up a pop-up, and then navigating back to the cart displays an error message. |
The following table lists the known issue fixed from the previous release.
Conga Internal ID | Description |
|---|---|
| CPQ-59173 | In the Unified Cart flow, CPQ displays an error when you add products with multiple charge types and perform the validate action. |
| CPQ-55186 | Turbo Integrations: After you save or finalize the configuration, the status for Product Configuration is set as New instead of Saved/Finalized. |
| CPQ-54278 | Turbo Integrations: You encounter the following error while finalizing the revalidated cart if the revalidation callback is configured in your org: entity is deleted |
| CPQ-49315 | Config asset pricing criteria are not functioning on a single ramp renewed line (renew one ramp = true). |
Known Issues
The following table provides the cumulative list of known issues up to this release.
| Conga Internal ID | Description |
|---|---|
| CPQ-58544 | You cannot finalize the Cart after revalidating the expired or inactive price list item (primary) of a product. |
| CPQ-54022 | Turbo Integrations: Attribute-based pricing is not working for Numeric Expression. |
DOC ID: CPQFEB23RNREVC20230317