Soft Delete for Global Documents API

Contract administrators can use the DELETE /api/drive/v2/files/{documentID} endpoint to soft delete global documents, marking them as inactive without permanently removing them from the database. Soft-deleted documents are excluded from new contract attachments, remain visible in the recycle bin with deletion details, and are still downloadable for audit and historical reference. Only users with the ‘Delete Global Document’ permission can access this action, preserving access control and audit history.

My Requests Grid: Expanded Requester and Creator Visibility

The My Requests grid now displays contract requests where the logged-in user is either the Creator or the Requester, allowing both parties to track and follow up on requests regardless of who submitted them. Role-based access control (RBAC) and policy-based access control (PBAC) rules continue to govern visibility and permitted actions, ensuring users only access records and actions allowed by their assigned roles and permissions. For more information, see Contract Requests Management and Creating a Contract Request.

Dynamic Lookup Field: Alternate Parent Reference Name and Filter Logic Support

Administrators can configure the dynamic lookup field to use an alternate parent reference name in the dependent lookup filter expression by specifying the criteriaFieldName property. When multiple parent fields are configured, the filter logic defaults to AND with partial matching if not explicitly set, allowing filtering based on available parent values; when filterLogic is explicitly set to AND, all parent fields must have values for the filter to apply. Invalid or non-existent field names in criteriaFieldName are handled with clear validation messages, and existing configurations remain unaffected when the property is unset. For more information, see Dynamic Lookup Filters for CLM Layouts.

Cycle Time Report and Dashboard Enhancements

The Cycle Time Report and Dashboard now include the ‘Approval Status (Indicator)’ in the CTG table. It is used to determine the ‘In Approval’ stage, alongside updated logic for review stages based on the latest status and status category combinations. Rows with null or non-positive durations are excluded from calculations, average cycle time uses unique contract numbers as the denominator, and system-generated cycle groups are omitted. The dashboard displays horizontal split bars for different stages, and queries have been refined for accuracy and consistency.

Contract Request Number Format Configuration

Administrators can now configure a custom numbering format for contract requests by defining a prefix and sequence padding. Contract request numbers are automatically generated in a consistent Prefix-PaddedSequence format, such as REQNO123-0000042, making requests easier to identify and reference. The configured numbering scheme applies to newly created contract requests, while existing request numbers remain unchanged. For more information, see Configuring Contract Request Auto-numbering.

Signing Order for Signer Team Roles in Contract Teams

Contract Managers can now define and auto-apply a signing order for default signers assigned through Contract Team roles, supporting Contacts, Users and User Group recipient types. The configured signing sequence is carried over to the Send for eSignature page, where recipients are auto-populated in the specified order and can be reviewed or adjusted as permitted. This enhancement applies to Contract Team creation through the UI as well as the API ({{POST /api/clm/v1/contracts/

/teammembers}}). For more information, see Creating a Contract Team, Sending a Document for Conga Sign eSignature, Sending a Document for AdobeSign eSignature, and Sending a Document for DocuSign eSignature.

Duplicate Check Rule Configuration for Contract Requests

Administrators can now configure duplicate check rules for contract requests, enabling selection of target object (Agreement or Contract Request) and specifying matching fields such as Account, Counterparty, Contract Type, Effective Date, Agreement Title, Amount, and Record Type. Duplicate check can be enabled or disabled at the organization or request-type level, with options to define match logic, fuzzy-match thresholds, lookback scope, and enforcement behavior (warn or block). Out-of-the-box, duplicate checking is disabled, with default actions and fields provided for Agreements and Contract Requests; all configuration changes are governed by PBAC and captured in audit history. For more information, see Configuring Duplicate Checks for Contract Requests.

Restriction on Review and Signature Actions during DAI Extraction

The system restricts the Send for Review, Send for Signature, and Preview & Submit actions while document extraction is in progress, waiting, or uploading. These actions become available only after the extraction of at least one document is complete. For more information, see Uploading a Third-party Paper with Enhanced Flow.

Recall Conga Sign Signature Request

Users can now recall or cancel an in-progress Conga Sign signature request using the Recall Signature Request action button in the Contract Details page. Upon confirmation, the system deletes the transaction and resets the contract status to 'Ready for Signatures'. For more information, see Recalling a Signature Request.

Contract Document Download from Contract List

Users can now download contract document and executed documents directly from the contract list page without opening individual contract records. The menu action appears for all contracts in Activated or Fully Signed status and having documents. It supports both direct download and selection via confirmation popup when multiple documents exist. For more information, see Downloading Contract Documents.

Document Version Comparison

Users can now compare two versions of a contract document directly within the application. The system supports DOCX files and includes contract and supporting documents with available versions. Additions, deletions, and formatting changes are displayed inline using color-coded markup. Users can also download or print the comparison results, or search within the results. For more information, see Comparing Contract Documents.

To support document comparison using API, a new endpoint /api/clm/v1/contracts/{contractId}/\documents/compare is introduced.

Compliance Agent

Users can now run compliance checks directly from the My Contracts and All Contracts lists or from an open document in X-Author for Contracts. They can select one or more compliance checks, including GDPR and HIPAA compliance analysis, and apply them to specific contract documents across multiple contracts in a single action. In X Author, the Compliance Check action uses the same compliance workflow, reporting, and notifications as the platform experience.

Compliance results provide dimension-level findings, status indicators, recommendations, and an overall compliance assessment. The HIPAA Compliance Analysis evaluates eight HIPAA dimensions and automatically flags a FAIL when the required 60-day breach notification clause is missing. The GDPR Compliance Analysis evaluates 14 GDPR dimensions and provides overall Compliant, Review_Required, or Non-Compliant results.

Completed compliance reports are available directly in the contract's Documents tab, where authorized users can preview, download, and print reports using the contract's existing document permissions. Consolidated email notifications provide compliance results, report download links, and details of any failed analyses. Successfully generated reports remain accessible from the Documents tab, with separate versioned reports generated for each document and compliance framework. For more information, see Compliance Agent.The following APIs are introduced for compliance checks:

• GET /compliance/checks
• POST /compliance/eligibility
• POST /compliance/runs

Clause Health Dashboard with Configurable Thresholds

The Clause Health Dashboard displays aggregated semantic similarity scores for each clause type in the Clause Library, with configurable thresholds for each clause type. Users can filter the dashboard by contract type, business unit, and time period, and drill into clause deviation trends and outlier contracts for detailed analysis. Only clause types with scored contracts appear, and the dashboard updates with the latest computed scores.

Automatic Clause Comparison at Contract Execution

The system now automatically compares each executed contract clause against its corresponding approved standard clause from the Clause Library, providing a legal-context-aware similarity score. The computed score, is stored in the Semantic Similarity Score field on the Contract Clause object and is available for reporting. Clauses without a matching standard clause are skipped and do not receive a score.

Supplier Approval Status Handling with Multiple Approvers

When a supplier approval workflow is configured with multiple approvers and the Continue Policy Approval on a Reject rule is enabled, both the Approval Indicator and Supplier Status now remain as Pending Approval until all assigned approvers have completed their review actions. A rejection by an individual approver will no longer immediately set either status to Rejected. The final status is evaluated and applied only after the full approval workflow concludes. For more information, see Approval Workflow for Suppliers and Rejecting a Supplier.

Expanded Access to Clone and Delete Actions on Contract Details Page

Users are allowed access to the Clone and Delete contract actions from any left navigation tab within the contract details page. These actions remain subject to existing user permissions and are disabled or hidden when the contract is in edit mode.