---
title: "What's New: Release 32"
canonical: "https://help.agiloft.com/space/HELP/535855109/What's%20New%3A%20Release%2032"
format: markdown
---
The Agiloft release cadence is as follows:

- **Agiloft Core Platform:** Quarterly releases with new functionality, plus monthly maintenance releases.
- **Connected Services: **Monthly releases with new functionality, plus anytime maintenance releases.

This page includes the full list of changes for the listed version of the Agiloft Core Platform, including monthly maintenance releases, plus changes to Connected Services during the same period.

This page covers updates for **Release 32.** The previous version was [Release 31](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/120422430).

To jump to a section of this page: 

> Macro (toc)

# Agiloft Core Platform November 2025 Release

## Automate obligation extractions from a contract with the new Obligation Management feature

Agiloft is introducing a new way to automatically extract obligation information directly from a Contract record. This workflow uses the power of Screen Run actions, and can be run from the Obligations tab, which serves as an upgrade to the Tasks and Obligations tab. 

When you select a document and click Extract Obligations, the Obligation Data section is populated with metadata such as Topic, Review Status, and Pinpoint Citation, which includes the text of the obligation. This creates an easily accessible environment to see important information about the extracted obligations. In the Obligation Management section, you can also click Create Tasks to create review tasks based on the obligations found. 

This feature is available with the latest out-of-the-box template only, but a future release will provide deployment instructions for adding this feature to existing KBs.

For more information, visit [Obligation Management](https://agiloft-public.atlassian.net/wiki/spaces/SD/pages/237240328), [Obligations Table](https://agiloft-public.atlassian.net/wiki/spaces/SD/pages/570163248), and [Using Screens](https://agiloft-public.atlassian.net/wiki/spaces/DT/pages/43716770).

## Run Screens on Attachment records directly in Agiloft with Screen Run actions

Screen Run actions are used to run screens directly from a KB, seamlessly integrating the Screens AI experience with your new and existing Agiloft workflows, using behind-the-scenes automation or activated directly from an action button. This way, you can ensure any new contracts are vetted using a custom AI workflow that can be tailored directly to your business needs.

Create Screen Run actions in the Attachments table and select the screen you want to run:

- Choose from a list of screens that appears in the action modal window, at the time of configuring the action. The list includes all the screens available in your Screens workspace.
- Choose a text field in Agiloft that holds your screen ID. This offers you some flexibility if you want to easily swap out the selected screen by editing the contents of that field.
- Choose at runtime, where users can select a screen at the time when the action runs.

You can run up to 20 screens per action. For more information, see [Screen Run Actions](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/120553719).

![Untitled-20251107-190158.png](media://45d3242c-050a-4b49-80c6-b991a06727dc)

## Search Contracts using natural language in Agiloft

Searching your knowledgebase just got easier with AI-powered natural language search. You can save time by typing "Show me all contracts with renewal dates next month" or "Find NDAs over $50,000" directly into the search bar, without spending time constructing an advanced search for a one-off query.

For this initial introduction, there are several limitations: natural language search can only leverage the fields and content on the first page and common area of your Contract table; it excludes some data types, like related tables and attachments; and it is only available in English.

Natural language search is also available as a REST endpoint, [NLPSearch](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/119799848), for additional integration and automation potential. It returns the number of records found, and for each record, it returns a set of field values such as ID and basic info related to the natural language query.

## Ask AI is now supported for multiple Contract tables

Ask AI is no longer limited to only one Contract table. Now, if you have multiple Contract tables selected in the Agiloft Contract Concept Mapper for Microsoft Word and Google Docs, AskAI is supported and visible automatically for all the Contract tables listed, provided that all other requirements for Ask AI enablement are met. 

This allows organizations that use multiple contract tables to harness the power of AskAI in more ways than ever. 

For more information, visit [Ask AI](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/43718504).

## New Prompt Lab models

Prompt Lab now offers OpenAI models GPT-4.1 mini, which has improved intelligence and a much larger token context window, and GPT-5 mini, which offers improved intelligence and speed.

## Additional models available for use with GenAI

When creating a Generative AI action, you can now select OpenAI-5 mini and OpenAI-4.1 mini from the Model Provider field, in addition to the existing options.

![Untitled-20251107-190324.png](media://6cec4869-97d7-469a-8acf-9dce83a4f718)

## Improvements to the left common area

Left common areas now offer an arrow to easily collapse or expand the pane, and you can click and drag the border to adjust the pane's width. 

This release also removes the option to place the common area on the right side of the screen, as this option is not optimal for readability and is not recommended. If you were using the right common area, your layouts are automatically updated to the left common area, preserving your current field arrangement.

The top common area is still available, although the left common area is the current recommendation for utility and user experience. If you elect to move your common area to the left, we also recommend setting your fields to show the field label above the input, rather than showing them next to each other. This minimizes horizontal scrolling.

## Pared down Look & Feel editor

Making your KB look good shouldn't be difficult! The Look & Feel editor has shed some of its more granular settings, so that more of the options are sensibly inherited from related settings or are hard-coded according to modern design and usability guidelines. For example, where previously you could set separate font families for field labels and user inputs, now these all use the base font.

## Images now automatically sorted by date

When you access the image repository in your KB, the images are now automatically sorted with the newest uploads at the top of the list. You can still select other sorting options from the drop-down list.

![Untitled-20251107-190417.png](media://f22f9bfd-7dcb-475a-aa9f-c5c250214ab8)

## Updates to the unsaved changes warning

To support the recent updates to the record header, the unsaved changes warning now appears if you navigate away from a record without clicking Save. If you frequently do this on purpose, you can still disable this warning by opening the user menu and going to **Preferences > General Preferences**.

## Tables in global search results now listed alphabetically

For a more intuitive user experience, the list of tables is now organized alphabetically in both the global search drop-down menu and in the global search results page. Previously, the search results did not list tables alphabetically.

## Update or insert records with a single action in the Integration Hub

The Agiloft connector in the Integration Hub now includes an Upsert Record action. This action combines the capabilities of the Create and Update Record actions, allowing you to simplify your integrations by making a single call that either updates a matching record or creates a new record if a match isn't found.

## Enhanced security for OAuth 2.0 REST API integrations

In addition to the standard OAuth 2.0 Authorization Code grant, Agiloft now supports Authorization Code with Proof Key for Code Exchange (PKCE) for API applications. This enhancement offers improved security for both public and private applications by verifying that the authorization request and subsequent token exchange come from the same client, adding stronger protection against authorization code interception attacks.

To update your KB to add the new grant type, go to **Setup > Integration > OAuth2 Client Setup** and click Upgrade. If the Upgrade button isn't present, your KB was already updated. This makes Authorization Code with PKCE an available grant type when you create or edit an OAuth2 app in Agiloft. 

For information about integrating OAuth 2.0 API applications with Agiloft, see [Using OAuth2 to Access REST API](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/43716464). 

## API Update operations support custom ID fields

Previously, API update requests required you to supply the standard ID of the record to update. For integrations using a custom field for record identification in Agiloft, that meant you needed to make one API call to find the standard record ID and then another call to update the record. Now, API update operations support matching records by custom identifier. Just make sure the identifier you choose requires unique values.

Include the new searchSQL parameter to specify the name of the identifier field and the value to search for record matching. The ID parameter is still supported and is now optional for API update requests.

Parameter syntax: `searchSQL=<field_name>='<value>'`

Example: `searchSQL=ext_id='a0B2c345'`

The Swagger OpenAI REST documentation is updated to include the searchSQL parameter where applicable. To view the documentation for your KB, go to **Setup > System > View REST documentation**. 

## Automatic search update for DocuSign 2.1 compatibility

For more accurate tracking of attachments and contracts when integrating with DocuSign, the "R: Status has changed to Completed" saved search used in the "Edit: Convert to Attachments and set Contract to Signed when Status is Completed, API only" rule in the DocuSign Envelopes table is automatically updated in this release for compatibility with DocuSign API version 2.1. Because the API event model tracks envelope completion through events rather than status fields, the automatic update modifies the search to find envelopes where the last modification changed the latest event to completed, rather than changing the status.

If the upgrade successfully modifies the saved search in your KB, it is renamed to "R: Latest Event has changed to Completed." If you don't see this search in your DocuSign Envelopes table, your KB either didn't contain the original saved search or your copy of the search has been modified from its original version, and you need to review your configuration to see if you need to manually switch references to look at events instead of statuses.

## Accessibility improvements

This release includes several corrections and enhancements for accessibility, including consistent labeling for screen readers, keyboard focus and navigation, better contrast, and improved text readability.

## Updated Agiloft token length

As part of the other changes in this release, the length of the token sent by Agiloft to third-party systems has increased above 250 characters. You might need to update your configurations to accommodate this increase.

## Bug Fixes

Fixed the requirement to allow browser pop-ups. This is no longer required to use the application.

Fixed an issue in the Word app's Compare feature where the Library Clause sometimes failed to appear in the right pane for comparison.

Fixed multiple display issues for linked field sets.

Fixed an issue where the Generate Clauses from Document option in the Word app sometimes unexpectedly failed.

Fixed an issue that prevented Word Web users from signing in after uploading a manifest file to install the Word app.

Fixed an issue where the file format name of documents uploaded during a legacy import deviated from "Document_name.docx.clean.txt." to "Document_name-cleaned.txt", creating inconsistencies with previous projects. Now, file formats always follow the original format.

Fixed an issue where the file format name of documents that had OCR run on them during a legacy import deviated from "pages_above_50_29_ocr.pdf" to "pages_above_50_29.pdf_overlayed.pdf", creating inconsistencies with previous projects. Now, OCR file formats always follow the original format.

Fixed an issue where hyperlinks that were configured to leave the user logged in and redirect to the table view were sometimes improperly directing the user to log in again.

Fixed an issue where updating a record title and clicking Save did not update the title in the table view if you had it open in a second browser window. Now, the title updates as soon as you save the change.

Fixed an issue where an AI Project record's Publish button was sometimes not be visible, even with multiple documents in a status of Reviewed. Now, the button is visible, as expected.

Fixed an issue with EWRead where previously the call failed to return fields with NULL values, even if they met the designated criteria.

Fixed an issue where clauses in the Similar Contract Clauses section of the Agiloft Word app could be displayed as HTML markup instead of as plain text.

Fixed an issue with sync that prevented transferring the action button setting to hide the button in view-only mode.

Fixed an issue with Conversion actions where the Conversion tab did not properly store selections in the table view if you navigated between the table view's pages. Now, your selections are held even if you navigate between pages, as expected.

Fixed an issue with $startif functions in document templates that sometimes showed incorrect information in related tables based on the order of $startif conditions.

# Connected Services November 2025 Release

## Assign users dedicated roles in Screens

Screens users can now be assigned a user role, which controls their access and permissions in the workspace.

- Reviewers can create, run, duplicate, and download any screens in the workspace, but they can't edit or delete screens they didn't create.
- Editors have the same permissions as reviewers, but they can also validate, edit, and delete screens created by other users.
- Admins have the same permissions as editors, but they can also manage user roles, disable access to Community Screens, and take other administrative actions.

If you already have a Screens workspace, all existing Screens users are automatically assigned the Admin role, and have the ability to adjust other roles within their organization. 

For new integrated workspaces, the first user to enter the workspace will be assigned an Admin role, with subsequent users being assigned Reviewer. In standalone workspaces, admins can invite users with any assigned user role.

For more information about roles, visit [Setting Up Screens](https://agiloft-public.atlassian.net/wiki/spaces/DT/pages/43716698).

## Easily navigate your documents in Screens with the updated Document Tab view

The Document tab of Screens has been updated so that relevant information is more immediately available. Now, documents are listed in a repository style with auto-extracted metadata columns of File Name, Document Name, Document Type, Counterparty, and Date Added available upon navigation, along with a column for any Labels you may have added. This makes it easier to skim all the documents you've worked with, and to sort, filter, and select the document you're looking for.

![Untitled-20251107-190846.png](media://707dda4b-d1d6-48e0-9f88-ea518bb06cdf)

## Instruct Screens on how to handle failed standards with the new Redlining Configuration section

You can now optionally choose to configure multiple redlining settings in the Redlining Configuration section when creating or editing a standard. The section contains the following fields:

- In the Preferred Language field, you can optionally add example text regarding what information you would like to see in this specific type of clause.
- In the Redlining Approach field, choose whether you want Surgical or Heavy redlining based on what you provided in the Preferred Language field. Surgical redlines make small modifications to ensure compliance with the standard, while heavy redlines copy the preferred language as closely as possible.
- In the Default Comment field, you can enter comments that are automatically added to a contract document when standards fail. You can include the Default Comment exactly as written by choosing Verbatim, or have AI modify the comment for clarity by choosing AI Adapted.

## Insert clauses directly from the Clause Library into a Screens standard

Choose a clause directly from your Clause Library as the input for the Preferred Language field of a standard in Screens, making it easier for you to screen for deviations from your organization's preferred clause language.

To add a clause:

1. In the Standards section of a Screen, click Clause Library, located near the Preferred Language field.
2. Search for a clause with the search bar, or filter by Contract Type, Clause Type, or Position.
3. Select a clause and click Submit. Now, the clause appears in the Preferred Language field.

For more information, see [Building Screens](https://agiloft-public.atlassian.net/wiki/spaces/DT/pages/43719566).

## Improved Bulk Analysis workflow in Screens

Simply click New Analysis from the Bulk tab in Screens to open a new modal window dedicated entirely to the Bulk Analysis workflow. In this window, you can choose documents based on Label or Document Type, and then analyze the whole document set. When the analysis is complete, Screens provides a clearer summary of results, along with the number of documents, at the top of the Bulk tab. 

For more information, see [Using Screens](https://agiloft-public.atlassian.net/wiki/spaces/DT/pages/43716770).

## Upload folders of documents to Screens

Screens users can now upload a folder full of documents all at once instead of uploading documents one by one. The documents are listed the same way they would be if they were uploaded one at a time. When documents are uploading, a progress bar appears at the top of the page throughout Screens, and displays a green completion message when finished.

## Bug Fixes

Fixed an issue where running a screen in the Screens Word app could occasionally result in a perpetual loading screen.

Fixed an issue where selecting a new Risk Level for a Standard in Screens sometimes failed to save.

Fixed an issue where Screens failed during the document upload process.

Fixed an issue with Bulk Analysis in Screens where an incorrect document count could be displayed on analyses that filtered results by Document Type.

Fixed an issue that sometimes caused repeated errors when attempting to log in to Screens.

Fixed an issue in the Screens dashboard where the total document count did not always accurately reflect the total number of documents.

Fixed an issue where users could see irrelevant Document Type filter options when selecting documents during the Bulk Analysis upload process. 

# Connected Services December 2025 Release

## View search terms directly in the Documents tab URL

When users filter data or search on the Document tab of Screens, their selections are now reflected and visible in the URL. This allows users to precisely share links of curated information, as well as bookmark certain views. Additionally, when a user clicks Back after navigating away from the tab, it will return to the latest search/filter iteration, as opposed to resetting the Documents tab entirely.

## Additional content added to Workspace Activity dashboard

On the Workspace Activity page of Screens, users can now see two additional total fields: Documents Uploaded and Screen Runs. 

## AI Platform license availability extended

AI Platform licenses are now available for use in Canada and Australia, and can be used for processing documents with AI.

## View Screens user roles in Settings

Easily check your current assigned Screens role by opening your user profile and going to Settings.

## File name visible alongside document title in Screens

Building on the recent change to show a cleaned up, user-friendly version of a document's name, Screens now also shows the original file name to provide clarity in lists of multiple documents that may have similar titles. For example, if you upload multiple NDAs, they may all have the same title extracted. Including the File Name provides additional clarity.

## Bug Fixes

Fixed an issue where users with access to multiple KBs were always logged into the last KB they used when opening the Screens web app, instead of the KB that correlated to the Screens account. Now, users are logged in to the correct account, as expected.

Fixed an issue where apps with Agiloft integrations, such as Screens, could time out much sooner than the anticipated default 15 minute timeout period.

Fixed an issue where Legacy Import projects sometimes failed after the document analysis stalled in the Queued status for several minutes. Now, analysis is either updated correctly, or marked as failed immediately.

Fixed an issue that sometimes caused a blank blue screen when opening Ask AI chat history right after logging in. Now, there is no delay in accessing chat history.

# Agiloft Core Platform December 2025 Release

## Update to Outlook app search function

The search function in the Agiloft Outlook app has been updated to mirror the [Quick Search](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/43718348) experience available in a KB's table view, offering faster and more accurate results.

## Bug Fixes

Fixed an issue where the document field of an AI Project sometimes failed to display the uploaded document file despite being processed with a status of Ready to Annotate.

Fixed an issue with natural language search that sometimes incorrectly returned no results for common searches. Now, search results are completed, as expected.

Fixed an issue where running a Screen Run action on an attachment could result in an error stating that the required attachment was missing from the Attached File field, despite the file being present. Now, Screen Run actions detect attached files, as expected.

Fixed an issue that could occur that prevented users from saving or analyzing the new Attachment record when running a Document Analysis Action on a single document.

Fixed an issue where **Setup > Integrations > Agiloft Contract Concept Mapping **sometimes showed the Upgrade button after it was already clicked.

Fixed an issue where users who had selected Chat-GPT 5 Mini as their active model could fail to see any output in Prompt Lab.

Fixed an issue when configuring multiple SAML accounts where on saving a profile, the Profile ID used in the Single Sign-On URL did not match the initial ID when creating the profile.

Fixed an issue where Home did not consistently respect the setting to open the user's last viewed dashboard.

Fixed an issue where downloading an entity set's sync history (**Setup > Sync > Entity Set > select a set > History > Download**) showed a blank page instead of the history logs.

Fixed an issue where including table fields in emails did not work correctly for fields that were not also on the record layout.

Fixed an issue where Excel reports did not handle date and time values the same way as other reports. Now, the data handling is uniform across formats and date and time values match expectations.

Fixed an issue with dashboard hotlink widgets where widgets linked to a filter did not transfer that link when exported using entity set sync.

Fixed an issue that sometimes prevented opening the Linked Surveys tab of a Survey Question record.

Fixed an issue where deleting an existing value from a field did not trigger the Validation action requiring a value if you deleted the value and then ran an action button. Instead, it restored the value that had been deleted. Now, the deletion is stored properly and the missing value triggers the Validation action when attempting to run the action button's steps.

Fixed an intermittent issue where using Ask AI in a Company record sometimes yielded a file access error.

Fixed an issue that sometimes showed an error stating only five nested actions were allowed, when only two or three layers of nested actions were configured. Now, this error does not appear except in situations where there are five or more nested actions.

Fixed an issue that could cause an API endpoint in the REST API Documentation to continue pointing to the test environment, even when implemented in the production environment. Now, this issue is fixed.

Fixed an issue where Calculated Result fields showed different values in view mode versus edit mode when the value was calculated from linked fields and those linked values had been updated in the source table. Now, treatment of these values is consistent in both view and edit modes.

Fixed an issue where AM and PM tags appeared in comments for time values that were formatted in 24-hour time.

Fixed an issue where related tables with no records did not always appear in the record form, if the record's Common Area was placed on the left but had no fields added to it.

# Connected Services January 2026 Release

## Introducing an easier way to review bulk Screens results

In the new grid view of the Bulk tab in Screens, you can see the results of all the individual documents in a bulk analysis project in rows and columns, making it easier to compare outcomes across documents, scan for trends, and quickly find failures and anomalies. From the same interface, you can also click individual cells from the grid to learn more.

You can switch between the grid view and the list view using the toggle in the top right corner of the tab.

![image](media://62eccb42-2c2a-4bea-b665-7f8176f84f39)

## Easy access to filters in Screens

Easily access filtering capabilities in any Screens tab by clicking the new filter button to the right of the Search bar. After you apply a filter, that filter is listed below for easy reference.

This release also adds a new option to filter based on Document Type, in addition to the existing Labels filter. The example below shows a search for License Agreements that have been tagged with the demo label.

![image](media://baa42e2e-1adb-4cd9-aef3-3ce8ca83dd45)

## Screens tabs updated to a new table-style UI

The Home and Results tabs have been updated to match the new table-style interface in the Document and Bulk tabs. This table view provides users with a more intuitive and comprehensive way to view their information, and also limits the amount of scrolling required. For example, the Screens home tab now shows a row for each screen that includes information such as the number of standards and questions that Screen contains, and the type of Labels added to the screen.

![image](media://43d395fa-eb21-4fcb-9337-c74b55411716)

## Bug Fixes

Fixed an issue that could cause Bulk exports of documents in Screens to fail. Now, documents can be exported as expected.

Fixed an issue where users who hold an Admin role could receive an error message when trying to change the roles of other users. Now, Admins can change roles as expected.

Fixed an issue where Screens users could occasionally be routed to the incorrect workspace.

Fixed an issue where some Agiloft and Screens integrated users could experience frequent timeouts, despite making adjustments to the default timeout interval.

Fixed an issue where some Force Majeure-related labels were sometimes extracted and listed as both clauses and key terms, instead of one or the other. Now, Force Majeure-related labels are listed properly in the appropriate category, as expected.

Fixed a few issues related to the recent Screens data view update:

- Document Type filters could fail to apply
- Applied filters could fail to display the corresponding tags
- Incorrect filter options could fail to display in Bulk History
- The default sort order indicator could fail to display properly

# Agiloft Core Platform January 2026 Release

## Bug Fixes

Fixed an issue where the X of the open record did not work consistently after quick editing the fields in a related table inside the record.

Fixed an issue that sometimes prevented the upgrade installer from creating a KB backup.

Fixed an issue that prevented deploying AI if English was not the selected interface language.

Fixed an issue where reviewing a group's table access (Setup > Access > Manage Groups > Tables tab) sometimes showed a group as having access when it did not.

Fixed an issue where printing from the document viewer sometimes resulted in a blurry printout compared to the digital version.

Fixed an issue that, in rare cases, caused a persistent lock after a minor field configuration change. Now, this process takes an appropriate period of time and does not result in a long-standing lock.

Fixed an issue where opening a document from the insight popover and then clicking Analyze Contract resulted in an error.

# Agiloft Core Platform February 2026 Release

## Bug Fixes

Fixed an issue where editing the question in a Survey Question record opened a blank modal.

Fixed an issue that sometimes prevented comments from loading if the record was opened in a new window.

Fixed an issue that occasionally caused Update actions nested in Action Buttons to show an error when run.

# Agiloft Core Platform March 2026 Release

## Bug Fixes

Fixed an issue that sometimes prevented GRAPH inbound emails from being processed properly.

Fixed an issue where occasionally, scripts were unintentionally included when exporting a KB. Scripts are now consistently excluded from the full KB export.

Fixed an issue that sometimes prevented showing the Test Output when testing a new Prompt Lab design.

# Agiloft Core Platform April 2026 Release

## Bug Fixes

Fixed an issue that sometimes caused long wait times to edit attachments stored in SharePoint.

Fixed an issue in embedded tables where using Quick Edit on one field sometimes unexpectedly cleared the value of another. Now, only the edited field is changed, as expected.

Fixed an issue where clicking Export on a record multiple times sometimes resulted in the same fields being listed multiple times on the Options tab. Unless you cleared the duplicate selections, the final export included duplicate values. Now, this issue is fixed.

Fixed an issue where, after running a search with context on a specific table, the global search on the End User Interface always searched with context, even if the option was not selected.

Fixed an issue that sometimes caused documents in an AI Project to stall in the Processing or Flagged status, even after re-running the documents.