Minor Agiloft software releases happen continuously throughout the year, while major releases happen about twice per year. This page includes the full list of changes for each version, but if you prefer to focus on the highlights, check out What's New: Release 24.1 instead.

This page also includes minor releases that have happened since the release of version 24 and prior to the next major version.

Release 24

Agiloft Integration Hub powered by Workato

The new Agiloft Integration Hub makes it easy to connect your KB to over 200 enterprise integrations using Workato, an integration-enablement platform. With these connections, you can trigger purchase orders when contracts are signed, send contract data to your billing platform for invoicing, notify your team in Slack or Microsoft Teams when deals close, and much more.

The Integration Hub includes a Templates folder with recipes specific to Agiloft, and it offers a library of pre-built recipes for popular apps, which makes the process simpler, quicker, and more intuitive. You can also create your own recipes from scratch on the Recipes tab.

After you've set up some integrations in the Hub, you can quickly check their status using the Dashboard tab.

The Integration Hub is an add-on that requires additional licensing. When you've purchased the add-on and set it up, you can access it at Setup > Integration Hub. To learn more about how to set up and use the Integration Hub, see Integration Hub and Workato's own documentation here.

Connect KBs to Mulesoft with new Agiloft connector

Easily connect Agiloft with your software ecosystem using the Mulesoft platform, where you can now add the new Agiloft connector. When you're connected to Agiloft in Mulesoft, you can configure your connector to do any or all of the following:

• Pull data using Get, GetChoiceListId, Query, and Retrieve Attachment
• Add or update data using Create, Update, Delete, Attach, and Remove Attachment

To leverage this new connector, log in to Mulesoft and add the Agiloft connector through Exchange. From there, configure the KB you want to connect to.

If multiple users need to work with the connector on the Mulesoft platform, or if one user needs to connect to multiple KBs, configure a connector for each user-KB combination. Access to KB data is controlled by the permissions attached to the Agiloft credentials you use to configure the Agiloft connector in Mulesoft. 

For more information about connectors in Mulesoft, see Mulesoft's Introduction to Anypoint Connectors. For detailed guidance on adding the Agiloft connector and configuring it in Mulesoft, see Mulesoft's documentation about configuring connectors. The connector integrates with Agiloft using REST API calls with the JSON request/response format over an HTTPS connection.

Sync CPQ with the Salesforce managed package

If you use Configure, Price, Quote (CPQ) with Salesforce, you can now leverage that information when you sync to Agiloft by including linked product information in contracts, and keeping the product list up to date in both systems. The new CPQ sync is easy to set up with the existing Salesforce managed package.

With CPQ included in your Agiloft sync, contracts automatically include any linked products when they sync back to Agiloft. Your product lists also stay in sync, so users can create contracts in either system while pulling from the same list of products. If you want to use only one of these features, you can easily disable the other.

Whether you've already installed the Salesforce managed package or you're installing it for the first time, you can access this setting by logging in to Salesforce and using the App Launcher to search for and open Agiloft Configuration. At the bottom of the Field Mapping tab, select Include CPQ and click Upload Mapping. This automatically creates new SF Contract Product and SF Product tables in Agiloft, and creates or updates the necessary sync configurations to connect everything in both systems.

For more information about integrating with Salesforce, see Salesforce Integration.

New outbound webhook system

The new outbound webhook system was created for use with the Integration Hub, but can also be a useful alternative method for integrating your KB with other systems and apps. With webhooks, your Agiloft system can send out notifications when certain events happen, so that external systems can then request updated information from Agiloft. 

For example, you could notify an external system when a new Contract record is created, so that system can then request that contract data from Agiloft. This push-based model requires fewer API requests overall, tends to be simpler to build, and provides real-time updates. 

You can create, edit, and delete webhooks in the Setup > Integration > Webhooks Setup menu, which lists all webhooks in your system. You can also create webhooks in Agiloft using the new POST /ewws/webhooks API call. Webhooks can run when a record is created or edited, after any applicable rules have run.

For details about Agiloft webhooks, including how they work and how you can configure them, see Webhooks.

View and test REST API methods directly in your system

Explore convenient, interactive documentation of our REST API methods and responses now available using Swagger. The documentation is available directly in your KB, for the most up-to-date and KB-specific information, at Setup > System > View REST Documentation.

The documentation inside your KB showcases REST information using the fields and tables specific to your system. You can even call the API from the documentation to test it out. In addition, the values and parameters included in REST calls can now be formatted in JSON.

Easily share links to specific records

You can use the new Copy Link option to easily share a record with coworkers or vendors, or even send it to yourself for quick reference. Open the record you want to share, click the ellipses menu in the top left corner, and click Copy Link. This copies the URL to your clipboard so you can paste it into an email, instant message, notebook, and more.

These links are encrypted for security, and they respect user permissions, so you don't need to worry about them getting forwarded to a third party. If you click a link to a record in a KB you're already working in, the link opens right away so you can get right to work. Otherwise, you're prompted to log in, and then brought directly to view the record. If you need to make changes, simply click Edit.

You can even include a record link using the new deeplink() function, which is available in Formula Help on the Functions tab. For example, you might use it in an approval notification so that you can also include a link to the contract being approved.

Note that this feature requires you have a value set in the Hotlink Server Root URL global variable (Setup > System > Manage Global Variables). This global variable is also used for hotlinks in email templates, so if you use those, it's probably already configured.

Internal Comments in the Agiloft Word App

Collaborate on contracts with the rest of your team right in the Agiloft Word app using the new Comments section. These comments make it easy to communicate with your colleagues without leaving comments embedded in the actual Word document, so you can share the Word file with third parties without your comments included. Your comments are stored in your Agiloft KB, rather than the Word file itself.

To deploy this, go to Setup > Integrations > Word Add-in and click Upgrade. This automatically adds the necessary Comments field to your Contract table, and will also update your KB with any other new features of the Word app. If you want to see and post comments in your KB also, simply add the new field to your Contract layout.

For more details on installing and configuring the app, see Agiloft Contract Assistant for Word.

Additional updates for the Word app

Beyond the addition of the Comments tab, the Agiloft Contract Assistant for Microsoft Word has more improvements to offer.

• When working with document templates, you can use the app to insert linked variables that point to other tables.
  
• When editing a contract with duplicate tags, the tags are now interconnected, so when you update the tag in one location, the duplicates update as well.
• If you try to save a document where duplicate tags have conflicting information, the app shows a warning message.

Updated design of Quick Search filters, buttons, and settings

The new Quick Search pane continues to improve, now sporting minor but notable updates to filters, buttons, and settings.

• Filters now use different letter styling to clearly distinguish the field name, operator, and value. You can hover over a filter to see a full text description.
• Adding filters has changed from "+ Filter" to "+ Add filters," and the button is now placed above the added filters, so it doesn't move out of view.
  
• The advanced text options String, Context, Synonym, and Active Only are now hidden by default, so they don't take up space on the screen unless you expand the caret to access them. This section also now has a gear icon that contains all the advanced settings that you used to access by clicking "More Options." This concentrates all the advanced options into the same area, and hides them from users who don't want to use them. The options stay expanded once you expand them, even if you switch tables or close the Quick Search pane and reopen it.
  

Updates to the layout editor

The new layout editor has been improved in a few additional ways. You can now:

• Click on a grayed out field in the field list to jump directly to its position on the layout, so you no longer have to scroll through the whole form to locate a specific field
• Use Ctrl + click to select multiple cells, and then delete them all at once
• Drag fields onto a tab name to open that tab and access its layout

Turn on the new user interface more easily

Enabling the new user interface is now simpler, relying only on the setting you choose in the navigation menu. The Use New GUI setting has been removed from Setup > Look and Feel > Power User Interface. 

To enable the new interface for a set of users, go to Setup > Look and Feel > Navigation Menu Setup and edit their navigation menu. Then, you can set the Navigation Menu Location on the General tab to Top, which both relocates the navigation menu and enables the new user interface across the system.

For more information about the navigation menu, see Navigation Menu Setup.

Updated scheduling options added to Chart Collections

Chart Collections now offer the same improved frequency options on the Schedule tab as the other types of reports. These options are more intuitive, and they also offer more granular control when creating schedules. For example, you can now schedule a Chart Collection to be distributed every two weeks on Monday at 12:00.

New warning about unsaved changes in split view

To avoid unintentional lost work, you will now see a warning if you're editing a record in split view and you open a different record without clicking Save. For users who frequently work in split view and don't need the reminder, you can disable the warning.

If you turn the warning off, but later want to re-enable it, you can do so from User Menu > Preferences > General Preferences. The setting can also be changed globally from Setup > Look and Feel > General Preferences.

Bug Fixes

Previously, database-related timeouts and delays could occur when an external user changed their password directly after logging in for the first time. Now, these timeouts and delays do not occur.

Previously, entity sets containing nested linked actions could cause a sync to fail, and would display an "Error exporting: null" error message. Now, nested linked actions no longer cause the sync to fail.

Previously, in some situations, multi-choice fields that were conditionally visible would appear even when the visibility conditions were not met. For example, a multi-choice field that is conditionally visible only for Employment Agreements might appear on a Contract record for a Non-Disclosure Agreement, and might appear in the History tab as if they had been modified. Now, this issue is fixed.

The sync options to "Make the ability to edit this field conditional" and "Make this main table default Action Bar for" now work as intended. Previously, they were not applied to new teams or groups added during the sync.

Hotlinks are now generated properly for users with usernames containing umlauts.

Previously, failed External Syncs locked the record where the sync error occurred. Now, the record is properly released instead of remaining locked.

Previously, ignoring error messages in the Agiloft Contract Assistant for Word could allow you to bypass certain validation checks, such as Contract Start Date being after Contract End Date. Now, error messages prevent further action until they are addressed.

Previously, diff reports sometimes contained false positives for Actions. Now, these reports accurately reflect Actions.

This release features performance optimization for the following, which will now work faster in some situations:

• Editing and viewing records
• Teams
• In-memory storage

June 2022 Interim Release Notes

Note that these changes predate the maintenance release format, and were released ad hoc between June 2022 and the advent of maintenance releases in early 2023.

Updated hotlink encryption setting

To optimize security in your system, the Hotlink Authentication setting has been deprecated, and instead hotlinks will always require both login and password for non-SSO users. SSO users who click a hotlink are not asked for additional authentication. 

The login page has also been updated to include a link so that users can reset their password if needed. This way, if you have any users who previously didn't have their own login credentials, they will be able to use the link on the login page to reset and obtain their own credentials, without requiring intervention by administrators.

Note that you might have configured some groups in your system to disallow resetting passwords by email. By default, the admin group is configured this way. To review or change this setting, go to Setup > Access > Manage Groups, edit the group, and set the Allow Sending Password? option as desired.

This also disallows anonymous users from using hotlinks, as they cannot provide login credentials. If you must allow anonymous users to access your system with hotlinks, set the "Allow use of Anonymous User" setting to Yes on the General tab of Setup > System > Security.

For more information, see Hotlinks.

Improved permissions handling on History view

Field-level permissions are now taken into account when you view record history. When you view a History entry that includes changes to fields you don't have permission to view, those values are now hidden.

New KB Alias option to make renaming KBs easier

If you've considered changing the name of your KB, but avoided it because you have a lot of customizations, now is the time to reconsider. The new KB alias option in the admin console allows you to give your KB a new name, but specify its past name as an alias. This allows existing configurations to continue working, without needing to update the KB name everywhere it appears.

For example, REST calls you've set up will continue working after you change names, if you provide the old name as an alias.

If you need to change the KB name again in the future, you can add more aliases to the list.

Use the Link action to connect related records

This release restores the Link option, which is now available for action bars. The Link options historically appeared in the Actions drop-down menu on default action bars, and allowed users to link records as related. This feature has been brought back by popular demand.

Added indentation tools to HTML editor

The HTML editor now includes buttons to increase or decrease indentation.

Improved error logging for report emails

Improved error logging for scheduled reports sent by email.

Bug Fixes

The option to automatically run a custom search when users open a table is now compatible with the new UI. Previously, this option did not work for tables that were included in navigation menu groupings, which is an essential part of navigation menus in the new UI. Now, this issue has been fixed.

Numeric dashboard widgets are now compatible with lowercase table labels. Previously, changing a table label to lowercase could cause numeric widgets to be blank.

Fixed an issue that prevented backup when it ran without attachments.

Fixed an issue with Quick Search that did not yield the expected search results when using non-Latin characters.

Fixed an issue that prevented saving the setting for navigation menus to apply the menu to any new teams that are created.

Fixed an issue that, in rare cases, caused a workflow status to disappear.

Fixed an issue where dashboard permissions were not saved if all teams were removed.

Fixed an issue that prevented the Search option from appearing in an action bar.

Fixed an issue that caused EUI record form tabs to appear blank in some cases.

Fixed an issue where DocuSign requests appeared to originate with different accounts in a case where the user was associated with multiple DocuSign accounts, despite the specific requests originating from the same account.

Fixed an issue where the interaction of redlining and data conversion caused some email responses to not be captured by the inbound email account.

Fixed an issue where the workflow editor froze when editing a complex workflow and switching to another tab in the table wizard.

Fixed an issue with Fixer.io key application in currency conversion rules.

Fixed an issue where email windows rendered with overlap.

Fixed an issue that prevented Conversion actions from running under some circumstances.

Fixed an issue where views did not respect the setting to apply the view to any new teams that were created.

Fixed an issue with Variable Formula counting.

Fixed an issue that caused the Delete button to persist in the All Communications table, even for users who did not have permission to delete.

Fixed an issue that prevented synonym searching from including synonymous terms as expected.

Fixed an issue where document templates included an additional line when the template referred to a clause that was blank.

Fixed an issue that caused Conversion actions to run very slowly in some cases.

Fixed an issue in automatically tagging references in document templates, when the template contains multiple formula expressions in the same line.

Fixed an issue where Integration Hub connections did not properly handle subtable data.

Fixed an issue where unsuccessful login from a hotlink did not direct the user to the intended exit URL.

Fixed an issue where accessing the KB from Microsoft Teams was not included in the activity log.

Fixed an issue that displayed a technical, internal server name instead of the expected server name in the URL.

Fixed an issue where arrow keys did not work in plain text fields when using the latest version of certain browsers.

Fixed an issue where the linked field look-up search did not populate correctly when the parent linked field value contained a comma.

Fixed an issue where long file names occasionally did not present a link to view the file name in full. Now, this link always appears for file names that are too long to display in full.

Fixed an issue where backup file cleanup did not respect the window set for automatic deletion time. Now, backup files are only deleted according to the configured automatic deletion period.

Fixed an issue where the concatenation formula could unexpectedly add extra symbols in front of the generated text.

Fixed an issue that truncated very long Choice list values when displayed as radio buttons.

Fixed an issue with filtering dashboards that sometimes caused the detail view to not apply the selected filter to the data.

Fixed an issue where the system incorrectly required any URL in any HTML field to satisfy the Trusted Zones listed in the Security wizard.

Fixed an issue where fields created with an empty field label did not appear at all in the table setup wizard. Now, such fields appear in the wizard with a blank field label.

Fixed an issue where, in rare cases, syncing an entity set caused unintended changes to the record layout.

Fixed an issue that could cause OCR actions to fail, and upon failure, to report the wrong error message.

Fixed an issue that sometimes caused an error when trying to create a new table.

Fixed an issue that prevented creating more than 100 LDAP teams. Now, this limit has been removed.

Fixed an issue where creating a new user with a login that was previously used for another user prevented creation of the new user. Now, reusing logins is permitted as long as that login is not in active use by another account.

Fixed an issue that caused Out of Memory alerts to appear frequently under some circumstances.

Fixed an issue where the deprecated Hidden tab on the layout still caused an error stating that a field was duplicated on that tab and another tab.

Fixed an issue where excess white space appeared in the new layout editor.

Fixed an issue with Calculated Result fields when the initial calculation fields were still empty and the Calculated Result field was configured not to calculate until all fields were populated.

Fixed an issue where the user was not always shown the last selected dashboard upon login with that option selected.

Fixed an issue where the base image for action bars could be deleted, causing all action bars to disappear. Now, the base image is not removable through the image management interface, and it is also not removable by script.

Fixed an issue where password reset instructions could not be sent to email addresses that included the plus (+) symbol.

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

September 2023 Maintenance Release

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

Fixed an issue that forced time-based rules to stop if any error was encountered when updating records. Now, time-based rules include a setup option so that they can be configured to continue running if there is an error on a record update.

Fixed an issue with REST search calls that prevented returning results.