This page covers updates for Release 2628.

The latest release is documented in the What's New. You can find the latest 

New Features and Enhancements

Look and feel refresh with new Core Theme

The new Core Theme offers a fresh take on the default look and feel scheme, with better visual contrast, enhanced readability, and modern details like rounded corners and font adjustments. New Agiloft KBs are equipped with this scheme automatically. 

Image Removed

After importing the new Core Theme to an existing KB, we recommend assigning yourself to a new group and applying the theme only to that group, so you can test how it looks and make adjustments as needed.

Elevate workflows with powerful generative AI

Take advantage of new features using generative AI.

Introducing ConvoAI Document Q&A

Get information about your contracts and reduce the burden on your legal team with the new ConvoAI feature, Document Q&A. This feature aims to save you time by making it quicker and easier to parse complicated contracts.

Document Q&A allows you to ask questions about your contract directly from Agiloft in the document viewer and receive answers with information about the contract, even quoting exact text from the contract body where applicable.

...

This section details new enhancements to your system.

Improvements to AI features

This release includes several improvements to AI features.

Introducing two new Generative AI workflows

AI Platform now offers two additional generative AI workflows, one called Data and Document Mismatch and another called Clause Analysis.

Data and Document Mismatch allows you to compare field data stored in Agiloft against the data contained in one of your contract documents, allowing you to extract any mismatched data to an output field in your KB for comparison.

Clause Analysis allows you to compare clauses extracted from your contracts, allowing you to identify non-standard clauses, as well as generate standard and fallback Clause Library positions.

For more information, visit Generative AI.

Doc Q&A answers now include links to relevant text

Easily explore or confirm answers from Ask AI with new in-line citations that appear when an answer references text in the contract document. These superscript links jump directly to the source text, and the answer includes an expandable reference section with more details about the cited parts of the document.

Image Added

Use AI features on longer documents

Apply AI workflows to more of your files with upgraded generative AI models that can process documents up to 300 pages long. Both GenAI Prompt Lab and ConvoAI Document Q&A have been upgraded to handle these larger files.

Additional AI model provider available for Prompt Lab

Generative AI actions now support Anthropic's Claude 3 Haiku (hosted in AWS) as another AI model provider option, offering you additional freedom to choose your preferred model when using AI Platform. You can now also connect to any of your own AWS bedrock models. 

Long text responses are now expandable in generative AI workflows

When using generative AI models in the Doc Q&A workflow, responses are truncated after 100 characters. To view the entire text, simply click Show More. To return to the truncated version, click Show Less.

Create more robust document template conditions in the Word app

Enjoy a more intuitive and user-friendly way to build conditions for your document template with new additions to the template editor in the Word app. These enhancements include:

• When creating a condition, linked fields included in the condition now show drop-down lists of applicable values, so you don't need to enter the value from memory. For example, if you select Contract Type as your If Variable, the Value field shows a drop-down list of your Contract Types. However, if you want to add a specific string to search on outside of the values available in the Contract Type linked set, you can still manually enter that custom value into the Value field.
• The new Add linked field button allows you to create linked chain variables in the app, so you can create conditions using fields that do not need to be part of the designated linked set. For example, if you want a condition to check for North American contracts, you can select Location ID as the If Variable, then click Add linked field to select the Region field. Now, the Value field populates with a drop-down list of the available options for Region, where you can select North America. Previously, creating linked chain variables was done exclusively by manual text input.
• The addition of the Add variable and Add a group buttons offer a faster and more efficient way to create complex conditions in the app, such as nesting multiple variables in groups with AND/OR combinations. Previously, creating complex conditions was done exclusively by manual text input. Now, you can add multiple variables to a condition or to a group all within the right pane of the app. When you've added groups to a condition, groups are visually denoted by their color scheme.
• Clauses and key terms that are included as part of conditions are indented underneath the condition in the Tags column of the right Word app pane.

For more information on the Template Editor, see Creating Document Templates.

Improved interface for conditional variables in the Word app

The Word app interface has been improved to more closely mimic human expectations when working with document templates in the Word app. Now, Key Term tags are not created for the variables that are used to form conditions. For example, now, if your template includes an expression like $startif($company_name=="Agiloft"), the app does not show a Key Term tag for $company_name because it is part of the condition. Previously, tags were shown for these variables, which made the list of tags more difficult to navigate.

Easily check your Word app version

Easily find your current version of the Word app at the bottom of the pane when in the main menu. The version information is useful for troubleshooting, and should be included when engaging Support.

Insight popover improvements

This release includes two improvements to insight popovers.

Improved sorting in insight popovers

Insight popovers now offer improved default sorting for your convenience. By default, insight popovers now sort their contents the same way the embedded table is sorted when you open the full record.

As before, you can click the drop-down and sort by any of the four fields configured in the Insight Popover section of the field wizard.

Image Added

Insight popovers now hidden when empty

To save you time, insight popovers that are empty are now shown with a disabled icon in the table view.

Image Added

Use the new Oracle integration to automate actions

Integrate your Agiloft KB with Oracle using the Oracle Integration Cloud. With Oracle, you can leverage additional automation in your KB, such as scheduling a new Contract record to be created in Agiloft with fields like Contract Title and Contract Type auto-populated.

To set up the integration, you must have an Oracle Integration Cloud account. For more information, see Oracle Integration.

Updates to e-signature

This release includes several updates to e-signature integrations.

Adobe Sign agreements now available exclusively through Adobe Sign

Due to changes to Adobe Sign’s Reseller Program, Adobe Sign agreements (or transactions) must now be purchased directly from Adobe. If you have agreements you already purchased through Agiloft, you can use them until November 30, 2024. After that point, any remaining agreements you purchased through Agiloft will be cancelled, and Agiloft will apply a credit to your account for their value.

Agreements that have already been sent for signature prior to the deadline will work normally, even after the deadline, to complete the signing process. 

If you have previously purchased agreements through Agiloft, you must create a new Adobe Direct account to begin purchasing agreements from Adobe, and then update your Adobe Sign integration to use the new account. For more information or assistance with this process, reach out to your Agiloft representative.

Use Adobe Sign groups to manage e-signature scopes

Agiloft's Adobe Sign integration now supports enabling scopes on a group basis rather than by account, if this configuration is needed for your organization. This is controlled in Adobe Sign, when configuring OAuth for the API application you set up.

For more information about setting up Adobe Sign, see Adobe Sign Setup. For more information about scopes in Adobe Sign, see Adobe Sign's documentation here.

New support for DocuSign ACG authentication

Agiloft now supports integrating with DocuSign with the Confidential Authorization Code Grant (ACG) authentication method, in addition to the JSON Web Token (JWT) authentication method currently supported.

ACG requires less maintenance by the Agiloft administrator, provided that your users all have their own DocuSign logins. However, this method does not allow automatically sending envelopes in the background with rules or automation, and it must be the only DocuSign account set up in Agiloft. For more information about ACG, including its advantages and disadvantages, see DocuSign's documentation here.

To set up DocuSign with ACG, see DocuSign Setup. If you currently use DocuSign with JWT, and you want to switch to ACG, simply remove the JWT account in the DocuSign Accounts table before you begin the setup.

Additional admin enhancements

This release includes continued enhancements to the admin experience.

Track data exports in the activity log

The activity log now offers the option to track when data is exported from your system. This offers a fuller picture of file interactions that might be cause for security concerns.

Image Added

Easily remove icons in table views

When editing the notification icons in a view, you can now easily remove an icon after it's been selected. Previously, you had to select an empty icon from the image list. To select a different icon, simply remove the current icon, and then select a new one.

Click to open admin screen drop-down menus

To provide a more consistent user experience, the admin wizard action bars now require a click to open drop-down menus, rather than opening on hover. For example, when creating a new field, you must click New to open the list of field data types. This better matches the behavior in the rest of the system

To use Document Q&A, open a contract in document viewer and click Ask AI at the top right of the document viewer. You can ask your questions in the pane, and ConvoAI will respond in a conversational manner with the requested information.

For more information, see ConvoAI Document Q&A.

Leverage generative AI in records with new action type

Generative AI actions are a new action type that allow you to configure generative capabilities that can be triggered by a rule or action button. These generative capabilities are referred to as templates.

To make a new Generative AI action:

1. Navigate to Setup [Table] and click Actions.
2. Click Generative AI Action.
3. Give the action a name and an optional description.
4. Select the template you want the action to generate.
5. Click Finish.

You can use pre-built templates provided by Agiloft or create your own. For example, you might create a template to generate a text description for a given contract document. To make your own templates:

1. Click New from the Templates tab of a Generative AI action.
2. Enter the name and description of the template.
3. Choose the Model Account you'd like to use.
4. Choose the AI Model Provider you'd like to use for generation.
5. Click Next.
6. In Prompt Input, write the natural language you'd like the model to use as a prompt for generating information about a given document.
   Image Removed
7. Under Test Output, click the lookup icon to choose a record you want to test the prompt on.
8. Click Generate. Under Output, you can see how well your prompt worked with the record you chose. If desired, tweak your prompt and test it again until you're happy with the outcome.
9. You can optionally add parameters and postprocessing settings by expanding the Parameters and Settings heading. 
10. Choose an Output Field. This determines which field in your KB will hold the text generated from the template.
11. Click Finish.

For more information, see Generative AI Action.

Continued improvements to existing AI features

In addition to generative AI tools, the current AI toolset continues to improve.

Quickly asses model performance with a downloadable .xlsx file

The new Review Annotations button, available from the AI Projects or Label Models tables, allows you to quickly check your model's performance in a given dataset, showing you real examples of what the model is recognizing and helping you identify areas that might require additional model training.

To generate an .xlsx file of a given AI Project's annotations, click the Review Attachments button.

Image Removed

The file contains the following columns:

• Document ID

• Document title

• Document status

• AI Project ID

• AI Project name

• Annotation

• Annotation label

Filter highlighted AI annotations and suggestions in the document viewer

Easily search through annotations and AI suggestions in the document viewer with a new filter system. By filtering your data, you can list and highlight specific labels throughout the entire document with ease.

Image Removed

To see the highlighted data in the contract body, you must select Show Highlights from the three-dot menu.

Publish to contract tables of your choice

If your system uses multiple contract tables, you can now choose which table will receive the published data from your AI model.

Now, when a Publish action is run from the foreground, you can select the contract table to publish to using the Contract drop-down list that appears in the Publish window. The values in this drop-down list are determined by the tables under the Table Configurations section in Setup > Integrations > Agiloft Contract Concept Mapping. For more information, see Publish Actions.

Image Removed

New groups for AI Project records

There are two new group types available for use in AI Project records.

• AI Project Owner: Users who have complete access to view and manage all AI Projects. Users can create and train new AI models, and determine the priority of model usage.

• AI Project Annotator: Users who have access to some AI Projects, both for Legacy Import and AI Training. Users will only have access to AI Projects where they are listed as an Annotator.

Updates to Integrations

These improvements enhance other integrations available for your system.

Improved contract search for Gmail app

The contract search function in the Agiloft Gmail app now considers additional fields, to better ensure all relevant contracts are returned with the search results.

Easily create Agiloft tables for syncing Salesforce CPQ data

Create Agiloft tables for your CPQ data with the click of a button, making it easy to plug your Salesforce CPQ data into Agiloft with Integration Hub. To create CPQ tables in Agiloft, simply go to Setup > Integration > Salesforce Extension, click Configure, and then click Deploy.

This automatically creates two new tables, SF Contract Product and SF Product, for easy mapping to Salesforce entities.

Note that if you use the Salesforce Managed Package integration, or if you already sync your Salesforce CPQ data with your Agiloft KB, you already have these tables and do not need to use this feature.

Additional Enhancements

These additional enhancements don't fit into a single category, but they offer exciting additions to your Agiloft KB.

Cleaner, smarter license management

Use your licenses more efficiently with a new option that automatically grants a license when a user logs in, but only if the user meets the criteria of a saved search. This new option is also available for floating licenses, which previously did not offer filtering. This gives you better control over how your licenses are used.

Image Removed

Beyond this new setting, your KB now applies more sophisticated logic to use your license resources wisely based on who accesses the system. To achieve this, your permission groups are now associated with a specific type of license, instead of with a general user type. When a user logs in to your system and doesn't already have an associated license, the system reviews the user's groups and the available licenses and grants the user the most appropriate license available based on their group memberships.

To make this transition as seamless as possible for you, Power User groups are automatically transitioned to Assigned/Floating licenses, and End User groups are automatically transitioned to Read/Request licenses. To adjust this setting, simply go to Setup > Access > Manage Groups, edit the group, and select a license type on the General tab. Note that the license type now also filters the available permission settings for the group, to make it clear which settings will function properly based on the limitations of the chosen license type.

Updates to the Google Docs app

The Google Docs app continues to grow, adding two new features this release.

Inserting Clauses

Now, when inserting clauses into a contract from the Google Docs app, you can filter clauses more efficiently using a modified search system. After clicking Insert Clause from the Google Docs app, you'll now see two search functions just like the Word app:

• Search Text: searches text against the Clause Text, Clause Title, and ID fields
• Clause Type: dropdown list of all available Clause Types

Both filters are applied when the Search button is clicked. If you want to search with only one of the options, simply leave the other blank.

Generating Tags with AI

Now, you can use AI to tag key terms and clauses within a Google Docs document, the same way you can with the Word app. 

Keep contract data up to date with new pushback actions

When a document comes back into the system after a round of negotiation, there are often changes in the text that aren't reflected in the associated Contract and Clause records in the KB. Now you can easily bring the document and the records back into synchronicity using two new action types, which can be added to action buttons or automation for your convenience.

For more information on these two actions, visit Pushback Actions.

Enhance your outgoing Agiloft emails with new style options

Take your outgoing emails to the next level with new support for custom CSS. With custom CSS, you can establish a base stylesheet template for all outgoing email. You can find these new options at Setup > Look and Feel > Email Schemes on the General tab. This update has also improved the formatting options for included fields, which can be found on the Tables tab.

Document viewer user settings now persist throughout the session

Enjoy a smoother document viewer experience where your preferred settings, such as the zoom level and whether you have Show Highlights enabled, now persist as you open and close documents throughout your session.

Updates to look-up window terminology

In the search window for look-up fields, the Import/Replace button has been renamed Replace, and Import/Append has been renamed Add. These terms are more user-friendly and offer a cleaner look for the window.

Note that if you have already customized these terms on your specific server, your customized terms are retained and you will not see this change.

Improvements to entity set sync

Entity set sync now includes a new Action Bar tab where you can choose which, if any, action bars to sync for a given table. Simply click Customize for any table you have added to the entity set.

Use scalable vector graphics in your KB

Avoid pixelated images or poor image resolution by uploading scalable vector graphics (.svg files) in your KB. For example, if you have a vector file for your company logo, you can now upload that to use in your Look and Feel so that it looks clean and sharp on every user's screen.

Bug Fixes

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 where expanding or collapsing a tree view node or an insight popover in split view also selected that row's record and opened it in the split view. Now, these actions do not open the record and instead simply display the additional context requested.

Fixed an issue where opening a record from a hotlink and clicking Cancel redirected the user to the exit URL instead of the cancel URL.

Fixed an issue where table view showed action buttons even if they were configured to appear only when editing the record. Now, the table view respects this setting.

Fixed an issue where Compound fields that were used to combine Choice field values did not properly reflect the selected language for translated choice lists. Now, the Compound field reflects the language that is used in the Choice field value for Choice fields that have translated lists.

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 when using saved searches to check the contents of an attached file for a value that included quotation marks. Previously, filtering on a value with quotation marks and then adding a new filter caused all previous filters to be removed. Now, the filter is added normally, as expected.

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

Fixed an issue where opening a record in View mode that was missing required fields, and then clicking an action button with validation checks, the validation checks for the required fields were bypassed by the button. Now, these checks are enforced.

Fixed an issue where fields set to mask encrypted data except for the first X characters were instead shown with the entire value masked. Now, the setting is respected.

Fixed an issue with entity set sync when a linked set was synced from a source KB where fewer fields were included in the set than there were in the target KB set. Previously, the target KB was updated to remove the excess fields. Now, the fuller set is kept in this situation.

Fixed an issue where selecting a record, clicking Export in the action bar, and then canceling the export did not close the export modal window as expected.

Fixed an issue where creating a new group and clicking Cancel would also delete the last group that was edited. Now, this does not occur.

Fixed an issue with insight popover that caused the popover field to be listed twice in the View wizard.

Fixed an issue that led to slow performance when opening very large documents in AI Projects. Now, the fuzzy search matching that caused this slowdown no longer runs on documents of more than 40 pages. The page limit is configurable with the new Fuzzy Search Page Count Threshold global variable.

Fixed an issue when rendering some alphabets in the document viewer.

Fixed an issue that prevented the Load Tags button from appearing when there were no tags present.

Fixed an issue that caused unused elements in a document template to appear as empty tags in the annotation pane. Now, these elements are ignored in the pane.

Fixed an issue where imported email templates did not consistently appear in the list of templates.

Fixed an issue where switching documents sometimes froze the document viewer when opened from an AI Project record.

Fixed an issue where some circumstances caused the record form to freeze when it was opened for editing. Now, the record works as expected.

Fixed an issue that prevented the Load Tags button from appearing when there were no tags present.

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.

an issue in the table view where going to the next page of records did not move you to the top of the page.

Fixed an issue where using Quick Edit on a text field near the bottom of the screen could overlap the bottom of the window, out of view. Now, the complete input box appears in the window, as expected.

Fixed an issue with email templates where links to edit the record were sometimes applied with trailing characters that broke the link. Now, these links are saved correctly.

Fixed an issue where importing values into a link to a single field with multiple values enabled sometimes imported only the first value, rather than all the values listed.

Fixed an issue that sometimes suppressed the warning message for validation actions, even though the validation action still worked correctly.

Fixed an issue that caused an error when opening a SharePoint attachment with the Word app enabled.

Fixed several issues that impeded DocuSign workflows in the mobile interface.

Fixed an issue when automatically sending emails to a link to multiple fields, where emails were not sent to all recipients if the link contained selections from both tables simultaneously.

Fixed an issue that sometimes prevented displaying the checkboxes in the Files to Send with Email section of the email editor.

Fixed an issue with conversions that sometimes did not properly transfer the contents of a link to selected fields with multiple values enabled.

Fixed an issue where syncing a field with Input Correction configured did not retain that setting.

Fixed an issue where edited comments were not indicated. Now, edited comments show "Edited" next to the time stamp.

Fixed an issue with Legacy Import AI Projects where manually tagged annotations in the document viewer sometimes failed to publish to your KB, even when the Manually Added Tags checkbox was selected in the document viewer. Now, data is sent to your KB as expected when the publish action runs.

Fixed an issue with Address extractions where AI sometimes failed to capture some kinds of information included in the address, such as the Company name. Now, all relevant information is included.

Fixed an issue where sometimes clicking a tagged annotation from the right pane of the document viewer could fail to highlight the corresponding text in the text body of the contract. Now, the relevant text is highlighted as expected.

Fixed an issue where sometimes the relevant text body of a contract would stay highlighted after the Tags pane was closed. Now, annotations are no longer highlighted if their tag is not clearly selected.

Fixed an issue where clicking the text body of an annotation in the Tags pane could fail to navigate the user to the corresponding area of the contract document. Now, users are properly directed.

Fixed an issue where users could publish AI models without training them. Now, models can only be published when in the Trained or In Review status.

Fixed an issue where opening a document from an AI Project record sometimes opened the document in Preview Mode, without the option of annotating or editing.

Fixed an issue where annotations that had been manually added to an AI Label Training document could erroneously appear on the Suggestions tab after reloading the document. Now, the annotations stay in the Annotations tab, as expected.

Fixed an issue that sometimes highlighted the Governing Law value of a contract when the same value appeared outside of a Governing Law context. For example, if a contract was under the Governing Law of New York, and the preamble of the contract mentioned New York, the document viewer would recognize and tag the New York text in the preamble as an additional instance of Governing Law. Now, Governing Law key terms are tagged only where applicable.

Fixed an issue where AI extractions sometimes failed to include subheaders present in the contract document. Now, subheaders appear as expected in the text body of the annotation.

Fixed an issue where AI extractions that included multiple columns of data could fail to extract text from top to bottom, and instead would extract text from left to right, which rearranged how the text was represented in the annotation. Now, column data is represented as expected.

Fixed an issue with settings in the Group wizard that did not apply updated permissions to sets of linked fields. Now, these changes are applied, whether they are made in the Field wizard or the Group wizard.

Fixed an error that occurred when using an action button to merge files from a record that is open for view onlyFixed an issue with Modal actions that sometimes showed fields in view-only mode in the modal that should not appear based on permissions.