Conga Product Documentation

Welcome to the new doc site. Some of your old bookmarks will no longer work. Please use the search bar to find your desired topic.

Show Page Sections

Conga Advantage Platform 202607.1.0 Release Notes

In these release notes, you can find enhancements and fixed and known issues for the Conga Advantage Platform 202607.1.0 release. For documentation updates, see What's New in Conga Advantage Platform Documentation.

Note:

This documentation may describe optional enhancements for which you have not purchased a license; therefore your solution or implementation may differ from what is described here. Contact your customer success manager (CSM) or account executive (AE) to discuss your specific enhancements and licensing.

Enhancements

The following enhancements are new to Conga Advantage Platform in this release.

Staged Workflow: Prevent Deletion of the Default Record Trigger

The system now restricts deletion of the default Record Trigger activity (DataChangeWorkflowTrigger) in staged workflows but continues to support editing.

Migration Hub: Granular migration for dashboards, CX layouts, and custom code

Administrators can now selectively migrate individual or multiple Dashboards, CX layouts, and Custom Code between environments. From the Extensibility tab, you can expand and browse available components and migrate only the items you need.

The migration process includes dependency checks, conflict resolution options for existing dashboards and layouts, and validation of Custom Code resources before migration. A review page summarizes your selections before execution.

For more information, see Performing Selective Migration.

Audit and Access Dashboard – Data Sync Schedule Change History

The Data Change History panel in the Audit and Access Dashboard now tracks Data Sync schedule configuration changes. Administrators can view a complete audit trail of schedule updates, including the user who made the change, the date and time, the modified field, and its previous and new values. The system tracks changes to schedule frequency, interval, start time, Run As identity, and enable/disable status, along with schedule creation and deletion events. No user, including administrators, can edit or delete audit entries. The panel displays data for the last three months. For more information, see Audit and Access Report.

Value Transformations Now Accessible Directly from the Field Mappings List

You can now view and manage Value Transformations directly from the Field Mappings list. Key enhancements include:

  • The Value Transformations column displays an Update link for each field mapping. This provides direct access to configure transformations without using the context menu.
  • The Rule Name column displays the transformation rule applied to each field. This helps you quickly confirm configurations across all mappings.
  • An information banner appears at the top of the Field Mappings page, prompting you to review and update field transformations.

Additionally, you can now view the configured Source Filter Criteria in the Criteria column on the Mapped Objects for Data Sync page. For more information, see Transforming Field Values.

Data Sync: Blocking Incompatible Field Type Combinations at Configuration

The field mapping configuration now validates source and target field types when you create or edit a mapping. If the combination is unsupported, an inline error appears and the save is blocked until you select a compatible type combination. For more information, see Field Type Compatibility Between Salesforce and Platform.

Data Sync: Field Types Are Now Read-Only in Field Mapping Configuration

When you create or edit a field mapping, the source and target field types are now automatically fetched from the system metadata and displayed as read-only. You no longer need to enter them manually. The displayed type updates automatically when you select a different source or target field. This applies to both the Create mapping and Edit mapping flows.

Data Sync: Salesforce Settings Uses OAuth-Based Authentication

You no longer need to provide Salesforce user credentials when configuring Data Sync. Instead, Data Sync uses the Salesforce External Client App with the OAuth 2.0 Client Credentials Flow to authenticate securely. To support this authentication method, the Salesforce Settings page displays only the fields required to configure the connection: Token URL, Client ID, Client Secret, Domain URL, and Salesforce API Version. For more information, see Configuring the Salesforce Settings.

Fixed Issues

The following issues are fixed in this release. If any actions are required, they will be listed in this table.

Case Number Conga Internal ID Description
00972940 PLATFORM-25295

In Migration Manager, fields with the isPropertyLookup schema metadata property remain marked as Modified after a successful selective migration because the property is not updated in the target organization.

- PLATFORM-25271

Exporting a LineItem Schema configuration as a migration package fails with an internal server error.

00975591 PLATFORM-25260

When a misconfigured workflow triggers repeatedly and overloads the system, reverse sync stops responding. The platform now limits the number of times a workflow runs on the same record within a short period, ensuring reverse sync continues to work as expected.

IE-1417 PLATFORM-25072

Previously, deleting a user group did not validate whether the group was still assigned to users. This could result in orphaned group assignments and inconsistent user group data affecting permissions and access.

Resolution:

The platform now validates existing user assignments before allowing a user group to be deleted. If the group is still assigned to users, deletion is prevented, ensuring group assignment data remains consistent.

NA EUF-7537

Accessing the Opportunity link from the Account's Related Records redirects to an invalid URL, resulting in an error page.

- EUF-7446

CX Studio UI visibility rules do not apply to out-of-the-box action buttons, such as Submit for Approval, when the rules use formula field criteria. As a result, the button remains visible regardless of the formula field value.

Known Issues

There are no known issues in this release.

DOC ID: RLP202607.1.0RN20260727