In these release notes, you can find packages, requirements, features, enhancements, resolved issues, and known issues for the Conga Approvals February '24 release. For documentation updates, see What's New in Approvals 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.


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 must have Community Portal login credentials to download these packages.

You can register your org for Conga Push Upgrade, an automated tool that upgrades packages available in your production or sandbox Salesforce org to the latest versions. In addition, it ensures that all the Conga published managed packages are on the latest versions for your registered orgs. For more information, see Registering for Conga Push Upgrade.


Required for

Latest Certified Version 


Conga Approvals (New)

Conga Grid (New)

Conga Approvals Center


Conga Approvals Center

This package is not available in the Conga Install Center. 

  • Install in Production from here.
  • Install in Sandbox from here.

Conga Approvals Center

Conga Base Library (New)


Conga Custom Approvals

Conga objects or other Salesforce standard/custom objects


Conga CPQ Approvals 

Conga CPQ

Conga CPQ Setup (New)

Conga CPQ API (New)

Conga Configuration & Pricing (New)

Conga CPQ Approvals


Conga Contract Lifecycle Management (New)


Conga Quote Management

Conga CPQ Approvals


Conga Quote Configuration Integration (New)

Conga CPQ and Quote Management

Conga CLM Configuration Integration (New)

Conga Quote Approvals

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

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 suite delivered on the Salesforce platform, see the System Requirements and Supported Platforms Matrix.

New Features

The following features are new to Conga Approvals in this release.

Submit with Attachment

An admin flag, APTS_HideSubmitButton, is introduced. Creating an admin entry with this default-false value set to true hides the Submit button on the Visualforce page. 

Selected Document Information on Approval Request

The Selected Documents field, introduced on an approval request object, stores title and version information for selected documents. 


Improved Error Messaging

Apex exception logging has been enhanced to conform with Salesforce information security findings. Administrators can configure verbose logging while supporting minimalist error messaging in the user interface.

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 NumberConga Internal IDDescription

Users in some orgs cannot assign an approval request from the queue to any user. A new admin entry, APTS_ReassignmentPermission, resolves this issue.


Incorrect security for approval step reassignment: any user can reassign and approve any step, even if the user lacks sufficient permissions.


When using the Apttus_Approval.ApprovalsWebService.approveRequestsBulk API to approve an approval request, this API does not assign the next approval request if it depends on the current approval request and the current approval request is a child process.


The approval process’s step dependency set is not honored when re-approval criteria are met in generated approval requests. When a quote is cloned with a product configuration record and associated approval requests, the approval requests in a new quote do not honor the step dependency or the dependent approval steps.


When the MyApprovalsEmail component is used in the email template, step information does not show correctly in the email if the approval assignee is a queue.


Quote approval status is updated to Approved when a user recalls the approval process.


The maximum character limit of the Rule Criteria field (Apttus_Approval__Criteria__c) on the Approval Rule object (Apttus_ApprovalApprovalRule__c) prevents users from adding all desired conditions/criteria.


Approver cannot take ownership of approval requests from the queue if the approver is a backup approver of users whose total queue/group memberships exceeds 50.


When trying to approve an approval request from the MyApprovals Sf1 page, user receives an error message, cannot leave page, and approval status is unchanged.


Refreshing a page in Lightning console reverts approval status to "Pending approval".

Known Issues

The following issues are known for this release.

Conga Internal IDDescription

When the user clicks the Approval Center tab and loads the default view, the filter saved for the default view is not applied.


When ad hoc approvers are added, step dependencies are not honored. When an ad hoc approver is added to an independent step that is rejected, the dependent step request moves to an Assigned status instead of the desired Canceled status.

DOC ID: IWAFEB24RN20240207