Organization-Level Currency Display Format

Administrator can now configure how currency values are displayed across the organization. In the Organization Details screen, the administrator can choose between Currency Code and Currency Symbol.

• Code (default): Selecting this option displays the three-letter currency code with the amount, such as USD 100.00 or EUR 150.00, wherever currency values are displayed.
• Symbol: Selecting this option displays the currency symbol with the amount, such as $100.00 or €150.00, wherever currency values are displayed.

The selected format applies across the organization and cannot be overridden by individual users. For more information, see Organization Management.

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.

Workflow and Custom Code Enhancements

The following enhancements improve workflow configuration and reliability, expand custom code capabilities, and optimize platform performance.

• 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.

• CancellationToken Support for Framework Class Extensions: You can now use a new, simpler cancellation syntax when writing custom code that extends Conga framework classes. This does not require passing a cancellation token explicitly. The platform now handles token retrieval automatically in these cases. For implementation details, see CancellationToken Implementation Guidelines.
  Note: This update applies only to custom code classes that extend specific Conga framework classes. All other custom code must continue using the existing approach.

• New Workflow Activity: Internal Webhook V2: Introduced Internal Webhook V2, an improved version of Internal Webhook, for configuring internal API calls. Internal Webhook V2 simplifies endpoint configuration, supports the use of activity outputs in downstream workflow activities, and provides access only to approved internal APIs. When creating new workflows, you can select only Internal Webhook V2 from the activity list. Existing workflows that use Internal Webhook V1 continue to work without any changes. For information, see Internal Webhook V2.

• Support for System.ComponentModel.Annotations Namespace in Custom Code: Added System.ComponentModel.Annotations to the list of supported .NET namespaces in the Custom Code Framework. You can now use built-in data validation and metadata attributes from this namespace in custom code. For more information, see .NET Class Library Usage.

• New Activity: Custom Error for Screen Workflows: The Workflow module now includes a Custom Error activity for Screen Flow workflows. Use this activity to display clear, custom error messages to users when a screen action triggers a workflow that encounters an error. Instead of showing a generic system error, you can configure a specific message using static text or dynamic values from variables and activity outputs. The message appears directly on the screen and tells users what went wrong. For more information, see Custom Error activity.
  Note: This activity supports error messaging only. Success and informational notification messages are planned for a future release.

• Service-Based Endpoint Filtering for HttpCalloutV2: You can now use the Service Name dropdown when configuring an HttpCalloutV2 activity. The Service Name field helps you quickly identify and select the appropriate endpoint configuration by grouping endpoint connections by service. When you select a service, the system displays its associated endpoint configurations. Workflow execution remains unchanged. For more information, see HTTP Callout V2.

• Workflow Display Name Enhancements: Use Display Name as the primary way to identify, search, and manage workflows. The application now requires a Display Name when you create or edit a workflow and automatically generates the system-managed Name field during workflow creation. Additional improvements include:
  • Search workflows using Display Name.
  • Use flexible, user-friendly Display Names with support for spaces and up to 80 characters.
  • Automatically populate missing Display Names for existing workflows.
  • View recently modified workflows at the top of the workflow list with default sorting by Modified Date.
  • Return to the workflow list after saving or publishing a workflow and quickly access the updated workflow at the top while preserving any applied filters and search criteria.

  For more information, see Workflow Management

• Resource Dropdown Supports Record IDs for String and LongString Fields: You can now select and map record Id values directly to String and LongString fields from the Intellisense Resource Dropdown when configuring workflow activities. For example, in the Update Record activity, you can map a record Id to a field such as Description without creating a formula to convert the Id value to a string.

• Self-Loop Validation for Workflow Import and Publish: The application now prevents workflows that contain self-loop connections during import and publish operations. A self-loop occurs when an activity connects back to itself, which can cause infinite execution loops at runtime. If a self-loop is detected during import or publish, the operation is blocked and an error message identifies the affected activity. You must resolve the self-loop before you can proceed.

• 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.

• Custom Code Analyzer Rules: The Conga Advantage Platform enforces a set of code quality and security rules and validates Custom Code at compile time. When you import Custom Code, the platform checks for violations across blocked types, static usage, reflection, and cancellation token patterns. If it detects any violations, it blocks the import and returns an error message with the file name, line number, and details about the violation. For more information, see Custom Code Analyzer Rules.

• Logging Optimization: The Advantage Platform now handles internal log messages more efficiently when processing operations through the custom code module. If a log message exceeds the allowed size limit, the platform automatically captures a preview for immediate diagnostics and retains the full message as information level in application logs, ensuring no diagnostic data is lost. For more information, see Telemetry Helper.

• Deployment Time for Custom Code: The Conga Advantage Platform caches CustomCode assemblies in memory to improve execution performance. After you deploy updated CustomCode, the changes become available for execution within 2 minutes, the time the platform needs to clear the existing in-memory assembly and load the new one. During this window, the platform continues running the previously deployed version. For more details, see Custom Code Project Deployment and Importing Custom Code to Conga Advantage Platform.

• Accessing and Returning HTTP Headers in Custom Code Extensions: Custom Code Extensions now support reading inbound HTTP request headers and setting outbound headers in the HTTP response. This enables header-driven business logic and end-to-end correlation for custom APIs. You can access only headers that are present in the original request. A comprehensive list of blocked headers and prefixes applies to both inbound and outbound traffic. Existing custom APIs remain fully backward compatible with this update. For more information, see HTTP Header Access Reference for Custom Code Extensions.

• Granular Logging Control for Custom Code Execution: Administrators can now configure log levels for specific custom code projects, classes, or methods without changing logging settings for an entire application area. This enhancement enables targeted troubleshooting by increasing logging detail only where needed, which reduces unnecessary log noise and helps developers identify issues more efficiently. Administrators can also view and manage configured log-level settings through dedicated APIs. For more information, see Configuring Log-Level Overrides for Custom Code.

  Note: This feature is available on request. Contact your Conga Support Representative to enable it for your environment.
• Cursor-Based Pagination Support in DataHelper: DataHelper now supports cursor-based (keyset) pagination for retrieving large datasets more efficiently and reliably. Using the new .After(cursor) query builder method, developers can pass an opaque cursor token to continue retrieving records from where the previous page left off. This approach maintains a consistent record order and prevents skipped or duplicate records when data changes during pagination. Query responses now include two new properties:
  • NextCursor: The token to use for retrieving the next page of results.
  • HasMoreRecords: Indicates whether additional records are available.
  Existing offset-based pagination (Skip/Limit) continues to work without any changes, so it doesn't affect your existing code. For more information, see DataHelper Cursor-Based Pagination Reference.

• Standalone Workflow Instance Persistence Optimization: The platform saves execution details for Standalone workflows only when they fail. If a Standalone workflow completes successfully, the platform does not save its execution details. All other workflow types continue to work as before, with execution details saved for both successful and failed runs. For more information, see Standalone Workflow Instance Persistence.

Contact Scope for External Users

Administrators can now use Contact Scope in Permission Groups to control record-level access for external users based on their relationship with a Supplier or Account primary object. This capability automatically limits users to records associated with their related Supplier or Account, making it easier to provide controlled access to external users without manually configuring access for each user or organization. For more information, see Adding Contact Scope and Use Case.

External User Management and Access Control Enhancements

Administrators can now manage external users, such as partners, vendors, and contact users, with dedicated authentication and access controls. External users can sign in through a dedicated login option using a one-time password (OTP) sent to their registered email address. Administrators can create and manage roles, permission groups, and object permissions, and map them to define the type of access they support.

Data Manager Enhancements

This release includes the following Data Manager enhancements:

Task Management Enhancements

This release introduces collaboration and governance enhancements for Conga Tasks, including user mention support, object-level task creation restrictions, and direct navigation to related records:

• Restrict Task Creation to Allowed Objects: Task creation and work item linking are now restricted to permitted objects only. When configured, users can only create tasks or link work items to the allowed objects, and the work item dropdown displays only those permitted objects. To manage or update the list of allowed objects, contact your Conga Support Representative.

• User Mentions in Task Management: You can now mention multiple users while managing a task. Mentioned users receive both in-app and email notifications when referenced in a comment. Hovering over a user mention displays a clickable pop-over with the mentioned user's details, including their name and email address. Clicking a link in a comment opens the linked content in a new browser tab.

• Navigate to Related Records from Task Details: You can now navigate directly from a task detail page to the associated record, such as a contract, product, or agreement. Selecting the linked record opens its detail page in a new browser tab, making it easier to access related information and continue your work without manually searching for the record.

For more information, see Task Management.

Migration Support for InternalEndpointConfiguration object

Migration Manager now supports migration of the InternalEndpointConfiguration object as part of workflow migration. When you migrate a workflow, the system automatically includes the associated internal endpoint configuration metadata and preserves their references in the InternalEndpointConfiguration object in the target organization. For more information, see Migration Manager.

Data Sync Enhancements

The following enhancements simplify Salesforce authentication, improve visibility into sync errors, and add a new option for handling missing data during migration.

• 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.

• Platform Token URL Now Managed Automatically: The Data Sync Platform settings no longer show the Platform Token URL field. The system now manages the token authority URL securely, preventing unauthorized changes and improving overall security. This update requires no user action and does not affect existing data sync operations.

• Improved Visibility of Template Sync Errors in Run History: Data Sync Run History now displays detailed error messages when template sync operations fail. Administrators can view clear reasons for failures, such as missing template versions or invalid field mappings, directly in Run History.

• Transformation Rule to Handle Null and Empty Source Values: A new transformation rule, ApplySchemaDefaultTransformationFilter, is now available for field mappings in Data Sync. When configured on a field mapping, the rule automatically applies the destination field's schema-configured default value whenever the incoming source value is null, empty, or whitespace. For more information, see Apply Schema Default When Source Value is Null or Empty.

• 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 Manager Enhancements

This release expands Migration Manager with broader artifact coverage and granular control, enabling administrators to migrate precisely what they need across environments:

• Migration Support for View Settings and View Setting Mapping: Migration Hub now supports migrating View Settings and View Setting Mapping configurations, making it easier to move customized layouts between environments.

  This enhancement supports the migration of Object Layout and Wizard Layout configurations from the Data tab. When you select the Workflows option, the system also automatically migrates related WorkflowScreenMetadata forms from the Extensibility tab. In addition, owner information is preserved by migrating the associated User object along with the View Settings configuration. For more information, see Selective Migration and Incremental Migration.

• 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.

• Dashboard Migration Support in Full Migration: Administrators can now migrate Dashboards as part of the full migration process. The system preserves dashboard configurations, including layouts, filters, visualizations, and permissions, when migrating dashboards from a source environment to a target environment. For more information, see Full Migration.

Data Sync Schedule Enhancements

The following enhancements let you track execution users for scheduled syncs, migrate away from legacy user handling, prevent duplicate or conflicting schedules, and maintain a complete audit trail of schedule changes.

• Execution User Visibility for Scheduled 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.

• 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.

• Schedule Validation to Prevent Duplicate and Conflicting Schedules: Data Sync now validates schedules before saving to reduce redundant sync operations and data conflicts. The system warns administrators when schedules have 40% to 59% object overlap and blocks schedules with 60% or greater overlap. Data Sync also blocks the creation or update of schedules that duplicate an active schedule with the same objects and frequency, and identifies the conflicting schedule in the error message.

• Schedule Change History in Audit and Access Dashboard: 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.

Data Sync Mapping and Validation Enhancements

The following enhancements add automatic field type detection, block incompatible mappings, streamline value transformation management, enable bulk mapping, and expand audit tracking for Data Sync field mappings.

• 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.

• Type Validation for Field Mapping Configuration: The field mapping configuration now validates source and target field types when you create or edit a mapping, helping ensure your mappings are complete and data syncs correctly:
  • Unsupported type combinations: If the source and target field types are not compatible, an inline error appears on the field mapping row, and the save is blocked until you select a compatible type combination. For more information, see Field Type Compatibility Between Salesforce and Platform.
  • Type mismatches requiring a transformation rule: The field mapping configuration now guides you to assign a Rule Name when the source and target field types require a transformation rule. When a type mismatch is detected, a warning appears inline on the field mapping row, and the save is blocked until you assign a Rule Name.
  This validation applies to both the Create mapping and Edit mapping flows.

• Centralized Value Transformation Management: You can now view and manage Value Transformations directly from the Field Mappings list and the Edit Field Mapping page, without navigating to separate pages:
  • On the Field Mappings list, 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.
  • The Rule Name column displays the transformation rule applied to each field, helping 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.
  • On the Edit Field Mapping page, an inline, expandable Value Transformations section lets you add, modify, view, and delete value transformation rules directly within the field mapping workflow. The section displays the assigned rule name and transformation status, and provides guidance for configuring transformations when needed.
  Additionally, you can now view the configured Source Filter Criteria in the Criteria column on the Mapped Objects for Data Sync page, and 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.

• Field Mapping Target Lookup Object Name Auto-Population and Validation: The Target Lookup Object Name field now auto-populates when you map fields with Lookup or Reference data types, removing the need for manual entry. The field is read-only and validates values during configuration to prevent missing or invalid selections.

• Pre-Sync Validation Results Now Available in the UI: Pre-Sync Validation results are now displayed directly on the Validation Report page instead of only being available as a downloaded JSON file. Administrators can review issues by category, see severity classifications, and follow suggested fixes, all from within the application. For more information, see Viewing the Pre-Sync Validation Report.

• Bulk Mapping with Inline Validation: The All Object Mappings screen is renamed to Bulk Mappings. Admins can now select multiple objects or fields simultaneously using checkboxes and save them in a single action, replacing the previous one-at-a-time workflow. Bulk Mappings also introduces the following enhancements:
  • Target Object Name and Target Field Name auto-populate. Admins can accept or override the suggested values.
  • Inline validation flags type mismatches and invalid lookup targets during configuration, before saving.
  • Confirmation dialogs appear for both save and delete actions. Delete confirmations state that only the mapping is removed and the underlying schema object or field is not affected.
  • Formula fields no longer appear in the mapping list.
  For more information, see Bulk Mappings.

• Audit and Access Report: Mapping Configuration Changes Now Tracked: The Audit and Access Report now tracks Data Sync mapping configuration changes, including object mappings, field mappings, and value transformations, in addition to its existing coverage of user activity, data changes, and system configuration changes. Each audit record captures the user, timestamp, action performed, and the old and new values. For more information, see Audit and Access Report.

Template-Based Migration

Administrators can now save migration configurations as reusable templates for Selective Migration and Incremental Migration. Templates retain the selected components, filters, preferences, and other migration settings, allowing you to reuse the same configuration for recurring migrations. This functionality helps standardize migration processes, reduce manual configuration, and ensure consistent migration results. For more information, see Template-Based Migration.

Modern UI: Sidebar Navigation Redesign

The sidebar navigation is redesigned to make it easier to find and access application features. Frequently used features are now available directly from the sidebar. Related features are organized into categories with grouped links, providing a more structured navigation experience. The sidebar displays only the features available to you based on your permissions, licenses, and enabled features.