Removal of Duplicate 'Fulfilment' Tab in Obligations

The redundant Fulfilment tab is removed from within individual Fulfilment records in the Classic UI, eliminating duplicate information in both the Contract record > Obligations > Fulfillment > Fulfillment Number and Manage Fulfillment > Fulfillment Number views. This update streamlines the display of fulfilment details for contract users.

Supplier and Request Management Enhancements

The Supplier Requests form now captures contact names as separate, required First Name and Last Name fields. For more information, see Creating a Supplier Request. For more information, see Creating a Supplier Request.

 A mandatory Email Domain field has been added to each Supplier record. All suppliers contact email addresses must match the configured domain (including sub-domains. An Active toggle sits above the Login toggle, with Login only enabled when Active is ON; turning Active OFF automatically disables Login and shows a warning. The Primary Contact option is available only for active contacts. The Contact List page now displays a Enable Login column indicating each supplier contact's login status when the Supplier Portal setting is enabled in CLM Admin. The Enable Login field is also available as a filter and applies to both supplier profile and portal views. For more information, see Supplier Fields.A new Obligations tab in the Supplier Profile provides a centralized view of all obligation fulfilments for a supplier across multiple contracts, in every status. It supports search and sort by Fulfilment Number, Status, Assignee, Reviewer, and Due Date, and offers saved views for Overdue, Upcoming, and All Fulfilments. Selecting a fulfilment number opens the Manage Fulfilment details in a unified view with Details and Activity History tabs. Supplier Managers can act on fulfilments on behalf of supplier contacts, submitting or waiving fulfilments in "Pending Fulfilment" status, and accepting, rejecting, or requesting information for fulfilments in Pending Review status. All comments and documents are synchronized back to the contract records and Manage Fulfilment pages. For more information, see Obligations.

Delete Action for Global Documents

Contract administrators can now delete global documents. Deleting global documents marks them as inactive while preserving their audit history and existing associations with contracts. Deleted documents are excluded from new attachments but remain accessible for download in the recycle bin, along with deletion details. For more information, see Viewing a Global Document.

Duplicate Check for Contract Requests

The system now automatically detects potential duplicate contract requests or contracts during key actions, such as submitting, converting, or approving a contract request, based on configurable criteria set by administrators. When enabled, a modal dialog displays a list of possible duplicates for user review, allowing users to proceed or abort the action, while actions without duplicates continue uninterrupted. The duplicate check is available only for single requests. For more information, see Creating a Contract Request, Approving a Contract Request, and Converting an Approved Contract Request.

A new API endpoint GET{{/api/clm/v1/requests/

/duplicate-check}} is introduced to identify potential duplicate contract requests by comparing request details against existing contracts. The endpoint requires read authorization on the Agreement entity and returns a list of matched contracts in a standard response envelope, supporting both exact and fuzzy matching as configured. When duplicate checking is disabled, the endpoint returns an empty list without querying existing contracts. For more information, see Conga Developer Portal.

Delete Contract Requests and Bundled Contract Requests

Users can now delete single or bundled contract requests in Draft status. Deletion is supported from the My Requests and All Requests list views, as well as from the Contract Request tab on Account and Opportunity records. Deleting a request moves it to the Recycle Bin and removes it from standard list views while preserving complete audit history (including user, timestamp, and tracked fields). For more information, see Deleting a Contract Request, Deleting a Contract Request for an Account, Deleting a Contract Request for an Opportunity.

Contract requests can also be deleted programmatically using the API endpoint DELETE https://rls-dev.congacloud.io/api/clm/v1/requests/<contractRequestId>. For more information, see Conga Developer Portal.

Supplier Sanctions Screening

You can now run sanctions screening on suppliers directly within CLM and act on the results. Supplier Managers can initiate screening for one or more selected suppliers from the All Suppliers and My Suppliers pages, checking against the OFAC SDN List and UN Consolidated Sanctions List, with support for both single and bulk runs and exclusion of suppliers already blocked. After each run, a system-generated email summarizes the results for all processed suppliers in a single message, including overall and per-list outcomes and links to download individual PDF screening reports; failed screenings are clearly identified, and all reports remain accessible from the supplier's Documents tab and profile even if email delivery fails.

The supplier profile's Basic Details section displays the latest screening result—Match Found, Match Not Found, or Not Screened, with a details popup showing supplier information, screening date, per-list results, and a downloadable report. A dedicated Sanctions Screening Status field (Not Screened, Pending Review, Clear, or Blocked) tracks the supplier's disposition independently of the existing Supplier Status, reflecting the latest screening outcome and any block or unblock actions, with all transitions recorded in Activity History and the field hidden from suppliers in the portal.

Approved users with the appropriate permission can block or unblock a supplier when a Match Found result appears, providing a required reason that is captured in Activity History; these actions update the Sanctions Screening Status without changing the supplier's lifecycle status. Administrators control who holds Block Supplier and Unblock Supplier permissions through user groups, and blocks are enforced across CLM: related contracts display a Blocked tag, contract actions are paused, and blocked suppliers cannot be selected when creating new contracts.

For more information, see Supplier Sanctions Screening, Object Permissions, Action Permissions, Buy-side Contract for Suppliers, and Creating a New Contract by Filling a Form.

Supplier Contacts Enhancements

When creating or editing a supplier contact, users can toggle Enable Login directly on the contact record. Enabling login automatically provisions a user in User Management with the appropriate permissions, while disabling login deactivates portal access immediately. For more information, see Supplier Fields.

Out-of-the-box, merge-field-driven email templates are available for supplier portal workflows without requiring custom code. The system includes dedicated seeded templates for dispatching supplier portal invitations as well as notifying supplier contacts when their portal access has been disabled. The system automatically triggers a branded HTML invitation email upon enabling portal login or reactivating an account. Emails feature secure token-based activation link directing supplier contacts to the OTP verification and password setup flow. For more information, see Email Template Management.

Users can review full activity history filtered by event type and date range directly on the supplier record to support compliance and governance reviews. For more information, see Activity History and Audit and Access Dashboard.

Enhanced Global Conversations: Direct Post Creation

Users with appropriate permissions can now initiate a new conversation post directly from global views (My Conversations, All and Unread Conversations) without navigating into individual object records first.

Users can also link discussions to a specific context object and record, automatically filtering selectable objects based on the user's access permissions, when creating a post in global Conversations page. For more information, see Creating a Post and Conversations.

The POST /api/conversations/v1/view-conversations/my-records/query and POST /api/conversations/v1/view-conversations/my-records/search endpoints retrieve and search conversations, with real-time updates reflecting changes in record ownership.

The GET /api/conversations/v1/supported-object-names endpoint provides a list of supported object names and their display names for initiating conversations from All, My, and Unread Conversation views. The API response includes objects such as Account, Agreement, Contract Request, Supplier, and Supplier Request, enabling integration and automation scenarios. For more information, see Conga Developer Portal.

Mention Handling for Removed Participants in Conversation Posts

When a user is mentioned using @mention in the Rich Text Editor and subsequently removes from the participant list before posting, the system now validates the mention. The post either retains the mention as a tagged user or prompts for correction if the participant is no longer present, preventing mentions from appearing as plain text. For more information, see Creating a Post.