Page tree

What's New: Release 25.2

Agiloft provides quarterly releases with new functionality, plus monthly maintenance releases consisting of corrections only. This page now includes the full list of changes for each version, and the 25.2 Release Notes page has been rolled into this one.

This page covers updates for Release 25.2.

The latest release is documented in the What's New. You can find the latest  Agiloft downloadable installer at, or contact Support to request an upgrade if your knowledgebase is hosted in the cloud.

Previous ReleaseThis ReleaseNext Release
Release 25.1Release 25.2Release 26

New Features and Enhancements

Use generative AI to streamline contract negotiation, review, and redlining

When you review a contract, you often find a few clauses you'd like to modify. With Agiloft's new generative AI capabilities, you can easily align contract clauses with your standard Clause Library equivalent, or leverage AI to directly revise the clause based on your instructions.

  • Align Clauses: Improve third-party clauses in your contract draft by using Align Clauses to bring them in line with approved, vetted clauses from your Clause Library. For example, this can take a non-standard Force Majeure clause and adjust it to match the Force Majeure clause in your Clause Library.
  • Revise with AI: You can give AI direct suggestions about how to revise a clause through text prompts. This is especially useful if you don't have a Clause Library, or if your library doesn't have a comparable clause. For example, you could prompt the system to change your Limited Liability clause to a Mutual Limited Liability clause.

In both cases, Agiloft uses AI to generate a suggested new draft for the clause, which you can then tweak as needed and insert into the contract. You can run these workflows in the Agiloft Contract Assistant for Word once you have created a contract and stored it in Agiloft.

For more information, visit Generative AI.

Make contract relationships obvious at a glance with tree view

Make your contract relationships easy to see with the new tree view option. This collects child records underneath each parent, and makes it easy to expand or collapse different branches of your record's family tree. This is especially useful if you already use a diagram field to see this information, since the tree view helps to make that relational data visible directly in the table grid.

We recommend using this option when showing related records inside a record form, provided you have already established hierarchical relationships between your records. For example, you might update your Contracts table so that the Related Contracts section shows the relationships between the records. When shown in an embedded table, tree view also shows a breadcrumb trail to aid in navigation, especially for records that have many relations.

In addition, tree view includes a numeral next to each parent record that shows the number of direct descendants, and when you search or filter on a table that is using tree view, the parents of a search result are included in lighter opacity. That way, you can see which record matched your search without losing the contextual information you get from the family tree.

To configure your own Contract table this way:

  1. Go to Setup Contracts and open the Layout tab. In the layout, select the tab that contains information about related contracts. In the example above, the tab is named Renewal / Related Contracts. Note the name of the field that shows the related contract records.
  2. Next to the Layout tab, open the Fields tab and edit the field you noted in step 1. In newer KBs, this is an Embedded Search Result field named All Related Contracts.
  3. On the Permissions tab, find the Additional Filters section and edit the current saved search.
  4. If it includes a condition that ID does not equal $, click the trash can icon to delete it. This condition hides the current record from the table, and when using the tree view option, it is more intuitive to include the current record. In the example above, this step is the reason that Raynor-Collins Amendment 1 to Statement of Work 1 is included in the tree.
  5. Go to the Options tab for the saved search and under "When the search is run," select "Change the view" and choose an appropriate view from the drop-down. Note the name of the view you selected. If you don't have a view configured for viewing related contract records, you can create one in the next step instead, and then return to these steps to select it.
  6. Click Finish to save the search and then click Finish again to save your changes to the field.
  7. Go to the Contracts table, go to Views > Manage, and edit the view you selected in step 5. If you need to create a view, select Views > New and create one for this purpose.
  8. Select the Show Tree View checkbox.
  9. Select the field that stores the ID of the record's parent and establishes the parent-child relationship. For example, Parent Contract ID.
  10. Select the field that should show the plus and minus icons, and nest to indicate hierarchical relationships. In the example above, this is configured as Contract Title, so the title is where the icons appear and where the text is indented.
  11. Choose how many records you want to show at a single level. If there are more records at a single level than the number you choose here, the list includes a Load More button at the end of the list. This setting can impact performance if your hierarchies include many records on each level.
  12. Make any other updates to the view as needed and then click Finish.
  13. Open a contract that has linked family members and test the changes you made, so you can make any necessary adjustments.

Browse attachments, approvals, and more directly in table view

Browse attached files, approvals, and more directly from the table view, without needing to open the contract at all. With the new insight popover, you can configure related tables, some linked fields, and embedded search results to allow users to quickly browse the field's entire contents directly in the table view. For example, see all of a contract's attachments without opening the contract at all.

The insight popover is also a powerful tool when used inside another related table, such as giving the user easy access to a contract's attachments inside the Related Contracts section.

To take advantage of this feature, simply edit the field you want to use, configure the insight popover display, and add that field to a view. For details, see the Insight Popover section of Configuring Views.

Introducing the Agiloft Google Docs App

Agiloft is excited to offer a new Google-based contract assistant for Google Docs, which introduces workflows in Google Docs similar to the Agiloft Contract Assistant for Microsoft Word.

With the Agiloft Google Docs App, you can easily perform the following tasks, directly in Google Docs:

  • Tag clauses in a contract, and send them to your KB as records
  • Tag key terms in a contract, and send them to your KB as field values for Contract records
  • Edit existing tags, and instantly sync those changes to your KB

The Agiloft Google Docs app is available on the Google Store. To take advantage of the Google Docs app, you also need to set up the new Google Drive Integration.

For more information about using, installing, and configuring the app, visit Agiloft Google Docs App.

Automatically highlight required clauses missing from a contract

Improve your contract review workflows by configuring the Word app to highlight clause types that appear to be missing from a contract. With this feature, whenever a contract is opened in the Word app, the system checks the contract for clauses required by the Contract Type, and flags any absent Clause Types in the Missing Clause Types field. You can select a missing clause in the field to easily add it to your contract.

To set up this feature:

  1. Navigate to Setup > Integrations and click Configure under Agiloft Contract Concept Mapping.
  2. Scroll to the bottom of the General tab and edit a table.
  3. Under Missing Clause Types, select the field where the system will store any clause types that are flagged as potentially missing. In the default template, this is the Missing Clause Types field. If you don't have this field, you can create it by creating a linked field to the Clause Type field of the Clause Types table.
  4. Click Save twice.

In order for Missing Clause Types to populate in the field, you need to establish which Clause Types are required by each Contract Type. You can assign required Clause Types to a Contract Type by editing a Contract Type record and adding Clause Types to the Required Clause Type field, which is usually located on the General tab.

Word app manifest file improvements

Manage your organization's Word app installation with a new and improved manifest file source that:

  • Makes it easier to add or remove users from the O365 group, which helps with accessibility changes.
  • Eliminates the need for users to manually enter a URL and KB name.
  • Automatically keeps the Word app up to date.

To enjoy these benefits, download a new copy of your manifest file and select the appsource option on the Download Manifest tab of the Agiloft Contract Concept Mapping wizard. Then, follow the rest of these steps to publish the file to the O365 access group.

AI labels now automatically kept up to date

Keep your system up-to-date with the latest improvements and additions to your AI labels library. Now, your system automatically updates the AI label library on a nightly schedule, and any time you navigate to Setup > Integration and click Configure under AI. For a list of available labels, visit AI Platform Labels.

Evaluate model performance directly in the document viewer

If you have AI enabled, you can evaluate the performance of the models you are working on in an AI Label Training project by uploading a sample contract and clicking Generate AI Suggestions. This button appears in the top right corner of the document viewer in the AI Suggestions tab, but only appears in documents that are linked to an AI Label Training project, and only when the AI Suggestions tab is empty.

For more information, see AI Trainer.

Annotate contracts directly in the document viewer with AI

Easily access the Analyze Contract button directly in the document viewer, so you can quickly run an AI model and complete the annotation workflow for an AI Project, with fewer steps and screens.

In order for the Analyze Contract button to appear in the document viewer:

  1. Your KB must have AI enabled in Setup > Integrations > Agiloft Contract Concept Mapping, and the "Action Button field to use when requesting clause extraction" field must point to an action button that runs the Data Analysis action used for extraction. In the default template, this is Analyze Contract.
  2. The action must be configured to have a Processing Type value of Single Document.
  3. The action button must be configured to not run in background mode.
  4. The Attachment record that you open in the document viewer must be linked to a Contract record.

If all the above criteria are met, the Analyze Contract button appears on the top right corner of the document viewer. When you click this button, the AI model annotates your document and shows all the tagged labels in the right pane.

Open .docx files for editing directly from doc viewer

Jump directly from the doc viewer in Agiloft into Microsoft Word with the new Edit in Word button. This method is faster and more intuitive than downloading a copy of the file, editing it locally, and re-uploading it to the record.

The button appears only when the file field is configured to allow direct file editing. To turn on direct editing for a file field, edit the field and go to the Options tab, then set Enable Versioning? to Yes and Direct File Editing to "Allow direct editing of MS Office document and directly save back to the file field."

As part of this change, some other controls on the toolbar have been rearranged.

New API support for the Integration Hub

Expand your integrations with new API support for Integration Hub, which opens the door for even more flexible interconnectivity between Agiloft and the other systems you use. This offers several advantages:

  • Secure Traffic Forwarding: Create secure pathways, known as API proxies, for data to move from one place to another. This feature is not available on the base platform.
  • Data Sharing: Utilize API recipes, which expose certain functionalities as API endpoints so you can share data with partners or use it in other recipes. Without the API Platform, this process is more manual.
  • Access Control: Control who has access to your data endpoints on a more granular level than you can with the base platform.
  • Lifecycle Management: The API Platform supports the smooth transition of APIs from development to testing to production. Managing the lifecycle of APIs without the API Platform would require additional tools or manual processes.

The Integration Hub now also includes the API Platform tab, where a dashboard makes it easy to monitor your APIs and track their usage and performance.

For more information, visit Workato's documentation on the API Platform.

New Table field in Integration Hub to improve load times

When you edit a recipe in Integration Hub, the system automatically retrieves a comprehensive list of table metadata. For a larger KB, this process can be rather slow and may lead to errors. Now, you can enter a single table name, so that the Hub only retrieves the metadata for the specified table. This cuts down on load time as well as potential errors.

Use Quick Search to find multiple values

When you search on a field in the Quick Search pane, use the new "is contained in" and "is not contained in" operators to apply more sophisticated filtering to your searches. For example, you might use "is contained in" to find all contracts whose status is any of the selected options, instead of having to search for only one status at a time.

To select more than one value in a drop-down list, hold the Shift key as you click. For other field types, you can enter multiple search terms separated by a comma.

Improved DocuSign event tracking and separate Certificates of Completion

This release includes two improvements to your DocuSign integration:

  • The new Latest Event field tracks a more granular list of events, so you can see what last occurred with an envelope and its recipients and get additional context beyond the existing status fields. This field is available in both the DocuSign Envelopes and DocuSign Recipients tables. Simply add the field to your record layout or view to take advantage of this new feature.
  • Completed DocuSign envelopes can now include both a Certificate of Completion for the envelope and a separate final, signed copy of all the documents in one unified file. If you have configured your envelopes to save a combined file with both the signed documents and the Certificate of Completion in one, you will continue to receive combined files unless you change your settings. To review your settings, follow the steps in the Certificate of Completion section of DocuSign Account Settings.

To take advantage of these improvements, go to Setup > System > Manage Global Variables and locate the DocuSign API Version variable. Edit the variable, set it to "v2.1", and save it. Then, go to Setup > Integration > Configure DocuSign Extension, edit your DocuSign integration, and Disable and then Enable DocuSign Connect.

In addition to these changes, the configuration settings for DocuSign Users now offer only the JWT authentication method, now that the alternate authentication methods are no longer supported by DocuSign. For more information about setting up DocuSign authentication, see DocuSign Setup.

Machine to Machine (M2M) authentication for REST API

The Agiloft REST API now supports client credentials flow, which enables machine-to-machine (M2M) authentication. M2M is beneficial because it enhances security, centralizes API management, standardizes configurations, and eliminates the need for human intervention in the authentication process.

To create the Client Credentials API application:

  1. Go to Setup > Integration > OAuth2 Client Setup.
  2. Click New.
  3. Under Authorization Grant Type, select Client Credentials.
  4. Add a Name and a Display Name.
  5. Select a user under Associate this Application with the Contract ID field. This specific user's permission settings are used by the server when handling API calls. In most cases, it is useful to use a dedicated account for this purpose.
  6. Add the Redirect URI.
  7. Click Save or Apply Changes.

For more information about M2M use cases, visit the Microsoft documentation on client credentials flow.

Bug Fixes

Additional enhancements have been made to improve the security of your system.

Previously, when you opened a document from your KB from Google Drive, it opened in a new window. Now, if your browser is already open, the document opens in a new tab.

Fixed an issue with edit popovers where clicking Attach/Manage for a File with Versioning field in the popover opened the Attachments window behind the popover window, instead of opening in front of it.

Fixed an issue where the Flag: Documents Added field did not change to Yes after files were added to a Label Training project, which prevented the Add Documents embedded table from becoming visible. Now, the field changes to Yes and the embedded table becomes visible by default, as expected.

Fixed an issue where PDFs that had undergone OCR sometimes did not show the actual text of the document.

Fixed an issue where labels tagged in the document viewer sometimes showed incorrect Clause Types or Key Term Types. Now, these labels have the proper data types assigned to them.

Fixed an issue where clicking tags in the document viewer could cause the scroll bar to disappear.

Fixed an issue where clicking Previous or Next in the document viewer could cause the user interface to show options generally available for a different Project Type, such as showing the Label Training interface during a Legacy Import project.

Fixed an issue where Teams notifications could be sent twice, with the second notification coming in an undesignated format. Now, notifications are only sent once in the designated format, as expected.

Fixed an issue that prevented the simultaneous use of split view and Clear Filters when running a search. Now, you can use both in unison.

Fixed an issue that did not allow the keyboard arrow keys to scroll in a record form.

Fixed an issue that sometimes prevented the creation of Adobe Sign agreements.

Fixed an issue that caused tables to look different when the record was open for viewing instead of editing. Now, the width and alignment is consistent.

Fixed an issue with the workflow editor that could cause an existing status to disappear when a new one was added, if the new one caused the existing status to be repositioned on top of another status. Now, this issue does not occur.

Fixed an issue that sometimes prevented creating new tables.

Fixed an issue with Summary layout popovers that prevented action buttons from running.

Fixed an issue with If-Then-Else actions that hid the control buttons when scrolling down on a long list of conditions. Now, the control buttons remain visible when scrolling.

Fixed an issue that did not consistently apply the option to "Include newly created teams" when updating a navigation menu configuration. Now, if this option is chosen for a navigation menu configuration, that navigation menu is consistently applied to newly created teams, as expected.

Fixed an issue that caused performance issues when a Communications table search attempted to compare the "Call From" or "Call To" fields to an email address. Now, if a KB contains such a search, the erroneous filters are ignored.

Fixed an issue where, when using an edit pop-over in the table view, clicking the look-up icon for a field would open the look-up window behind the pop-over. Now, the look-up window opens in front.

Fixed an issue that hid the option to edit Notification actions. Now, the Edit button appears as expected.

Fixed an issue where if you tagged over 50 labels in a contract document, only the first 50 annotations were visible in the pane of the Contract Assistant. Now, you can view all the annotations.

Fixed an issue that sometimes prevented creating new transitions on the Workflow tab of the table wizard.

Fixed an issue that could cause conditionally visible fields to appear in view-only mode, even if the conditions were not met.

Fixed an issue that sometimes prevented exporting an entity set if the set contained certain dependency relationships.

Fixed an issue that caused calculated results to reset to 0 under certain circumstances.

Fixed an issue with inbound emails that stored incorrectly in Agiloft and were not readable.

Fixed an issue with table widgets that always displayed the default action bar for the user's team, rather than the action bar configured for the widget.

Fixed an issue with Integration Hub webhooks that prevented webhooks from being deleted after a recipe was stopped. Now, webhooks are deleted when their recipes stop, as expected.

Fixed an issue when mass editing fields where using the look-up did not populate the selected value in the selection field. Now, the look-up works as expected in this situation.

Fixed an issue where saved search conditions incorrectly resolved field variables that did not include a table name. Previously, a field variable like $id was evaluated based on the context of the search, so if the search ran from a specific record, that record's ID was used. Now, the variable is evaluated for each row being considered, to make the behavior consistent across the system. In situations where you need to compare to the ID of a specific record in this way, simply add the table name as a prefix, such as $ When the prefix is added, the value of the variable is found and then used to evaluate the search condition, rather than continuing to evaluate the variable.

March 2024 Maintenance Release

Additional enhancements have been made to improve the security of your system.

Fixed an issue that caused AI extraction of contract data to run slowly. Now, extraction can run up to eight times faster.

Fixed an issue with the Word app that prevented processing annotations that included dates in year-first format, such as 2024-2-16 for February 16, 2024.

Fixed an issue with action buttons that contained multiple If-Then-Else actions, which included a Validation action. Previously, this caused other actions in the action button not to work as expected. Now, this issue is fixed.

Fixed an issue where automatically forwarding discarded emails sometimes removed the discarded email's header information.

Fixed an issue that caused AI Model Field records to be removed under some circumstances.

Fixed an issue with formulas that contained concat() and int() that caused the formula to return a decimal instead of an integer.

Fixed an issue with anchors added to hyperlinks in emails and email templates. Now, these anchors work as expected.

Fixed an issue with the Microsoft Dynamics integration setup that enforced all required Dynamics fields, even if those fields were not intended to be part of the integration. Now, if a required Dynamics field is not selected for mapping, this error does not occur.

Fixed an issue that prevented CSS stylesheets from being applied properly. Note that CSS may require updating your KB's trusted domains (Setup > System > Security).

Fixed an issue that caused some document templates to show table contents without rendering a table. Now, tables are shown as expected.

Fixed an issue that occurred when comparing two KBs that contained fields of different data types that used the same logical name. Now, the system is able to complete the comparison in this situation.

Fixed an issue that prevented the document viewer from displaying correctly on the mobile interface.

Fixed multiple issues preventing the proper display of tree view.

Fixed an issue that prevented searching a very large number of record IDs in the global search bar.

Fixed an issue with Coupa integration where instances of """ in the Coupa Content field caused errors. Now, this phrase is parsed correctly, as it was before.

Fixed an issue where end users were directed to the legacy EUI after resetting their passwords, instead of being directed to the defined login URL.

Fixed an issue where the app sometimes failed to identify labels tags, such as from a document template or using the Generate Tags button to perform an AI extraction. Now, all labels are tagged.

Fixed an issue that caused approvals to be generated twice under some circumstances.

Fixed an issue that sometimes prevented customized action bar text from appearing in the table view.

Fixed an issue that caused the system to run very slowly when many Calculated Result fields were updated at the same time. Now, these calculations are throttled to manage the impact on system performance.

Fixed an issue where especially long text from generated clauses could become layered beneath interactive parts of the user interface, like buttons. Now, clauses are confined to a specific space, and especially long ones can be navigated with a scroll bar.

Fixed an issue where the Back button in the Word app didn't work consistently.

Fixed an issue where messages sent in Microsoft Teams sometimes failed to send due to an error with the Oauth token.

Fixed an issue where annotations might fail to load in the document viewer or Word, but still appear in Agiloft, sometimes with unnecessary content such as numbering. Now, annotations load as expected, and are recorded properly.

Fixed an issue where annotations on the Annotations or AI Suggestions tab were not always expandable after clicking Generate AI Suggestions. Now, all annotations are expandable.

Fixed an issue that prevented the Link button from appearing when linking Contract Types in a document template.

Fixed an issue where AI failed to tag part of a label if the label contained non-letter symbols at the end of a line.

Fixed an issue where documents uploaded for use in an AI Project could become stuck in a Processing status. Now, documents consistently advance from this status to succeed or fail.

April 2024 Maintenance Release

Additional enhancements have been made to improve the security of your system.

Fixed several issues with tree view, including:

  • Trees not expanding to show the results of a search; now, each tree expands to the first search result
  • Tree not consistently preserving the expanded branches when returning to the tree or clearing search filters
  • Tree not loading correctly when manually sorting an embedded table
  • No warning shown when selecting a tree view relationship field that contains looped data

As part of these fixes, there are two new options in the View wizard:

  • You can choose not to preserve the tree's full expanded state, which can have a performance impact if your data structure includes very large trees. In this case, the tree loads only part of the expanded branches when you return, and you can use Load Previous and Load More buttons to show more of the tree.
  • Control whether search results expand only the first tree with a match, or expand all trees in the table.

Fixed an issue that caused the new Quick Search to appear in the EUI even if the "showfastsearch" variable was set to false. Now, the new Quick Search can be hidden using the new "showquicksearch" variable in the same manner.

Fixed an issue that kept an insight popover in place when scrolling the table view. Now, the popover remains with its row when scrolling.

Fixed an issue where logging in through a single sign-on link prompted the user to log out of other sessions, even when concurrent sessions were enabled.

Fixed an issue with dynamic group assignment where, when assignment was automated and combined with SSO and Active Directory, assigned groups did not consistently save properly. Now, the group assignment works as expected.

Fixed an issue with the teamNonWorkingHours() function that resulted in incorrect calculations.

Fixed an issue with concurrent editing that caused files to open in Word instead of the document viewer.

Fixed an issue with numerical widgets that display a simple table variable or use the dateformat() function. Now, these widgets work as expected.

Fixed an issue that limited Salesforce sync to 200 records at a time.

Fixed an issue that prevented the Unlink option from appearing in action bars.

Fixed an issue where setting an action to open a URL defined in a record field sometimes added a ? symbol at the end of the field's stated URL.

Fixed an issue that caused the Insert Clause interface in the Word app to load slowly for large clause libraries. Now, the first 100 clauses are loaded initially to improve loading time, and from there you can apply filters or use the refresh icon to load more.

Fixed minor visual issues with Quick Edit.

Fixed an issue that sometimes prevented the X icon from appearing in the Quick Search bar of embedded tables.

Fixed an issue where import actions sometimes failed when importing non-alphanumerical characters, such as a backslash in a date format. Now, non-alphanumerical characters are processed as expected.

Fixed an issue where annotations seemed to disappear after an attachment was reopened in Word, if those annotations were tagged using the Analyze Contract button. Now, all annotations appear as expected.

Fixed an issue where redlined markup of tagged clauses sometimes failed to update the associated contract clause.

Fixed an issue where the "Change text to selection" button in a Word app annotation sometimes failed when used to update an existing annotation. Now, the button works as expected.

Fixed an issue where KBs with multiple contract tables didn't consistently show the Analyze Contract button or annotations pane in the document viewer. Now, these features are visible as expected.

May 2024 Maintenance Release

Fixed an issue that could cause some action buttons to not complete a selected Conversion action.

Fixed an issue where, in some circumstances, removing a record from a linked set caused the remaining linked records to disappear until the record was saved. Now, this issue is fixed.

Fixed an issue with Modal actions where certain configurations caused using the X button to freeze the parent record.

Fixed an issue in the look-up modal that prevented the navigation links to appear under some circumstances. Now, these links appear and function as expected.

June 2024 Maintenance Release

Track file views and check-outs in the activity log

Now, in addition to file downloads, you can use the activity log to track when files are viewed or checked out for editing. This offers a fuller picture of file interactions that might be cause for security concerns.

Partial list of events available for tracking, including View, Download, and Edit File

Bug Fixes

Fixed an issue where clicking the download icon in the document viewer opened the three dot menu at the same time.

Fixed an issue when the global variable "Always display visibility dependent field values in table views" was set to No where some field values did not appear in table views even if there was no visibility dependence configured. Now, this setting hides only the fields that are visibility dependent, as expected.