Conga Product Documentation

Welcome to the new doc site. Some of your old bookmarks will no longer work. Please use the search bar to find your desired topic.

Show Page Sections

Preview: CLM for Advantage Platform 202604.1.0 Release Notes

In these release notes, you can find enhancements and fixed and known issues for the CLM 202604.1.0 release. For documentation updates, see What's New in CLM Documentation.

Note:

This documentation may describe optional enhancements 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 enhancements and licensing.

Enhancements

The following enhancements are new to CLM in this release.

Account Page PBAC Permission Management

The Account page uses PBAC to restrict user access, limiting visible and selectable Account group values to authorized ones and blocking unauthorized submissions. The same access control applies to the Contracts tab. Accounts with admin access can be configured to bypass these restrictions. For more information, see Creating an Account.

Dynamics 365 Integration: Conga CLM Access in Sales Hub

Microsoft Dynamics 365 users can now access Conga CLM features including All Contracts, All Contract Requests, Conga Approvals, Obligation Fulfillments, Contract Search, and Contract Dashboards and Reports, from a unified Conga CLM menu within the Sales Hub navigation.

Each feature opens the full Conga CLM interface within an iFrame, enabling seamless in-app navigation while supporting all capabilities available in the Conga CLM application. For more information, see Accessing Conga CLM from Dynamics 365.

Mention Display and Highlighting in Conversation View

Conversations now display an @ badge on conversation cards, post headers, and reply posts when the logged-in user is mentioned, and visually highlight @mention text in message content for the mentioned user. These indicators appear only for users who are directly mentioned, enabling quick identification of relevant posts and replies. For more information, see Conversations.

Obligation Due Date Reminder Notifications

Assignees receive a single consolidated reminder email at 10 AM (organization time zone) on the obligation fulfilment due date for all Pending Fulfilment obligations assigned to them per contract. Reminders are not sent for obligations linked to contracts with Expired, Terminated, Canceled, or Inactivated status. For more information, see Obligation Fulfillment.

Context Object Integration (COI) for Conversations

Conversations now provide end-to-end context integration so collaborators always know which record a discussion is tied to—and can navigate back to it easily. Users can initiate and manage conversations not only from Contracts, but also from Contract Requests, Supplier Requests, Accounts, and Suppliers.

While creating or viewing a thread, the system consistently displays the context via badges/indicators and breadcrumbs across the Conversations experience (Initiate Post dialog, thread cards, thread detail view, and breadcrumb header). Context breadcrumbs follow the hierarchy {Context Type}s > {Context Name} > Conversations, and users can click breadcrumb segments or the context badge to navigate to the relevant list view or record details page. Email notifications continue to work end-to-end, including hyperlinks back to the correct context record (especially for Contract Request and Supplier Request) while maintaining referential integrity between threads and their associated context. For more information, see Conversations.

Aggregated Conversations and Unified Visibility Across Contract Amendments

View all conversation threads from a contract and its related amendments in a single, unified conversation page, whether amendments are linked automatically or manually. Each thread displays a version badge and tooltip for clear context, and search, pagination, and thread details operate across all versions while preserving the correct contract version for posting, replies, and notifications. To ensure performance and avoid circular relationships, manual amendment chains are supported up to 10 levels, while system?generated chains have no enforced depth limit. For more information, see Viewing Conversations.

Dynamics 365 Integration: Contract Request Creation from Opportunity

As an extension of the existing Conga CLM and Microsoft Dynamics 365 integration, contract request creation is now supported directly from opportunity records. Previously, users could create contracts from Accounts and Opportunities; this enhancement extends that capability to contract requests as well.

With this update, Dynamics 365 users can initiate contract requests directly from an opportunity and view all related contract requests within the same record. This streamlines the contract initiation process, improves traceability, and enables sales teams to manage pre-contract activities more efficiently within their existing workflow. For more information, see Creating a Contract Request from an Opportunity.

Dynamics 365 Integration: Contract Request Creation from Account

As an extension of the existing Conga CLM and Microsoft Dynamics 365 integration, contract request creation is now supported directly from account records. Previously, users could create contracts from Accounts and Opportunities; this enhancement extends that capability to contract requests as well.

With this update, Dynamics 365 users can initiate contract requests directly from an account and view all related contract requests within the same record. This streamlines the contract creation process, reduces manual data entry, and maintains consistency across systems. It is especially useful for sales, legal, or operations users who manage contracts tied closely to customer accounts and want to begin the contract lifecycle without navigating away from the Account record in Dynamics 365. For more information, see Creating a Contract Request from an Account.

Fixed Issues

The following issues are fixed in this release. If any actions are required, they will be listed in this table.

Case Number Conga Internal ID Description
- CONTRACTS-40657

Validation rules cannot be added to fields in custom objects located under the Related tab on the Contract page. Changes made using the Edit Page option are not retained after refreshing the page, and the rules fail to function as expected.

Known Issues

The following unresolved issues are known to Conga at the time of this release.

Conga Internal ID Description
AIPLAT-4970

Search Agent intermittently returns inconsistent results for identical queries executed within a short time frame.

DOC ID: CLMRLP202604.1.0RN20260421