Document Version in Activity History for Microsoft 365 Review

When users send a document for Microsoft 365 review, the system logs the document version and review email content in the contract’s Activity History.

To enable logging for internal review, the administrator must configure the APTS_DefaultEmailContactName admin entry with a dummy contact name. This configuration is required to create an Email: Subject entry in the agreement record’s Activity History related list after the review email is sent. It is a standard Salesforce behavior, if the admin entry is missing or contains an invalid value, the system does not record the email details in the Activity History.

For more information, see Sending an Agreement Document for Review in Sending an Agreement Document for Collaborative Review Using Microsoft 365 Review and APTS_DefaultEmailContactName.

Embedded Conga CLM Experience for Salesforce Lightning

Users can now access and manage Conga CLM for Advantage Platform Contracts and Contract Requests directly from Salesforce Lightning Account and Opportunity records. The integration automatically synchronizes Account, Opportunity, and Contact data between Salesforce and Advantage Platform, with parent object creation orchestrated via Workato middleware. All contract and contract request operations including viewing, creating, editing, and workflow management are performed within the embedded Advantage Platform UI, ensuring that all contract-related data resides exclusively on the Advantage Platform and eliminating the need for custom Salesforce forms or duplicate contract data in Salesforce.

A unified landing page in Salesforce Sales Cloud provides access to all core Conga CLM features, including All Contracts, All Requests, Conga Approvals, Obligation Fulfillments, Contract Search, and Contract Dashboards.

The embedded interface supports context-preserving navigation, allowing users to move between Accounts, Opportunities, and Contracts while maintaining accurate contract lists and standard Salesforce navigation features. Real-time updates and notifications are provided within Salesforce when contract statuses change, with direct navigation to the embedded contract view. Responsive design and user-friendly error handling are supported throughout the integration.

For more information, see Salesforce Integration with Conga CLM topic in CLM for Advantage Platform administrator guide and Salesforce Embedded Experience in Conga CLM topic in CLM for Advantage Platform user guide.

Select All/Deselect All Checkbox for Document Attachments on Activate Agreement

The Activate Agreement pop-up now displays a Select All/Deselect All checkbox above the document list, allowing contract managers to quickly select or deselect all documents for email attachment. This enhancement applies only to Salesforce Lightning. For information, see Activating an Agreement in Salesforce Lightning.

Column Width Adjustments on Select Attachments Page

The File Name column on the Select Attachments page in the Send for Adobe Sign workflow now displays more characters and wraps text, allowing users to view the complete file name without hovering. Column widths and margins have been optimized to fit all columns within standard desktop viewports, eliminating the need for horizontal scrolling.

Obligation Fulfillment Due Date Reminder

Assignees receive email reminders based on each obligation's Reminder (days before due) and Notification Frequency settings. Reminders adjust automatically if a due date changes and stop once the due date passes. Notifications apply only to obligation fulfillments; reminders are configured at the obligation level (Reminder (days before due)) but are triggered based on the due date of individual fulfillment records. For more information, see Setting Up Reminders for Obligations.

Field Mapping from Obligation to Fulfillment

When an agreement is activated, each obligation creates a fulfillment record that copies over the Assignee, Reviewer, Name, Status and Due Date fields — including any blanks. This happens once at activation; later changes to the obligation won't affect existing fulfillment records, but contract managers can update them manually. For more information, see Obligation Fulfillment.

Obligation Management UI Field Updates

The Obligation Management interface hides unused fields and renames Agreement Clause ID to Agreement Clause Name. Two new fields are added: a Reviewer lookup and an optional Reminder field (positive whole numbers only) for advance notifications. New installations apply these changes automatically; existing installations need manual layout updates. For more information, see Agreement Obligations.

Filter Supported Documents for Office 365 Review

Contract Managers can filter document selections for Office 365 Review by enabling the Exclude Transient and Checked Out Documents setting, which hides documents marked as transient or checked out in X-Author.

Also, a validation is implemented that requires at least one .DOCX file in the selection to proceed with the review cycle, and displays a validation error if none are included.

For more information, see Sending an Agreement Document for Review in Sending an Agreement Document for Collaborative Review Using Microsoft 365 Review.

External Recipient Warning and Visual Indicators

When selecting recipients for review or signature, the system flags external recipients by showing an info banner and highlighting recipient chips. The indicators clear automatically once all external recipients are removed. This feature helps contract managers detect unintended external recipients before sending, reducing accidental data sharing. For more information, see APTS_InternalEmailDomains and APTS_ValidateAccountDomain.

Enhanced Recipient Chip Hover Text

Recipient chips across send for review and send for signature pages now display both the full name and email address in a standardized tooltip format: “Full Name [[email protected]]". This enhancement applies to the To, CC, and BCC fields in Send for Review (offline and parallel), Send for O365 Review (all variations), Google Review, and Send for Signature pages. It also includes recipient chips in the parallel review initiation section when Recipients for Parallel Review Notification section is enabled, ensuring a consistent and more informative hover experience across all supported workflows. For more information, see -

• Sending an Agreement Document for Review
• Sending an Agreement Document for Parallel Review
• Sending an Agreement Document for Collaborative Review Using Microsoft 365 Review
• Sending an Agreement Document for Google Docs Review
• Sending an Agreement for Manual Signatures