Cross-Object Expression Evaluation in Pre-Trigger Workflows

The Pre-Trigger Workflow Engine now supports cross-object formula expressions during Before-Save processing, enabling evaluation of relationship-based data such as parent, lookup, and sibling records in both single and bulk execution modes. The engine parses and resolves valid relationship paths, fetches related data in bulk for batch operations, and handles null or invalid references by returning null or empty values without errors. For more information, see Creating Cross-Object Formula Expressions.

Confidential Client Connection Type for UI-to-API Connections

Administrators can now create a Confidential Client connection from the Conga API Connections screen. This connection type supports web applications that can securely store a client secret, such as enterprise AI clients like Microsoft Copilot.

Previously, UI-to-API connections supported only public clients, which authenticate using a client ID. Confidential clients use both a client ID and a client secret for authentication.

For more information, see Configuring UI-to-API Connection (Confidential).

Migration Manager: Record-Level Workflow Definition Selection

Administrators can now select specific workflow definitions under the Extensibility tab for migration. You can search and filter workflow definitions and migrate only the selected records, helping reduce migration time. Migration Manager also validates the selected workflow definitions and their dependencies before migration. Existing bulk migration functionality remains available. For more information, see Performing Selective Migration and Performing Incremental Migration.

Flexible field mapping for Reverse sync

You can edit the source and target field types in field mappings for an object mapping with the Reverse sync direction. For Reverse sync, the system skips field type and rule name validation, so you can map fields with different data types or without a rule name. This is useful when the field types in your source system do not match the field types in the platform, such as when you migrate data from another system. When you change the sync direction from Reverse to ETL, the system revalidates the mappings against the effective target object. You can also disable mappings without validation. For more information, see Creating a Field Mapping.

Preventing Duplicate Records During Reverse Sync for Complex Transactions

Reverse sync supports transactions that trigger several updates to the same record at nearly the same time. The application processes these updates in the correct order and syncs each record to the target system once. As a result, you do not need to remove duplicate records manually or build custom workarounds.

Example: An Amendment, Buy, and Option (ABO) order includes an ABO operation, such as a change to an existing installed asset, and a new product sale. When you accept the quote, reverse sync creates one OrderLineItem record in the target system for each line item, with no duplicates.

Template metadata conversion from Conga Platform to Salesforce

When you synchronize template documents from Conga Platform to Salesforce, the system now converts the metadata embedded in each Word (.docx) file to match Salesforce. This metadata includes object and field API names. Because the two platforms use different API names, templates could stop working after a sync. The conversion prevents this problem.

This feature benefits organizations that use both Conga Platform and Salesforce in a hybrid CLM environment.

Note: Only .docx files are converted. Other file types sync without changes.