...

This page covers updates for Release 2829.0.2.

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

New Features and Enhancements

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 Removed

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 Removed

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 Removed

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 Removed

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.

Bug Fixes

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

Fixed 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 only.

December 2024 Maintenance Release

This release adds the Check Dependencies button for saved searches, so you can see where a search is used in your system.

The latest DocuSign API version automatically shows the DocuSign preview screen when users create new envelopes, so let your DocuSign users know to expect this change. There is no other impact on DocuSign functionality.

Fixed an issue where opening a record from an insight popover and then closing it sometimes caused the table view to show only the record where you clicked the insight popover.

Fixed an issue where using a single field linked to multiple tables to send emails to both individual users and teams of users did not correctly send to all selected recipients.

Fixed an issue that caused an error when sending a report to a user without a login. Now, the report is sent as expected.

Fixed an issue that showed the Comments button in new records that were not yet saved, even though comments could not be added to an unsaved record. Now, the button appears only after a new record has been saved.

Fixed an issue that prevented display of Chinese characters in the document viewer.

Fixed an issue with Personal Split View that sometimes prevented applying multiple filters.

Fixed the DocuSign Recipient table's Message field to allow the maximum number of characters supported by DocuSign, 10000. Previously, it was limited to 2000 characters.

Fixed an issue that sometimes prevented selecting a linked record whose linked data included a URL field.

Fixed an issue where exporting data using the current view did not properly format the exported data from Singleton Check fields.

Fixed an issue when importing URL data that sometimes rendered & as amp;. Now, the original character is preserved.

January 2024 Maintenance Release

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

Fixed an issue that sometimes prevented OCR from extracting the full text of a document.

Fixed an issue with clearing a linked set using a scheduled import action, which sometimes prevented the full linked set from being cleared. Now, this works as expected.

Fixed an issue where, if you used a modal action to access additional fields and attempted to upload multiple files to a field that did not allow multiple files, the modal action did not show an error message, and did not open the next time you tried to use it.

Fixed an issue that prevented Ask AI from working properly on documents whose text was rotated 90 degrees.

Fixed an issue that prevented using action buttons if you changed the selected language while editing a record.

Streamline your contract review with Screens by Agiloft

Your Agiloft system now unlocks the door to Screens, an AI-powered contract analysis solution available as an app in Microsoft Word. Screens uses contract review playbooks you can configure to ensure specific contract requirements are met. Use pass/fail standards to check for compliance with requirements, and add questions to simplify document data retrieval. Screens redlines and comments help you breeze through common review tasks in a fraction of the time.

For example, an Arbitration Agreement screen would include AI prompts for all of the information your organization requires in an Arbitration Agreement contract. Simply run that screen on a third-party Arbitration Agreement to get a user-friendly score that illustrates how much of your requirements the contract has met, with extracted examples for clauses that align with your standards and items that need your attention.

Image Added

To make sure you capture any data from your users running screens, make sure to deploy the Screens app in your KB as soon as you upgrade to 29.0.2. To do so:

1. Log in to your KB as an admin.
2. Navigate to Setup > Integrations.
3. Under Screens, click Deploy.

Clicking the Deploy button does the following in your KB:

• Creates two new tables, the Screen Run and Screen Result tables. Screens results from any user are automatically mapped into these tables.
• Creates fields in these tables to capture Screens results, as well as a linked set of fields to the Attachment table. You might want to edit your Attachment table layout to add this linked set to the record form.
• Links screen result data to an Attachment record ID as long as the user opened the attachment from within Agiloft.

To open Screens:

1. Open a contract document from Agiloft using Checkout & Edit.
2. If it's not already in Microsoft Word, install the Screens app from the Microsoft App Store.
3. Once it's installed, click Screens in the top right corner.
4. Click Sign In.
5. Click Sign In with Agiloft Account.
6. Enter your Agiloft KB credentials. If you are the first user accessing Screens for your organization, make sure to log in as an administrator.
   
   1. For Server URL, copy your KB's URL, only copying from https:// to .com/, or similar.
   2. For KB Name, copy the name of the KB located in the top right corner of your KB.
   3. Use the same login and password you use to access Agiloft.
   4. Follow the prompts to provision a workspace for your organization, and select the appropriate data residency.

Once you've signed in, you can screen documents that have been opened with the Checkout & Edit feature in Agiloft. These results will populate into the Screen Result and Screen Run tables. Any time a user checks out a document and runs a screen, the results flow into the Screens tables in your KB.

For more information about setting up Screens in Agiloft, visit Screens.

For more information about Screens in general, visit the Screens help center.

All Agiloft users automatically have the ability to use Screens with the release of 29.0.2. If you want to disable Screens for your organization, refer to Screens.

Bug Fixes

Fixed an issue that sometimes caused an error regarding REST endpoints while processing documents in a Legacy Import project.

Fixed an issue with the EWSearch API where it did not return fields with null values. Now, these fields are returned with a value of null.

Fixed an issue where viewing a file was erroneously stored as a Download File activity in the activity log.

Fixed an issue with displaying Chinese characters when viewing a .docx file in the document viewer.

Fixed an issue that sometimes unexpectedly closed a user's session when logging in to Agiloft in the same KB on a second tab, or opening an email hotlink. Now, the session in the first tab is not closed in these cases.

Fixed an issue that sometimes caused errors when using Edit Fields to select values in a linked field in the main table view.

Fixed an issue where no results were returned when searching for a value that "is contained in" a link to single field with multiple values enabled.

Fixed an issue when editing a Conversion action from the Rules tab of the table wizard, where the Conversion tab of the action wizard did not loadFixed an issue where attached files sometimes failed to retain versioning text in their names when included in a K2D action. For example, a file called "examplefile--v1--12-12-2024-057853--sb.docx" would be stripped of the Agiloft-added versioning text, and would be stored only as "examplefile.docx" or similar. Now, versioning text is retained, as expected.