Conga Advantage Platform Feb '26 Release Notes
In these release notes, you can find new features and fixed and known issues for the Conga Advantage Platform Feb '26 release. For documentation updates, see What's New in Conga Advantage Platform Documentation.
This documentation may describe optional features 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 features and licensing.
To access the learning path, including overviews and demonstrations of this release’s updated features, visit the Conga Learning Center.
New Features
The following features are new to Conga Advantage Platform in this release.
Property-Based Access Control (PBAC)
Administrators can now control access to records using Property-Based Access Control (PBAC). This enhancement lets administrators define permissions based on business properties, such as classification, region, or contract group, directly within permission groups. PBAC works with existing role-based permissions to provide fine-grained, record-level access without creating additional roles. For example, a regional property manager can now be configured to access only properties within their assigned region (e.g., "North America") and specific contract types (e.g., "Lease") without creating separate roles for each regional team.
For more information, see Property-Based Access Control.
Integration Hub
Integration Hub provides a centralized interface to manage and monitor third-party integrations directly from the Conga Advantage Platform UI. It brings supported integrations such as Salesforce, Microsoft Dynamics 365, HubSpot, and SAP Ariba into a single, secure location, removing the need for separate integration tools.
You can view integration status, configure connections, monitor health metrics, and start or stop pre-configured recipes using embedded Workato screens. In this release, Integration Hub supports managing existing integrations only. Creating new recipes is not supported. For more information, see Integration Hub.
Task Management
You can now create and manage ad hoc tasks directly in the Conga Advantage Platform using the new Task Management feature. A centralized Tasks page lets you create tasks, assign owners, set priorities, and track progress from one place. You can also use views, search, and filters to organize tasks and take action quickly from task details.
For more information, see Task Management.
Migration Hub
Migration Hub provides a centralized way to migrate data, schema, configurations, and customizations between organizations. It helps you move changes safely across environments while maintaining consistency and reducing manual effort.
- Full Migration: Use Full Migration to copy all supported data, schema, configurations, and customizations from a source organization to a target organization in a single operation. This option is recommended for setting up new or empty organizations.
- Selective Migration: Use Selective Migration to migrate only specific components, such as schema, configuration, extensibility, or filtered data. The system automatically manages dependencies, giving you more control when promoting incremental or targeted changes.
For more information, see Migration Manager.
Attachment Management with Object-Level Permissions
Document Management APIs now support secure, access-controlled file attachments on Conga Advantage Platform records, allowing users with appropriate object-level permissions to upload, view, download, and delete common document and image types. Uploading attachments requires edit permission on the record, viewing and downloading require read permission, and deleting attachments requires delete permission, ensuring attachment access is always aligned with existing object and record-level security.
Search Settings Performance Optimization
Search is now enabled by default for a set of predefined out-of-the-box (OOTB) objects, delivering faster and more reliable results. In addition to these default objects, you can enable Search for up to 20 custom objects that best fit your workflows. If you need Search enabled for more than 20 custom objects, contact your support representative for assistance. For more information, see Search Settings.
Workflows Enhancements and Reliability Improvements
The following enhancements are introduced in workflows.
- Intellisense Criteria Builder Support: The Record Trigger activity in Standalone, Staged, anf Before Save workflows now supports the Intellisense Criteria Builder. The builder supports grouped and nested conditions, validates criteria, and does not affect existing workflows. When you edit criteria in the Record Trigger activity of an existing workflow, the activity editor provides a Switch to new Criteria Builder toggle in the top-right corner to switch to the IntelliSense Criteria Builder. For more information on using the new Criteria Builder and migrating existing criteria to it, see Workflow Creation and Record Trigger.
- ISCHANGED Operator Removed: Removed the ISCHANGED operator from Before Save, Callback, and Lifecycle Workflows because it only works after a record is saved and is not reliable in these workflow types. This update applies to both the classic and IntelliSense criteria builders and ensures more accurate workflow logic.
- Row-wise Variable Value Resolution: The Assignment workflow activity can now evaluate variable values separately for each row in a loop. You can use formulas that refer to the current row’s data, and the variables will get updated automatically while the workflow runs. This makes it easier to handle workflows that need different values for each record. For more information, see Assignment activity topic.
- Nested Loop Support: You can now configure a nested loop (a loop inside another loop) in the Loop Activity. Each loop runs independently, avoids infinite execution, and delivers accurate results. You can design workflows that handle multiple levels of records, such as contracts with clauses or quotes with line items, with greater reliability.
- Path Parameters Support: Added the Route Param section to the Execute Custom API workflow activity. This section allows you to define path parameters using Name and Value fields. You can now dynamically pass values for placeholders in API routes, such as record attributes or variables, instead of using static URLs. For more information, see Execute Custom API topic.
- ISCHANGED Operator for Boolean Fields: Added the ISCHANGED operator for boolean fields in both the Criteria Builder and the Intellisense Criteria Builder. This feature lets you create workflow rules that trigger when a boolean value changes during a record update. Your existing rules still work as expected.
- Mandatory Criteria Field for Record Fetch and Update Select Type: The Properties-level Criteria field is now mandatory when you select “Fetch records that meet the condition, loop through them, and update the fields” as the Select Type. This update does not affect Entry Criteria or any existing workflows. Your current workflows continue to work as before, and you can edit them at any time to add criteria under Properties when needed.
- OOTB Workflow Modification Restrictions: Out-of-the-box (OOTB) workflows now run in a protected mode. The system prevents adding, editing, or deleting activities and restricts changes to workflow variables and formulas. The workflow canvas disables all options to modify activities, variables, and formulas, ensuring workflow integrity.
Translation Support for Reporting and Dashboards
Reports and dashboards now support localization, allowing users to view datasets, queries, dashboards, and interface elements in their preferred language. The system automatically adjusts labels, filters, visual elements, and layouts based on the selected locale, while keeping the underlying data consistent across all languages.
For more information, see Reports and Dashboards and Translation Management.
Scheduler API Improvements
The Scheduler module now includes the following improvements to give you more control:
- Hourly Frequency Support for Scheduling Custom Code: You can now schedule custom code jobs to run once per hour using the existing
POST /api/extensibility/v1/servicehooks/rulesAPI. This new hourly option adds to the existing daily, weekly, monthly, and yearly intervals, giving you more flexibility to automate and manage your jobs. - Cron Expression Support: You can now use the CronExpression parameter in the
POST /api/scheduler/v1/jobs/cronAPI to schedule jobs using custom cron expressions. You can choose to use either the CronExpression model or the existing Frequency model, but not both at the same time. This enhancement gives you more flexibility and precision in defining job schedules. For more information, see Create a New Cron Scheduled Job API. - Time Zone Support for Cron-Based Jobs: You can now set a time zone for cron-based jobs using the Timezone parameter. The job runs based on the selected time zone, while jobs without a specified time zone will continue to use UTC by default.Note: The Timezone parameter applies only to jobs scheduled using the CronExpression parameter.
- Increased Job Name Limit: You can now define job names up to 64 characters in the Scheduler API, compared to the previous limit of 26. This gives you more flexibility to use descriptive job names, making it easier to organize and identify your scheduled tasks.
Workflow Enhancements for Assignments and Reviews
You can now assign workflow activities to Users, User groups, or Team roles, configure activity-level notes, and trigger email notifications when actions are required. These capabilities are available for approval, review, e-signature, and document generation activities during contract execution. To support this functionality, the following new workflow activities are introduced:
- CLM Send for Review: Blocks workflow execution until assigned reviewers complete their review.
- Interactive Decision: Pauses the workflow until an assigned user selects an explicit outcome, which determines the next step.
- CLM Implicit Interactive: Pauses the workflow and waits for a user action, supporting assignments, notes, and controlled execution.
In addition, a new Assignee section is added to existing Approval, E-Signature, and Document Generation activities. This section includes separate Assignee and Notes fields, allowing you to configure these settings.
Bulk Runtime API for UOM and Frequency Conversions
You can now retrieve multiple unit of measure (UOM) and frequency conversion rates in a single request using the new bulk runtime APIs:
- POST
/api/conversion-management/v1/query/uom-conversion-rates/bulk - POST
/api/conversion-management/v1/query/frequency-conversion-rates/bulk
In addition, the following APIs are available to retrieve the converted values for a specific frequency or UOM:
- POST
/api/conversion-management/v1/query/frequency-conversion - POST
/api/conversion-management/v1/query/uom-conversion
Custom Code Update
You can now dynamically include HTTP headers when making outbound requests using the HttpHelper method. This allows you to pass multiple header key-value pairs as needed. Existing implementations continue to work without any changes. For more information, see HttpHelper.
Data Integration and Synchronization Reliability Enhancements
Introduced improvements to data integration and synchronization to enhance compatibility, reliability, and overall data handling.
- Improved Source System ConnectorThe platform now integrates with an upgraded version of the source system connector. This update ensures full compatibility with your existing object mappings, field mappings, and queries, allowing you to transition smoothly to the latest source system standards. All new tenants automatically use the new connector.
- Data Synchronization ImprovementsImplemented industry-recommended configurations to strengthen data synchronization. These updates improve reliability, reduce synchronization errors, and better handle missing or incomplete data.
Email-Based Login for Conga IdP Users
Conga IdP users now log in with their email address instead of a username. This change simplifies access, enhances account security, and offers a more consistent user experience across the platform. Users can also register multiple accounts in the same organization using email aliases (username), enabling role-based or project-specific access without conflicts.
The login method is changed from username-based authentication to email-based authentication on November 2, 2025. Please note that your username and old password will not work, you must reset your password first to use the email-based login authentication.
For more information, see Conga IdP Users – Login and Account Considerations, Conga IdP Users – Email-Based Login Update FAQs, Adding a User, and Logging into the Conga Advantage Platform using the Conga IdP.
Telemetry Logs Improvements
These improvements to the Telemetry Logs experience make it easier for administrators to analyze system activity, troubleshoot issues, and work with log data more efficiently.
- 30-Day Log Retention: The application now retains and displays telemetry logs for up to 30 days, with a maximum range of 7 days per request. This enhancement gives administrators access to historical data for troubleshooting, auditing, and analysis, supporting more effective investigations and operational insights.
- Filter by Service Name: A new Service Name filter is available in the Filter panel, allowing you to quickly locate log records related to a specific service. This improves search accuracy and simplifies log review.
- Product Field Picklist: The Product field in the Filter pop-up now shows a picklist of available products, eliminating the need to manually type the exact product name. This enhancement improves filtering accuracy and makes selection easier and faster.
- Custom Date and Time Range Filter: You can now filter log records using a custom date and time range, giving you precise control when reviewing activity and helping you quickly narrow results to the exact timeframe you want to analyze.
For more information, see Telemetry Logs.
DOC ID: RLPFEB26.20260209
