Conga Approvals (Required if you are using Approvals)

15.1.394

15.394.5

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

5.1.266.3

5.266.3

Conga Billing (Required if you are using Conga Billing) (Changed)

10.1.399.5

10.399.5

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

16.1.0188.3

16.188.3

Conga Configuration & Pricing (Changed)

16.1.2136.20

16.2136.20

Conga Contract Lifecycle Management

15.1.750.2

15.750.2

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.2

Conga CPQ Maximizer

10.1.0036

10.36

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

16.1.147

16.147

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

8.1.0055

8.55

Conga Deal Maximizer

7.0.0007

7.7

Conga DocuSign API

8.1.142

8.142.8

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.11

7.11

Conga Quote Asset Integration

6.5.0015

6.15

Conga Quote CLM Integration

13.1.0086

13.86

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

16.1.0408.4

16.408.4

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)

14.1.0268.1

14.268.1

Cloning a quote with an attribute value set to blank via Field Expression results in the pricing status being stuck as "Pending." This prevents the quote from being fully processed.

After cloning a quote, the expired option is incorrectly retained in the line item during revalidation. The option should not appear in the new quote after revalidation.

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.

When you re-finalize the cart, CPQ does not create the usage tier record.

When you finalize the cart after adding a product for which usage-based PLI and Matrix are configured, CPQ creates the UsageTier records as expected on the lineitem record. But, If you try to reconfigure the finalized cart that leads to cloning the configuration and UsageTier records and finalizing the cart again, CPQ does not create the UsageTiers records on the new finalized configuration’s lineitem records.

CPQ does not remove the validation error message on the cart page even though the required conditions are met from the validation callback class.

An error appears when opening the Bundle Maintenance page due to unsupported queryMore() in aggregate queries.

Adjustments to individual tiers in the usage matrix are currently not functioning as expected. Discounts cannot be edited, removed, or applied correctly on single tiers.

Adding a default price from a product attribute field to a Price List Item causes issues when running maintenance and adding products to the DC cart. The system incorrectly adds the field label to Constraint Criteria Fields, leading to query errors on line items.

The configuration page displays misaligned quantity and product code fields when the quantity is set to read-only.

Product Filter Maintenance fails with an Apex CPU time limit error when processing over 200 Classification records in a single batch. This causes the job to stop before completion.

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.