ObjectDB APIs: 18-Character Identifier Field Support

Introduced the following changes to support 18-character identifiers (UID18) for custom Identifier fields:

• The Schema API (POST /api/schema/v1/objects/{objectName}/fields) now supports configuring custom Identifier fields with an 18-character format (UID18), in addition to the standard 36-character GUID.
• The Data API (POST /api/data/v1/objects/{ObjectName}) now supports creating records with UID18 fields. Leave the field empty to auto-generate a unique 18-character ID, or provide a value. The platform validates any provided ID and returns a clear error if the format is invalid.

Choose the identifier format per field: 36-character GUID or 18-character UID, based on your integration needs.

Workflow Activity Reassignment

You can now reassign an active workflow step to another user or user group directly from the CLM application, without restarting the workflow. This is useful when the assigned user is unavailable, has left the team, or when responsibilities have changed. To support this, the following workflow activities now include a new Allow Reassignment option in their configuration settings: Approval, Interactive Decision, CLM Send for Review, CLM Implicit Interactive, Document Generation, and Esignature. When a reassignment occurs, the platform notifies both the previous and new assignees and logs the change in the audit trail.

Email Delivery Status Tracking for Send Email and Bulk Email APIs

The Send Email API (POST /api/email/v1/emails) and the new Bulk Email API (POST /api/email/v2/emails/bulk) now support returning a unique DeliveryStatusTrackingId when the ShouldTrackDeliveryStatus property is enabled in the TrackingOptions payload, allowing users to trace and verify email delivery events for both single and bulk email operations using GET /api/email/v1/emails/status/batch and GET /api/email/v1/emails/jobs/{jobId}.

Workflow and Service Hooks Failure Notifications

The conga advantage platform now supports email notifications for workflow and service hooks execution failures, helping administrators proactively monitor and troubleshoot runtime issues. Notifications are triggered for failures caused by feedback loop detection and general execution faults. This feature is disabled by default. To enable it, contact Conga Support. For more information, see Workflow and Service Hooks Execution Failure Notifications.

Schedule Reports for Dashboards and Charts

Administrators can now schedule dashboards and charts to be delivered automatically by email at recurring intervals. You can set up schedules directly from the dashboard, chart, or centralized Reports tab. This enhancement helps you automate report distribution, monitor KPIs more efficiently, and manage all report schedules from a single location. You can also configure delivery settings, recipients, schedules, and output formats to meet your reporting needs.

For more information, see Scheduling a Dashboard Report, Scheduling a Chart Report, Creating a Scheduled Report from the Reports Tab, and Manage Scheduled Reports.

Callback Workflows: Execute Custom API Activity for Extensible Validation

You can now extend platform validations using the Execute Custom API activity in Callback Workflows. This feature allows you to invoke custom logic during platform events (such as approval reassignment) without modifying the core application. It enables you to control whether an operation proceeds or fails based on your custom validation logic, while supporting bulk processing and structured error handling. To support this capability, a new Callback Workflow template is introduced, allowing you to build and deploy compatible custom code using a standard structure. For more information, see Execute Custom API.

Enhanced Workflow Activity Output Handling and Workflow Stability

Introduced improvements to workflow activity output handling, dependency validation, output reusability, and workflow stability.

Improved Workflow Stability: Improves workflow execution stability when activities are added, removed, or reordered within a workflow.

Enhanced Get Record Activity Output Handling: You can now use the output of the Get Record activity directly as a Record datatype in subsequent workflow steps. This allows you to easily access and use record field values in assignments, updates, conditions, and other workflow activities without manual conversion. This simplifies passing record data between activities, mapping record attributes to workflow variables, and building workflow logic based on record values. For more details, see Get Records activity.

Prevent Deletion of Activities with Dependent Outputs in Workflow Builder: Workflow Builder now prevents deletion of a Data Transformation (DTA) or HTTP Callout V2 activity when its Activity Output is used by other workflow activities. When you try to delete one of these activities, the workflow builder displays a validation message listing the dependent activities. You must remove or update those dependencies before you can delete the activity.

Restore Activity Output on Workflow Resume: Activity Output values are now saved in the workflow instance state and restored when the workflow resumes. This ensures that Data Transformation (DTA) variables and expressions that reference Activity Output continue to work correctly after workflow suspension and resume.

HTTP Callout and Data Transformation: Direct Access to Output Fields: You can now directly access individual fields from structured outputs in HTTP Callout and Data Transformation activities within workflow expressions and activity inputs. You can:

• Expand activity outputs in workflow resource pickers (constants, activity outputs, and variables) using IntelliSense.
• Navigate nested objects and view the full output hierarchy.
• Select primitive fields such as text, numbers, or true or false values and use them directly in Criteria builders (both old and new) and activity inputs.

Existing workflows continue to work as expected.

Scheduler One-Time Job Auto-Deletion

Scheduler now automatically deletes one-time jobs after they run, so you no longer need to manage or clean up these jobs manually. This reduces unnecessary scheduler calls and improves performance, while recurring jobs continue to run as usual without any change in behavior.

Schema Manager: Global Search Support in Search Settings

Search Settings now supports Global Search configuration, allowing administrators to enable search across multiple objects using a single query. Added a new Global Search column in the Search Settings grid within Schema Manager, where administrators can select specific fields to include in Global Search after enabling Search for the field.

API Updates: Updated the existing api/search/v1/setting endpoint with these optional fields:

• IsGlobalSearchEnabled: Enables or disables Global Search for the object.
• GlobalSearchFields: Defines the list of fields included in Global Search.

These updates are backward-compatible and do not affect existing integrations.

New API Endpoint: Added a new GET /api/search/v1/global-search-data-types endpoint to return supported field data types for Global Search configuration.

For more information, see Search Settings and Search APIs.

Login as User for Administrators

Administrators can now log in as eligible internal users directly from the User Management screen using the Login as User option. This capability allows administrators to view the application exactly as the user experiences it, making it easier to:

• Troubleshoot and resolve issues faster by identifying the root cause directly from the user's perspective, without waiting for Technical Support availability.
• Train and guide users by reviewing the content and options available to them in real time.
• Validate permissions and access by verifying the settings assigned to users on specific documents, objects, and features.

By enabling self-service support and reducing dependency on external troubleshooting channels, the Login as User feature helps cut resolution times and enhances overall productivity across the organization.

For more information, see Login as User.

System Admin User: Action Restrictions

The System Admin User account is read-only and cannot be modified. To make this clear, the User Management UI no longer shows any modification options on this account. Previously, these options were visible but did not work. This update removes them to provide a clearer and more consistent experience. For more information, see User Administration.

Pre-Sync Validator for Data Sync

The Pre-Sync Validator is a new automated validation engine that checks your Data Sync configuration before a sync runs or a schedule is saved. The following changes are available in the Data Sync module:

• On the Mapped Objects screen, clicking Sync Now triggers validation before the sync starts.
• On the Sync Schedule screen, the Save button is renamed to Validate & Save and runs validation before saving the schedule.
• In Email Notification Settings, two new toggles, Enable PreSync Validation Notification and Enable PreSync Validation Notification on Schedule, let you receive validation results by email.

Soft failures display a warning and let you download a validation report before continuing. Hard failures block the sync or save action until you resolve the critical issues. Hard failures also include cases where a source object in Salesforce does not exist or is not accessible to the connected user, or where a source field exists in Salesforce but is missing in the target schema.

For more information, see Running Data Sync on Demand, Data Sync Schedule, Configuring Email Notification Settings, and Review Pre-Sync Validation Results.

Enhanced Salesforce Data Sync Capabilities and Reliability

Introduced multiple enhancements to Salesforce Data Sync to improve integration flexibility, synchronization reliability, document support, and data consistency across synced records.

• New Support for External Client App: Added support for Salesforce External Client Apps using the OAuth 2.0 Client Credentials Flow to enable secure, non-interactive server-to-server integrations. For more details, see Configure OAuth 2.0 Authentication for Salesforce Data Sync.
• Enhanced LineItem Reverse Sync Logic: Enhanced the LineItem reverse sync process with automatic retry logic to handle intermittent connection and server interruptions, improving synchronization reliability.
• Salesforce Content Libraries Sync Support: Added support for synchronizing executed agreement documents stored as Salesforce ContentVersion files within Salesforce Content Libraries into the Conga Advantage Platform.
• Support Multiple Target Objects in Forward Sync: You can now configure multiple forward sync mappings for a single Salesforce object. The system also supports dependent lookup field synchronization after related records are synced.
• Sync Attributes from Primary to Secondary Line Items: Enhanced reverse sync to automatically copy attribute lookup values from primary line items to related secondary charge line items. This behavior is controlled by a flag:
  • When true: During reverse sync, secondary line items inherit and display the attribute values from their parent primary line item.
  • When false: The system follows the existing behavior. It does not sync attributes from primary to secondary line items.
• Scheduled Data Sync User Context Preservation: Scheduled data sync always runs in the context of the user who originally created the schedule. This behavior remains unchanged even if other users update Salesforce settings, platform configurations, or modify the schedule. Each schedule continues to use its original user context, ensuring consistent execution and reducing permission-related sync failures.

Telemetry Logs Enhancements

• Log Details Panel: A new Log Details panel lets you view log metadata, copy identifiers such as Trace ID and Span ID, and review log output details (error messages, stack traces, and informational messages) while navigating between logs without losing your current filters.
• Log Listing with Span ID: The log listing page now displays the Span ID and Duration of each operation, helping you better trace and analyze requests across services.
• Service Name Filtering: Telemetry logs now show entries for custom code services by default, helping reduce unnecessary logs.
• Export Larger Logs: You can now export larger log files, with increased limits from 5 MB to 20 MB.

For more information, see Telemetry Logs and Log Details.

Enhanced List View Editing and UI Rule Handling

Improved list view usability and UI rule behavior to simplify data management and provide a more consistent editing experience.

Long Text Fields Display as Text Areas in List Views

List and grid views now display long text (LONGSTRING) fields as editable text areas, allowing you to read and update lengthy content directly from the grid without opening the details page. You can expand long content using the Show more option and edit multiline text directly within the list view. The application automatically saves changes when the field loses focus.

CX Studio UI Rules Clear Hidden Field Values on Save

CX Studio now automatically clears field values when a UI visibility rule hides a field at the time you save a record. If the field becomes visible again later, the application displays the field as empty, ensuring more consistent and predictable UI behavior. This change affects only fields hidden by UI visibility rules during save and does not affect visible fields or values cleared manually.