February24.05.17 Release Notes

In these release notes, you can find packages, requirements, features, enhancements, fixed issues, and known issues for the Billing February24.05.17 release. For documentation updates, see What's New in Billing 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. 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.

Product	Latest Certified Version
Product	Name	Number
Conga Base Library (New)	5.0.255.15	5.255.15
Conga Billing (New)	10.0.396.3	10.396.3
Conga CLM Configuration Integration	16.0.0187	16.187
Conga Configuration & Pricing (New)	16.0.2122.20	16.2122.20
Conga Contract Lifecycle Management (New)	15.0.740.4	15.740.4
Conga CPQ API (New)	16.0.0136.1	16.136.1
Conga Quote Asset Integration	6.5.0015	6.15
Conga Quote CLM Integration (New)	12.2.0085.1	12.85.1
Conga Quote Configuration Integration	16.0.0407	16.407
Conga Quote Management (New)	13.2.0267.6	13.267.6

For more information on installing Conga-managed packages, refer to Installing Conga Billing. For more information on upgrading Conga-managed packages, refer to Upgrading Conga Billing.

System Requirements and Supported Platforms

For requirements and recommendations to consider before installing the Conga product suite, see System Requirements and Supported Platforms Matrix.

Upgrade Note

Before you upgrade the Conga Billing Package, you must update the help text in the Billing Plan object's Billing Start Date and Billing End Date fields.

For more information, see Upgrading Conga Billing.

New Features

There are no new features in this release.

Enhancements

There are no new enhancements in this release.

Data Model Changes

There are no data model changes in this release.

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
NA	MAF-1568	While running the batch job for the invoice tax calculation, you get the following error message: `Too Many DML Rows: 10001.` Resolution Info: Tax calculation logic is optimized to update only those asset line items that are related to current batch-scoped invoice line items in an individual batch.
NA	MAF-1513	While creating Ad-hoc invoices with Custom Record type, you get the following error message: `The requested resource does not exist.` Resolution Info: The code is revised so that the engine retrieves the Invoice Summary Criterion dropdown values from the Invoice object rather than the Invoice Run object.
NA	MAF-1457	The billing API does not support the CPQ's "Calendar" selling term calculation method. Resolution Info The selling term calculation logic is revised to support "if-else" conditions. If the value in the config system property for the Selling Term Calculation Method field is set to Billing Preference, then the selling term is calculated per the billing preference; else, the "Calendar" based selling term is computed.
NA	MAF-1453	While performing an amendment for a period in the last billing cycle of an asset, the engine does not honor the billing preference. It creates an extra billing schedule record and a forecasted billing schedule record. Resolution Info The code is revised to alter the engine behavior so that if an amendment happens in the last billing schedule period, it must honor the calendar cycle start month.

Known Issues

There are no known issues in this release.

DOC ID: BILFEB24RN20240520