Conversations Page and Global Inbox Enhancements

Users with the required permissions can now initiate new conversation posts directly from the All Conversations, My Conversations, and Unread Conversations views without navigating into individual records. The Create Post modal enables adding a subject, participants (including internal and external users), rich-text message content with @mention support, attachments (up to 10 files, 21 MB total), and linking the conversation to a specific context object and record. Submitted conversations appear at the top of the active view and on the context record's Conversations tab, with notifications sent to all participants and mentioned users. see Creating a Post and Conversations.

The API enhancements include the following endpoints:

• GET /api/conversations/v1/supported-object-names, which returns a list of supported object names and their display names for initiating conversations.

• POST /api/conversations/v1/view-conversations/my-records/query and POST /api/conversations/v1/view-conversations/my-records/search for retrieving and searching conversations in the global inbox.

These updates support integration and automation scenarios, and ensure real-time updates reflecting changes in record ownership. For more information, see Conga Developer Portal.

Obligation Management and Fulfilment Enhancements

This release delivers the following enhancements to obligation and fulfilment management in Conga CLM, improving visibility, assignment accuracy, and compliance tracking across both classic UI and modern UI.

• Fulfilments visible across all post-activation contract statuses: Fulfilment records are now accessible at every stage of a contract's lifecycle after activation, not just in active status. Contract managers and users can refer to fulfilment history at any point without the contract needing to be in a specific state.
• Dynamic assignee and reviewer lookup based on accountable party: When assigning obligations, the assignee and reviewer lookup now filters based on the accountable party. If the obligation is internal, the lookup returns internal users. If it is external, supplier contacts and customer contacts are surfaced. Contract managers no longer need to manually identify the correct pool of assignees before assigning. The "Print on contract" toggle defaults to off for internal and on for external accountable parties, but remains user-configurable. For more information, see Creating an Obligation.
• Implicit contract access for obligation assignees. When a contract manager assigns an obligation to an internal user, that user automatically receives read access to the associated contract record. Assignees can now access contract records without requiring a separate access grant from the contract manager or an administrator. This applies to both individual users and user groups, excluding external parties. For more information, see Creating an Obligation.
• Assignee and reviewer visibility: The Manage Fulfilment listing page and the Fulfilment Details page in the modern UI now display the assigned user or user group alongside each fulfilment record, giving contract managers instant visibility of ownership without opening individual records. The listing page sorts fulfilments in ascending order by Due date by default.
• Supplier contact notifications for obligation fulfilments: Supplier contacts assigned to obligations now receive automated email notifications at four points: on contract activation (a consolidated summary of all obligations assigned to them), seven days before each fulfilment due date, on the due date itself, and seven days after the due date if the fulfilment remains incomplete. These notifications help external parties stay informed and act before non-compliance occurs. Notifications are not sent for obligations linked to expired, terminated, canceled, or inactivated contracts. These notifications are sent only for buy-side contracts where the accountable party is external and the assignee is a supplier contact.
• Locked edit on terminal-status fulfilments: The Edit option is now hidden on fulfilment records in a terminal status. This prevents post-completion modifications and preserves the integrity of the audit trail. This enhancement applies to classic UI and modern UI. For more information, see Obligation Fulfillment Lifecycle.
• Auto-removal of obligations on clause deletion (X-Author): When a clause is deleted from a contract document in X-Author and checked in, all obligations associated with that clause are automatically removed from the contract.
• Renamed filter views in Manage Fulfilment: The filter views on the Manage Fulfilment page are now labelled Overdue Fulfilments and Upcoming Fulfilments.
• All fulfillment records displayed: The Manage Fulfilment page and the Obligations tab in Supplier record display all fulfillment records across all statuses. For recurring fulfilments, only the upcoming fulfilment is displayed to prevent duplicate records. For more information, see Obligation Fulfillment in the Modern UI and Supplier Obligations.

Supplier Request and Supplier Enhancements

The Supplier Requests form now requires separate First Name and Last Name fields for supplier contacts, improving data structure and communication accuracy. For more information, see Creating a Supplier Request.

The Active toggle controls the Enable Login toggle, ensuring that only active contacts can have login access, and the Primary Contact option is restricted to active contacts. These changes also apply to the Create Supplier and Create Location screens. The Contact List page introduces an Enable Login column, displaying and filtering supplier contact login status when the Supplier Portal setting is enabled in CLM Admin. A mandatory Email Domain field is now present on each Supplier record, enforcing that all supplier contact email addresses match the configured domain, including sub-domains. For more information, see Supplier Fields.

The Supplier Profile features an Obligations tab, providing a centralized view of all obligation fulfillments across contracts and statuses. Supplier managers can search, sort, and filter fulfillments by Fulfillment Number, Status, Assignee, Reviewer, and Due Date, and access saved views for *O*verdue, Upcoming, and All Fulfillments. Selecting a fulfillment number opens a unified view with Details and Activity History tabs, displaying key fields and a comprehensive activity log. Supplier managers can submit or waive fulfillments in "Pending Fulfillment" status, and accept, reject, or request information for fulfillments in "Pending Review" status, with all comments and documents synchronized across contract records and Manage Fulfillment pages. Action buttons are available based on user permissions and feature flag status. For more information, see Obligations.

Bulk Amendments

Contract managers can now apply the same amendment to multiple active contracts of the same type in a single guided request, eliminating the need to amend contracts individually. They can upload contract and amendment-specific information through an attribute file, provide the amendment content, and select the applicable contract type and document template. Conga CLM validates and processes the contracts in the background, generates amendment documents, and moves successfully processed contracts to Ready for Signatures.

Managers can monitor processing progress, review successful and failed contracts, download a per-contract processing log, and send successfully amended contracts to signatories together through the organization's default signature provider. For more information, see Bulk Amendments.

CLM supports the following REST APIs for Bulk Amendments:

• GET /api/clm/v1/contracts/amendments/bulk/excel-template
• POST /api/clm/v1/contracts/amendments/bulk
• GET /api/clm/v1/bulk-amendment-requests
• GET /api/clm/v1/bulk-amendment-requests/{id}/download-log
• POST /api/clm/v1/contracts/amendments/bulk/{id}/send-for-signature

My Conversations

Access the My Conversations view to display all conversations where the user is an initiator, participant, or mentioned party, regardless of context. The view supports searching by subject and entity, sorting by Conversation Thread object fields, and pagination. Only conversations linked to entities where the user is involved are displayed.

The Unread toggle, available in both My Conversations and All Conversations views, helps to filter and display only conversations with unread messages. The toggle in My Conversations defaults to ON. Unread conversations are visually distinguished with a highlighted background, bold titles, and an unread count badge in the Messages column, while read conversations remain visible when the toggle is OFF.

The Entity ID field in the conversations list displays the relevant functional ID as a hyperlink for direct navigation. The Entity ID shows the Contract Number for contracts, Request Number for requests, Account Number for accounts, and Supplier Code for suppliers; for contract requests without a functional ID, the object ID is displayed. This update enables users to quickly access associated records from the conversations list, supporting traceability across all contexts. For more information, see Conversations.

The API endpoints /api/conversations/v1/view-conversations/query and /api/conversations/v1/view-conversations/search enable retrieval and search of conversations with detailed metadata, including subject, role, messages, and entity links. For more information, see Conga Developer Portal.

Contract Amendment Support for Microsoft Dynamics 365

Conga CLM now supports initiating contract amendments directly from upsell or cross-sell Opportunity records in Microsoft Dynamics 365 through the embedded Conga CLM experience.

When users select Amend Contract, Conga CLM triggers the amendment workflow through Workato and creates an Amendment Contract while maintaining the parent-child relationship with the original contract. The embedded Conga CLM interface then opens the new Amendment Contract in edit mode, pre-populated with data from the original agreement based on the configured Amendment clonespec rules. Users can confirm the contract creation and return to the Opportunity Contract Listing or Opportunity record as needed.

The following enhancements support the contract amendment process:

• Request Type field: The Opportunity object now includes a Request Type picklist field in the Conga CLM Details section. Users can select New Contract (default) or Amendment to indicate whether the Opportunity is for new business or a contract amendment.
• Previous Opportunity and Contract details: When users select Amendment, the Previous Opportunity lookup field becomes available and is filtered based on the Account. The Previous Contract Number formula field is automatically populated with the contract reference information for tracking and reporting.
• Line item synchronization: The Sync Lines button now adds line items from the Amendment Opportunity without removing existing line items from the original Opportunity, ensuring that line items remain tracked across both the original and amended contracts.

For more information, see Amending a Contract from an Opportunity.

Conga CLM Data Write-Back and Document Synchronization for Microsoft Dynamics 365

After a contract is fully executed, Conga CLM can now automatically write back the signed agreement PDF to the related Microsoft Dynamics 365 record. The executed document is stored as a file and linked to the associated Account or Opportunity, enabling sales teams to access finalized agreements directly from Dynamics 365 without switching applications. This enhancement improves document visibility, streamlines contract management processes, and ensures signed agreements remain accessible within the CRM system. SharePoint integration must be configured in Microsoft Dynamics 365 to support document storage. For more information, see Viewing Contracts for an Opportunity and Viewing the Executed Document for an Opportunity.

Contract Management API and User Interface Enhancements

This release introduces key functional enhancements across Conga CLM administration, contract relationship management, clause tracking, and document navigation to streamline contracting workflows and enforce compliance.

• Document Requirements by Contract Type: Administrators can define whether specific document types are mandatory or optional for each contract type and action. This can be managed individually or in bulk via the Document Requirement Type card in App Settings. When initiating the Send for Signature action, the system validates that all mandatory documents are present. If any required documents are missing, the action is blocked, and an alert lists the missing document types to prevent incomplete contracts from moving forward. Validation supports both custom record types and custom document types.For more information, see Configuring Document Requirements.

  The REST API endpoint /api/clm/v1/settings/documents/contract-type-requirements is introduced. For more information, see Conga Developer Portal.

• Account and Supplier Filtering in Contract Relationships: When adding relationships in the Relationships tab, lookup results are automatically filtered by default to show only contracts associated with the current contract's Account or Supplier. Users can expand search criteria using the Advanced search option to filter by Account/Supplier, Contract Type, and Status Category when linking related agreements. For more information, see Contract Relationships.
• In-Effect View for Clauses: The In-Effect View excludes deleted clauses and displays only active clauses, providing contract managers with a clear, reliable representation of currently binding terms.
• Multi-Document Navigation for DAI-Extracted Contracts: For contracts containing multiple documents extracted via DAI, distinct functional links are available for each document, allowing users to open each document directly in a new tab from the contract record. The Adobe Sign button is automatically hidden for organizations or profiles where Adobe Sign is not enabled, preventing clutter and the display of unavailable e-signature options.

Supplier Sanctions Screening

This release introduces the Supplier Sanctions Screening feature that integrates on-demand sanctions checks within the CLM Advantage platform, enabling screening, blocking, and unblocking of suppliers directly from the All suppliers, My suppliers, or supplier profile pages. Initiate checks against the OFAC SDN and UN Consolidated sanctions lists for one or multiple suppliers (up to 10 per run). Sanctions data is sourced from the OFAC SDN and UN Consolidated lists. The screening process uses a dedicated AI skill with exact-match logic, does not expose scores or confidence values, and never auto-blocks suppliers. Each screening returns a binary result, Match Found or Match Not Found, per list, with results delivered via email as per-supplier, per-list PDF reports. The latest screening outcome is displayed on the supplier profile, and failed screenings are flagged in the email without generating a report.

A dedicated Sanctions Screening Status field is now available on supplier records, displaying Not Screened, Pending Review, Clear, or Blocked, independently of the existing Supplier Status. This field reflects the latest sanctions screening outcome and any block or unblock actions, and is visually distinct from both Supplier Status and Sanctions Screening Result. All transitions to Pending Review, Blocked, or Clear are recorded in Activity History, while the field remains hidden from suppliers in the portal.

Administrators and authorized users can view sanctions status, activity history, and report artifacts, with all actions reflected consistently across supplier records. Blocking is permission-controlled and enforced across all related contracts, including visual indicators and deactivation of contract actions. Blocked suppliers are unselectable during contract creation. All block and unblock actions are recorded in the Activity History audit trail. The block status and screening results remain internal and are not visible to suppliers on the supplier portal.

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

Cycle Time Report and Dashboard Enhancements

The Cycle Time Report and Dashboard now include the ‘Approval Status (Indicator)’. 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 Review Cycle Revamp and Recipient Management

This release introduces comprehensive enhancements to the contract review cycle experience on the Conga Advantage Platform, focusing on structured review workflows, recipient eligibility, and API-driven review management.

Recipient selection now strictly enforces eligibility based on the selected Review Scope-Type, supporting O365 Active Directory users, CLM users, Contacts, and External Users according to a defined matrix. The system automatically determines and displays eligible recipients, ensuring correct notification and reporting behavior. CC and BCC fields in Simple reviews allow all recipient types except O365 Active Directory users, with no restrictions on account association for Contacts or External email addresses. For more information, see Configuring Review Settings.

Out-of-the-box team roles for internal and external review are introduced, enabling distinct flows for each review type. For more information, see Action Permissions.

The Add New Team Member(s) workflow now requires selecting a team role first, dynamically displaying only the applicable member types based on the chosen role to prevent invalid combinations. For more information, see Creating a Team Role and Creating a Contract Team.

The Review Cycle card displays an inline tag indicating whether a review cycle is Internal or External, allowing instant identification of the review scope. Notification enhancements provide contextual updates throughout the review cycle for all stakeholders, and reviewer responses are automatically captured as new document sub-versions with full metadata. For more information, see Sending a Contract for Review (Modern UI).

The following comprehensive suite of REST APIs are introduced that allow contract managers to create and initiate multi-document review groups:

• POST /api/clm/v1/contracts/{contractId}/review-groups - Create and initiate multi-document review groups.

• GET /api/clm/v1/contracts/{contractId}/review-groups - List all active or historical review groups.

• GET /api/clm/v1/contracts/{contractId}/review-groups/{reviewGroupId} - Retrieve granular cycle and reviewer progress.

• GET /api/clm/v1/contracts/{contractId}/review-groups/{reviewType}/{searchString} (with the reviewScope query parameter) - Dynamically query eligible internal or external recipients.

• POST /api/clm/v1/contracts/{contractId}/review-groups/{reviewGroupId}/reviews/{reviewId}/reviewers - Enable dynamic reviewer and cycle lifecycle operations without restarting workflows, including adding reviewers.

• POST /api/clm/v1/contracts/{contractId}/review-groups/{reviewGroupId}/reviews/{reviewId}/reviewers/{reviewerId}/end - Completing an individual review with optional document sub-version check-in.

• POST /api/clm/v1/contracts/{contractId}/review-groups/{reviewGroupId}/reviews/{reviewId}/reviewers/{reviewerId}/cancel - Revoking reviewer access.

• POST /api/clm/v1/contracts/{contractId}/review-groups/{reviewGroupId}/reviews/{reviewId}/end or POST /api/clm/v1/contracts/{contractId}/reviews/{reviewId}/end - Concluding review cycles with optional reconciliation.

• POST /api/clm/v1/contracts/{contractId}/review-groups/{reviewGroupId}/reviews/{reviewId}/cancel - Canceling review cycles.

Document Comparison for Contracts

Contract managers 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.

Org-Level Contract Language Analysis Dashboard

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.

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.

For more information, see Clause Comparison and Similarity Analysis.

Out-of-the-Box Roles and Permission Groups for Conga CLM

Conga CLM now provides the following six predefined, out-of-the-box (OOTB) roles, each paired with a corresponding permission group. These roles and permission groups are available upon installation, enabling administrators to assign, clone, or customize them to meet organizational requirements without building permissions from scratch. Each OOTB role is designed for specific contract lifecycle responsibilities:

• Requester enables users to initiate and track contract requests, with restrictions on negotiation, document generation, eSignature, and administrative functions.
• Contract Manager provides broad access to contract lifecycle activities, including contract creation, negotiation, document generation, eSignature, and reporting, while restricting system administration and record deletion.
• Legal grants in-house legal users full access to negotiation, redlining, eSignature, and clause management, while restricting system administration.
• Template Admin allows management of contract templates and clause libraries, including creation and maintenance, without access to contract execution or system administration.
• Platform System Admin offers unrestricted access to all CLM capabilities, including contract management, approval routing, document management, user and permission management, and system settings.
• Read Only provides view-only access to contract records and reports, restricting all create, edit, action, and administrative permissions.

For new tenants, only the current OOTB CLM roles are visible during setup and administration, with legacy roles hidden to promote standardized configurations. Existing tenants retain access to both legacy and new OOTB roles, with all user assignments and permission groups remaining unchanged. The CongaCLMReadOnlyUser role continues to be available for both new and existing tenants.

Administrators can extend access by adding additional permission groups or clone the default permission groups to create custom variants, ensuring flexibility without altering the base configuration. This standardized approach reduces manual configuration effort, minimizes the risk of misconfigured permissions, and accelerates user onboarding and acceptance testing. For more information, see Out-of-the-Box Roles.

Compliance Agent: Contract Compliance Screening, Reporting, and Document Management

This release introduces the Compliance Agent that provides on-demand contract compliance screening within the CLM Advantage Platform, allowing users to initiate compliance checks from the My Contracts or All Contracts lists, contract details page, or directly within X Author for Contracts. Use the Run Compliance Check wizard to select one or more contracts and target specific documents for analysis. The wizard supports bulk selection and enables the application of multiple compliance checks, such as GDPR Compliance Analysis (14 dimensions) and HIPAA Compliance Analysis (8 dimensions), in a single action. The Run Compliance button is available in the contract list toolbars, activating when one or more contracts are selected, with a 10-contracts-per-run limit.

Compliance results are delivered via consolidated email notifications, including contract, document, framework, verdict summary, and download links for each report. Only successfully generated reports are listed and accessible directly in the contract's Documents tab as documents of type "Compliance Report," inheriting standard permissions and filtering capabilities. All compliance reports, including version history, are now managed exclusively through the Documents tab. Users can preview, download, and print completed compliance reports, which include a title, executive summary, overall compliance score, findings counts, and detailed dimension-level results with recommendations. Downloaded files use meaningful names reflecting the document and check.

The GDPR Compliance Analysis skill evaluates 14 dimensions, providing PASS, WARNING, or FAIL status per dimension and an overall status of COMPLIANT, REVIEW_REQUIRED, or NON_COMPLIANT. The HIPAA Compliance Analysis skill covers 8 dimensions and automatically flags a FAIL if the 60-day breach notification clause is missing. Both skills generate versioned reports per document and framework, using a unified output format. Analysis failures are communicated via email and in-app notifications, and users can re-run checks as needed. For more information, see Compliance Agent.

The GET /compliance/checks, POST /compliance/eligibility, and POST /compliance/runs APIs power the workflow, supporting extensibility for future compliance frameworks without UI changes. For more information, see Conga Developer Portal.

Streamlined Request-to-Signature Flow for Unilateral NDAs

Administrators can use the out-of-the-box Unilateral NDA configuration included with 0-60 setup, to streamline the contract request and creation process. Business users can submit a Unilateral NDA request and automatically progress through request approval, contract creation, and document generation.

The following enhancements are available:

• Out-of-the-box Unilateral NDA configuration: Administrators can use the pre-seeded legal template, template filter rule, contract request form, and staged workflow provided for the Unilateral NDA contract type without manually configuring these assets.
• Automated request approval: Unilateral NDA requests are automatically approved upon submission, triggering contract creation and document generation without requiring manual approval.
• Automated document generation: The system automatically generates the Unilateral NDA document in PDF format using the seeded template when the contract is created.
• Requester notification: After the document is generated, the requester receives an email notification with a direct link to the contract record and can proceed with sending the document for signature.
• Automatic team member carryover: Team members added to the contract request are automatically added to the resulting contract record, eliminating duplicate data entry.

Enhanced Amendment Management & In-Effect View

Conga CLM introduces the Delta Amendment Model alongside significant enhancements to Amend and Clone Settings and the In-Effect View. This release empowers organizations to maintain legally accurate, cumulative contract amendment chains, eliminate data duplication, and configure copy rules and runtime views through an intuitive administrative UI.

• Delta Amendment Model (Amended Contracts)

  Administrators can configure the amendment model per contract type using the Enable Delta Amendment setting under CLM Admin Setup > General Settings. When this toggled is turned on, the system switches from the Full Copy model to the cumulative Delta Amendment model without impacting existing standard workflows. For more information, see General Settings.

  The Amend and Clone Settings replaces legacy JSON-based clone specifications (clonespec) with a structured, intuitive interface under Implementation Tasks. Administrators can independently configure default copy behaviors, field exclusions, expression-based field mappings, and document copy rules (Copy All, Copy Latest, or Do Not Copy) for both Amend and Clone actions across various contract record types. For more information, see Amend and Clone Settings.

  In the Delta model, users can initiate the Amend action exclusively from the base contract record. The system copies header fields and carries forward the Base Final document from the latest amendment into the newly created amendment record. The base contract cycles between In Effect/Being Amended and In Effect/Amended, while all prior amendment records remain active (In Effect/Activated) to form a cumulative legal agreement.Amendment records automatically receive decimal version increments (for example, 100.1, 100.2) and an automated Is Amendment system flag for instant filtering and reporting.During contract activation in the Delta flow, the system automatically selects and locks the Base Final document alongside the Executed document to guarantee document lineage.A dedicated, standalone View Amendments page accessible directly from the contract detail page displays the entire amendment chain, version history, execution statuses, and direct download links for Base Final and Executed documents.The check-in service stamps the originating DOCX ID into generated PDF metadata to ensure trace-back capabilities. Agreement clause schemas maintain an IsLatest flag, automatically updating historical clause entries when modifications occur.

  The following endpoints are introduced or updated:

  • POST /api/clm/v1/contracts/{contractId}/hierarchy/query: Retrieves the full parent-child amendment hierarchy for a contract, returning the base record and every amendment in the chain along with document metadata, including the Base Final document for each record.

  • POST /api/clm/v1/contracts/{contractId}/documents/querywithreview​: Retrieves a list of contract documents with review information. Each document now indicates whether it is the Base Final document, making it easier to identify the finalized document.

  • POST /api/clm/v1/contracts/{contractId}/activate: Activates a contract using its executed documents. When the Delta Amendment model is enabled, the Base Final document is automatically selected and locked along with the Executed document. The API also applies the appropriate status changes to the base contract and amendments and returns an error if the Base Final document is not included.

  • POST /api/clm/v1/contracts/{contractId}/amend​​: Creates an amendment from a base contract. With the Delta Amendment model enabled, amendments can be created only from the base contract. The new amendment includes the relevant contract information and the Base Final document from the latest amendment, with the appropriate status changes applied.

  • POST /api/clm/v1/contracts/{contractId}/cancel: Cancels an amendment. With the Delta Amendment model enabled, canceling an amendment returns the base contract to In Effect / Amended and marks the canceled amendment as Canceled without changing other amendments in the chain.

  • GET /api/clm/v1/clone-specs: Returns a paginated, searchable list of configured Amend/Clone specifications, parsing each stored config name into its action and record type. Supports skip/limit pagination, sorting, and a search expression that matches on action or record type.

  • POST /api/clm/v1/clone-specs: Retrieves a searchable and paginated list of configured Amend and Clone specifications. The results identify the action and record type for each configuration and support sorting and search.

  • POST /api/clm/v1/clone-specs/{action}- Retrieves the configuration for an Amend or Clone action in a format that can be used to display and manage the settings. The response includes object mappings, field selections, field counts, and information about which settings can be edited.

  • PUT /api/clm/v1/clone-specs/{action}: Updates selected fields in an Amend or Clone specification without changing the other existing settings.

  • DELETE /api/clm/v1/clone-specs/{action}/{source}: Removes an unlocked object from an Amend or Clone specification. Core objects such as Agreement, Agreement Clause, and Documents cannot be removed.

  • DELETE /api/clm/v1/clone-specs/{actionType}/record-type/{recordType}: Deletes the complete Amend or Clone specification for a specific record type. The shared default configuration is protected and cannot be deleted.

  • GET /api/clm/v1/clone-specs/{actionType}/objects: Retrieves related objects that can be added to an Amend or Clone specification. The response identifies objects that are already configured and includes the Documents option.

  For more information, see Conga Developer Portal.

• In-Effect View: A new administrative setting under Implementation Tasks allows administrators to visually customize the In-Effect View. Administrators can select, reorder, and display up to 30 contract header fields, as well as add standard or custom related child objects (such as Agreement Clauses, Documents, Contract Teams, and Obligations) and configure up to 5 column fields per related list. This setting is pre-configured with out-of-the-box defaults (Contract Name, Start/End Dates, Term Months, Total Contract Value, Clauses, and Documents) and supports tailored view configurations for specific contract types. For more information, see In-Effect View Settings.

  Users can access the In-Effect View from any record in the amendment chain to view a unified summary of the latest active contract state, including cumulative field values, current clause language, and executed documents. The view automatically renders all enabled sections expanded by default, displaying progress indicators during load and "No Records to Display" placeholders when no child records exist. Field headers and detail labels show configured display names and localized translations. For more information, see In-Effect View.

  The following endpoints are introduced or updated:

  • GET /api/clm/v1/settings/in-effect-view/record-types: Retrieves the record types that are available to configure for the In-Effect View. Record types that are already configured are excluded.

  • POST /api/clm/v1/settings/in-effect-view/query: Retrieves the record types configured for the In-Effect View, with support for search and pagination.

  • GET /api/clm/v1/settings/in-effect-view?contractType={contractType}: Retrieves the In-Effect View layout configured for a record type. If no record-type-specific layout exists, the default layout is used.

  • POST /api/clm/v1/settings/in-effect-view: Creates In-Effect View settings for one or more record types using the default configuration as a starting point.

  • PUT /api/clm/v1/settings/in-effect-view/{id}: Updates the fields displayed for an In-Effect View configuration. System-defined clause and document entries cannot be modified.

  • DELETE /api/clm/v1/settings/in-effect-view/{id}:Removes a user-added object from an In-Effect View configuration. Core objects such as Agreement, Agreement Clause, and Document Metadata cannot be removed.

  • DELETE /api/clm/v1/settings/in-effect-view?contractType={contractType}: Deletes the In-Effect View configuration for a specific record type. The default configuration is protected and cannot be deleted.

  • GET /api/clm/v1/settings/in-effect-view/objects?contractType={contractType}:Retrieves related objects that can be added to an In-Effect View configuration. Objects that are already configured are excluded.

  • POST /api/clm/v1/settings/in-effect-view/objects: Adds one or more related objects to an In-Effect View configuration. The objects are added without any fields selected, so administrators can configure the fields to display.

  • GET /api/clm/v1/contracts/{contractId}/in-effect-view/details: Retrieves contract details and version changes across the amendment chain. When the Delta Amendment feature is enabled, the displayed fields are based on the configured In-Effect View settings and include their configured display labels.

  • GET /api/clm/v1/contracts/{contractId}/in-effect-view/clauses & GET /api/clm/v1/contracts/{contractId}/in-effect-view/documents: Retrieves the cumulative clauses and documents across the amendment chain. When the Delta Amendment feature is enabled, the APIs support optional pagination and return the total number of unique records, making it easier to display large result sets.

  • POST /api/clm/v1/contracts/{contractId}/in-effect-view/{relatedObjectName}: Retrieves configured fields for a related object across the complete amendment chain. The results can be paginated to support large sets of related records.

    For more information, see Conga Developer Portal.

Supplier Contact Login Creation, Provisioning, and Onboarding Workflow

This release introduces a comprehensive workflow within the SRM platform for managing supplier contacts, provisioning portal logins, and onboarding suppliers. Procurement teams can add or update named contacts on supplier records, designate primary contacts, and control portal access using the Enable Login toggle. Enabling login automatically provisions a user in User Management with a seeded permission group, while disabling login immediately restricts portal access. The email field becomes locked after login creation, and attempts to edit it display an inline message explaining the restriction. For more information, Supplier Fields.

The onboarding process uses out-of-the-box, merge-field-driven email templates under the SupplierEmailTemplates category. These templates are public, HTML-based, and supporting merge fields such as TemplateData.FirstName, TemplateData.LastName, TemplateData.SupplierName, and TemplateData.ActivationLink. A new default templates SupplierPortalInvitation_NewSupplierContact notifies supplier contacts (new or existing) when provisioning access is given to the Supplier Portal, and SupplierPortalInvitation_SupplierContactLoginDisabled, notifies supplier contacts when their portal login is disabled. The system automatically sends a branded invitation email with a secure token-based activation link, directing supplier contacts to OTP verification and password setup. Administrators can add additional templates as needed, and per-send customization is supported without altering the saved template. For more information, see Email Template Management.

All actions related to supplier contact creation, updates, login provisioning, and invitation dispatch are recorded in the supplier’s audit trail. This log captures event details, including acting user, timestamps, and status changes, and is accessible in the Activity History tab on the supplier record. Audit entries are filterable by event type and date range, supporting compliance and governance requirements. Audit data is stored separately from transactional data and cannot be edited or deleted by any user. For more information, see Audit and Access Dashboard and Activity History.

Recycle Bin for Contract Documents

The Recycle Bin feature provides a secure repository for soft-deleted contract documents, allowing users to view and download their own deleted files, while administrators have access to all deleted records. Restoration of contract documents is not supported; only document download is permitted. Deleted documents are automatically purged after a configurable retention period, and administrators can manually delete records before this period ends. All deletion, download, and purge activities are tracked in comprehensive audit logs.

Role-based access controls restrict visibility to authorized users, and the recycle bin interface supports search and filtering by metadata, dates, counterparties, and contract types. This ensures efficient retrieval for audit, compliance, and investigation purposes, while maintaining data integrity and a complete audit trail.

For more information, see Recycle Bin.