Conga Approvals (Required if you are using Approvals)

15.0.388.13

15.388.13

Conga Base Library (Required if you are using Conga Configuration & Pricing) (Changed)

5.0.255.31

5.255.31

Conga Billing  (Required if you are using Conga Billing)

10.0.396.12

10.396.12

Conga CLM Configuration Integration  (Required if you are using CLM)

16.0.0187.2

16.187.2

Conga Configuration & Pricing  (Changed)

16.0.2122.58

16.2122.58

Conga Contract Lifecycle Management  (Changed)

15.0.740.14

15.740.14

Conga CPQ Api

16.0.0136.1

16.136.1

Conga CPQ Approvals  (Required if you are using Approvals on CPQ objects)

13.2.25

13.25

Conga CPQ Maximizer

10.0.0034

10.34

Conga CPQ Setup (Required if you are using CPQ Admin Console)

16.0.145.3

16.145.3

Conga Deal Maximizer Setup (Required if you are using Deal Maximizer)

8.0.0053

8.53

Conga Deal Maximizer

7.0.0007

7.7

Conga DocuSign Api

8.1.142.7

8.142.7

Conga Order Management

1.0.0000

1.0

Conga Promotions (Required if you are using Promotions)

1.0.0000

1.0

Conga Quote Approvals

7.1.10

7.10

Conga Quote Asset Integration

6.5.0015

6.15

Conga Quote CLM Integration

12.2.0085.1

12.85.1

Conga Quote Configuration Integration  (Required if you are using CPQ and Proposal Management)

16.0.0407.3

16.407.3

Conga Quote DocuSign Integration

4.1.23

4.23

Conga Quote Echosign Integration (You must install the latest Adobe Sign package to use this package)

3.1.17

3.17

Conga Quote Management (Required if you are using Proposal Management) (Changed)

13.2.0267.9

13.267.9

When you adjust the bundle line item, CPQ displays the Net and Base Prices of the options incorrectly.

You can use “APTS_DisableSellingTermDefaultForDateRange” admin setting to calculate the selling term based on the quote's start and end dates when enabled. If disabled, CPQ uses the preferred default selling term instead.

For more information, see Configuring Admin Settings.

The related pricing does not work as intended when it depends on a standalone product added as an option.

An Apex CPU Time Limit error occurs when attempting to enable Smart Search by clicking the Search Activation button.

The Quote Attachment page of 'Send Proposal' shows the document size in KB instead of MB.

You encounter the following error while running the criteria maintenance job for pricing fields.

"System.LimitException: Apttus_Config2:Too many DML rows: 10001".

You encounter the following error while performing collaboration on the cart. This issue is observed when you try to update the start date or the due date to null in a collaboration request.

"Could not resolve remote action: updateCollaborationRequest".

You encounter the following error when you try to invoke the applying promotion API.

"System.LimitException: Apttus_Config2:Too many query rows: 50001"

Turbo Cart disables actions when you reconfigure a product while pricing is in progress.

You encounter the following error intermittently while running the Smart Search sync.

"Invalid API response System.HttpResponse [Status=Bad Request, StatusCode=400] {"error":"invalid_grant","error_description":"authentication failure"}"

A pricing loop happens when one rule adds Product B with Product A, and another removes both. Re-adding Product A causes the loop.

Auto Renew Ramp incorrectly renews the first ramp based on the 364-day Renewal Lead Time. This results in renewal opportunities and proposals with incorrect start and end dates for 2027-28.

When sending a proposal via email, the "Sender and Recipient" list under activity history shows only the sender. However, querying EmailMessageRelation reveals three records, with two missing relationship details.

Mass update > Reset on custom lookup fields in the cart screen does not clear the field to blank. The custom lookup fields remain unchanged when using Mass update functionality.