ROUND Function Supports Rounding Modes

The ROUND function now supports an optional roundingMode parameter, allowing you to specify how the function rounds midpoint values. Use 0 for ToEven rounding or 1 for AwayFromZero rounding. Existing ROUND(num) and ROUND(num, digits) formulas continue to work without changes and use ToEven rounding by default.

For more information, see Guidelines for Functions.

Mark All Notifications as Read

You can now use the Mark All as Read option in the notifications section to mark all unread notifications as read with a single action. The notification count updates immediately to reflect all unread notifications, including those not visible on the current page. This option is available only in the Modern UI.

For more information, see In-App Notifications.

Email Template Management Enhancements

Email template management now includes the following enhancements to improve administration and prevent accidental configuration changes:

• Clone Email TemplatesYou can now clone any out-of-the-box or custom email template. The cloned template is created as a new custom template, allowing you to customize it without modifying the original.
• Edit Custom Email Templates Across the OrganizationAdministrators can now edit custom email templates created by any user in the organization. Out-of-the-box (OOTB) email templates remain read-only and cannot be modified.
• Protection for Default Email TemplatesThe system prevents you from deleting an email template that is configured as the default for a communication flow. Before deleting the template, you must first assign a different default template.

For more information, see Email Templates.

Condition Required for Service Hook Rules

Service Hook now requires a condition when you create a rule to ensure that rules run only when the defined criteria are met. The system displays a validation message if a condition is missing or invalid. Existing rules remain unchanged.

ComplexCpqFilter Rule Transforms Boolean FieldValues in Criteria Fields

The ComplexCpqFilter Data Transformation rule in Data Sync now converts Boolean values in Criteria fields from string format ("true", "false") to native Boolean format (true, false) required by Conga Advantage Platform during ETL and Forward Sync operations. This prevents criteria validation errors caused by field type mismatches and eliminates the need for manual data correction on Platform.

Migration Warning for Current User as Execution User

The schedule list now displays a warning for any schedule that does not have an Execution User assigned. The Execution User determines the user identity and permissions used when a scheduled Data Sync job runs. Schedules without an assigned Execution User continue to run using the created-by user. Existing syncs are not blocked while you complete the update. Once you assign an Admin User or Integration User as the Execution User, the warning no longer appears and all future runs use the updated user. New schedules require an Execution User at the time of creation.

For more information, see Data Sync Schedule.

Execution User Visibility for Scheduled Data Sync Jobs

You can now specify an Execution User when creating or updating a Data Sync schedule. Data Sync runs under the identity configured as the Execution User, which appears in the schedule list and schedule detail panel. Additionally, the Time Zone column is no longer available on the schedule list page.

To help you track who ran each sync, the Run History listing page now includes a Triggered By column that shows the Execution User for each run. You can also find this information on the Run Info page for the corresponding schedule run. For previously created schedules, the Run History retains the created-by context that was active at the time of execution. If you update the Execution User after a schedule has already run, only future runs reflect the updated user.

For more information, see Data Sync Schedule and Data Sync Run History.

Data Sync: Centralized Field Value Transformations View and Asset Based Sync Update

The Field Mappings page now serves as a centralized summary view, displaying value transformation details and rules without requiring you to navigate to separate pages. The Value Transformations column shows a Create button when no transformations are configured for a field, and an Update button when transformations already exist, helping you quickly identify the transformation status for each field. Additionally, Asset Based Sync is no longer available for manual and scheduled sync operations.

For more information, see Creating a Field Mapping and Transforming Field Values.