Generic Labels for Conversations Across Supported Objects

Conversations now display a generic introductory label that applies to all supported objects, including ContractRequest, SupplierRequest, Account, and Supplier. This update removes contract-specific references, providing a consistent user experience when enabling Conversations for different object types.

Contract Hierarchy Visualization API: Tree View and Data Integrity Updates

The Contract Hierarchy Visualization API now supports hierarchical retrieval of contracts for an account, including parent–child relationships such as master agreements, statements of work, amendments, and renewals. The child contract retrieval endpoint is updated to use the POST method, allowing flexible query parameters, and both endpoints return complete hierarchy data without pagination. The API enforces that contract IDs must belong to the specified account ID, preventing cross-account data issues and ensuring accurate contract relationships. For more information, see Conga Developer Portal.

Inline Notification for Manage Participants

Display an inline notification on the Conversation page when participants are added or removed, indicating the action, the user responsible, and the timestamp. Notifications appear in the order of occurrence and are visually distinct from standard responses, supporting both oldest and newest sorting options. For more information, see Managing Conversation Participants.

Email Notification with Conversation History for Added Participants

When a participant or conversation owner is added to a conversation, the system sends an email that now includes the full conversation history. This update enables participants to access prior discussion context directly from the notification email. For more information, see Conversations.

CloneSpec JSON Mapping for Contract Request Conversion

Configure field mappings from Contract Requests to Agreements using a customizable JSON-based CloneSpec, supporting source and target field mapping by request type. Administrators can manage and update CloneSpec configurations via config-management APIs, enabling tailored implementations without UI changes. This feature supports extensibility for custom fields and aligns with the contract conversion API endpoint POST /api/clm/v1/requests/{{contractRequestId/convert}}.

Legal Entity Create Button Controlled by RBAC and Property-Based Access Control

Only users with Create permission at the Legal entity object level can view the Create button, regardless of property-level permissions. This ensures RBAC and property-based controls restrict creation to authorized users. For more information, see Object Permissions and Creating a Legal Entity.

Property based Access Control for Contract Requests and Supplier Requests

Conga CLM now supports property-based access control on ContractRequest object in Contract Group and SupplierRequest object in Supplier Group. Administrators can define and manage reusable common attributes for contract requests and supplier requests objects. These attributes work with existing RBAC permissions to control who can see and act on specific contracts and supplier records, improving data protection while preserving current behavior.When determining user authorization for contract requests and supplier requests, the system evaluates both object-level and property-level permissions for these objects. Configuring both object-level and property-level permissions is optional. If data security requirements require property-level control over CRUD operations, administrators can configure permissions at both levels. If property-level permissions are not configured, authorization behavior remains based solely on object-level permissions.

Updated UserID Character Limit for Ad hoc Participants in Conversations

The UserID character limit in the schema configuration has been increased to accommodate longer email addresses, allowing ad-hoc participants to be added to conversations without errors.

Conversation Feature Management

The Conversation feature is now managed through CLM Feature Management Settings and is disabled by default. Administrators can enable the feature, making related pages and APIs visible and functional, while access remains restricted when disabled. The "Click here to know more" link appears for generally available features to provide additional information.

Contract Relationship Tree View

View all contracts for a customer in a hierarchical tree using the Tree View. It shows parent–child relationships (e.g., master agreements, SOWs, amendments). Users can expand/collapse branches, open contract details, and export the current hierarchy to CSV. The view is read-only and supports filtering, searching, and sorting only at the parent level. This feature is only available for accounts. For more information, see Viewing the Contract Details of an Account.

Global Documents Repository

The system introduces a centralized global documents repository for storing and managing documents accessible across contracts. Users with appropriate permissions can upload, search, and manage documents by type, description, effective and expiration dates, and associated entities, with access governed by role-based access controls. Only authorized users can view, upload, edit metadata, or retire documents, while document content remains uneditable after approval. For more information, see Global Documents.

Contract Managers can link global documents from the centralized repository to contracts, to reuse standardized documents without duplication. The system displays only effective documents based on contract dates, enforces applicability rules, and shows document metadata such as name, description, type, effective date, and expiration date in the Documents tab. Only supported file types are visible, and clear validation messages appear if a global document upload fails or a mandatory document is invalid. For more information, see Uploading a Document.

Fulfillment Record Creation for Renewed and Cloned Contracts

Activating a renewed or cloned contract automatically creates fulfillment records with a status of "Pending Fulfillment" for all associated obligations, including both newly added and copied obligations from the prior version. This enables contract managers to track obligation completion for the new contract version without manual setup.

Obligation Management for Renewed and Cloned Contracts

When a contract is renewed or cloned, the system copies only the obligation definition records from the current active version of the source contract to the renewed or cloned contract. Obligation fulfilment records are not copied, ensuring that historical fulfilment data is excluded from the new contract instance.

Before the renewed or cloned contract is activated, contract managers can manage obligations as needed. Users can add new obligations, edit existing obligation attributes, or delete copied and newly created obligations without requiring additional configuration.

Obligation Management Support for Amended Contracts

When an active contract is amended, the system copies only recurring obligations from the current active contract version if at least one associated fulfilment record is in the Pending Fulfilment or Pending Review status. Fulfilment records are not copied to the amended contract. Recurring obligations with fulfilment records only in final statuses, such as Fulfilled On Time, Fulfilled Late, Cancelled, or Superseded, are also excluded from the amendment.

Contract managers can add, edit, and inactivate obligations copied from a prior contract version when working on an amendment. Deletion of recurring obligations from previous versions is restricted, while obligations added during the current amendment can be deleted. The "Print on Contract" status is retained from the original contract but remains adjustable during the amendment process.

Fulfillment Record Creation for Amended Contracts

Activating an amended contract creates fulfillment records with a status of "Pending Fulfillment" for all associated obligations, including both newly added and copied obligations from the prior version. This enables contract managers to track obligation completion for the new contract version without manual setup.

Recipient Differentiation in O365 Integration

Show an External label for recipients who are not app users, helping distinguish them from internal users. Internal users appear without any label. This applies to Send for Review, Send for Signature, and post-activation notifications, ensuring accurate recipient selection. For more information, see Microsoft 365 Review.

Legal Dashboard for Contract Lifecycle Management

The Legal Dashboard provides legal managers with out-of-the-box visualizations, including clause category and subcategory distributions, clause risk analysis, contract volume trends, clause modification rates, and identification of non-standard language and frequently redlined clauses. Access key metrics such as high-value contracts at risk, ad-hoc clauses inserted from outside the clause library, and top fallback clauses used in contracts. For more information, see CLM Report.