Page tree

25 Release Notes

This page includes the full list of documented changes for each version, but if you prefer to focus on the highlights, check out What's New instead. This page also includes minor releases that have happened since the release of version 25 and prior to the next major version.

Release 25

Introducing AI Platform, Agiloft's latest AI offering

With this release, Agiloft introduces a new AI package called AI Platform. This is the foundation for new AI features like AI Trainer and Legacy Import, which are also covered separately in more detail. If you're interested in AI Platform, reach out to your Agiloft representative for more information on features and licensing.

With an AI Platform license, you can use the following artificial intelligence features in Agiloft:

  • Train your own labels with AI Trainer
  • Import legacy contracts to Agiloft and convert them to enriched records, all with the click of a button
  • Extract and review data from third-party contracts to speed up negotiation and reduce risk

To enable AI Platform, confirm that you have the package added to your license and then complete the steps in  AI Platform. Note that the listed features might require their own additional setup.

Tailor AI model behavior to your exact needs with the new AI Trainer

With this new proprietary feature, you can create new AI models that extract custom information from contracts. Everything you need to train a model, from annotation service to training metrics, is available right in the AI Project record for your convenience. Take your system beyond the bounds of pre-trained models and train the labels you need, using your own material as a blueprint. This powerful tool puts the power of AI in your hands.

Example AI training project for Force Majeure clauses

For details about licensing, setup, and how to train a model, see AI Trainer.

Import legacy contracts quickly with AI

With AI Platform, Agiloft provides an updated and easy-to-use workflow for converting many documents into Agiloft records. This is commonly used to import legacy contracts and create corresponding Contract records with searchable field data, but you can use it to import any group of contracts in a batch.

To import a batch of documents, create a Legacy Import project from the AI Projects table, which becomes available automatically after deploying AI Platform. In the new project, simply upload your set of documents. This runs an action that automatically analyzes your documents and tags the key terms and clauses, supported by pre-trained models or custom models you've created with AI Trainer.

Example list of legacy contracts being imported

Once the document has been analyzed, you can review the tagged key terms and clauses in context on the document itself. When everything looks good, you can publish the contracts to your KB as records. The contract details are stored as field values or other related records.

For more information, see Legacy Contract Import.

Integrate contracts with your Gmail inbox with Agiloft for Gmail

Agiloft is introducing a new integration for the Google Suite: the Agiloft Gmail app.

With Agiloft for Gmail, you can seamlessly add information like attached files or notes from an email body to existing records in Agiloft. You can also send attachments from Agiloft in outgoing emails, or record third-party email correspondence. This gives you your entire contract database at your fingertips while sending or replying to emails.

For more information about using the app, see Using Agiloft for Gmail. For information on installing and configuring the app, see Setting Up Agiloft for Gmail.

Updates to Outlook App Configuration

The pathway for configuring the Agiloft Contract Assistant for Outlook has changed. Now, there is a single configuration wizard for both Outlook and the new Gmail app. To see or edit your configuration, go to Setup > Email and SMS > Agiloft Email Apps.

Analyze Agiloft data with Power BI

You can now bring Agiloft table data into Power BI to easily place it in dashboards and reports, and analyze it alongside other business data from outside Agiloft. Connect as many tables as you like, so all your data is accessible in one place.

For detailed instructions on how to integrate with Power BI, see Power BI Integration.

Insert parent clauses into a child contract using the Word app

In addition to adding clauses from a Clause Library to your contracts, you can now add clauses from the parent contract if you're working in a child contract. Clauses are automatically added to a child contract's available list when they are tagged and saved in the parent contract.

You can select these clauses from the Insert Clause window of the app. You can filter the available clauses by source to see only clauses from the Clause Library or Parent Contract.

Work with multiple Contract tables in the Word app

You can now use the Agiloft Contract Assistant for Word with multiple Contract tables in your KB, meaning that you can send information about the documents you analyze to more than just a single Contract table. For example, even if you keep sales and procurement contracts in separate tables, you can analyze both types of contract using the Word app, and then send the information to the proper table. Note that this feature is not intended for tables that do not hold contracts.

To set up support for multiple Contract tables, go to Setup > Integrations > Agiloft Contract Concept Mapping and click Configure. Then, click New under Table Configurations and follow the steps in Configuring the Agiloft Contract Assistant for Word for each additional Contract table you'd like to work with.

Updates to Word App Configuration

The pathway for configuring the Agiloft Contract Assistant for Word has changed to support using the app with multiple tables. To see or edit your configuration, go to Setup > Integration > Agiloft Contract Concept Mapping.

Create smooth workflows and intuitive forms with new Modal actions

New Modal actions make it easy to nest workflows within workflows, so you can easily move optional steps out of the workflow of the main record without actually leaving that record. This gives you more freedom in designing complex record forms and breaking workflows into smaller sections that are easier for your users to follow.

For example, when working with a Contract record, you might need to upload a file as a related Attachment record. When you finish selecting a type, adding a title, and saving the file, you're still working in the Contract record, where you can select the new attachment right away.

Modal actions open a pop-up window that contains a set of fields. You can use Modal actions to create or update records in any table without leaving the current record, or complete optional fields that are part of the same table you're working in. For example, if a certain contract type requires a series of additional fields be filled out, you might choose to present those fields using a Modal action instead of using conditional visibility.

Attach a File modal window

For more information about this new action type, see Modal Actions.

Preview your nav menu changes in setup

Edit your nav bar with confidence thanks to the new live preview, which shows how your nav bar will look based on your current settings. This makes it easier to test and spot-check your changes, and envision how groupings will look in real workflows.

This change was made in part to support the upcoming deprecation of the left pane. If you are still using the left pane in your system, see Switching to the New User Interface for recommendations on how to make the transition smooth. Note that beginning with this release, you can no longer save a navigation menu configuration as a left pane; making changes to a navigation menu will automatically convert it to a top nav bar.

New look for Actions setup tab

Updates to the Action tab of the table wizard offer less scrolling, less wasted space, and a fresh, updated look for admins.

Actions tab showing the list of existing actions alongside the buttons to create new actions

Modernized File with Versioning fields

Enjoy improved usability for File with Versioning fields with a much larger target area, more informative graphics, and better display handling when a field contains many attached files.

Drag and drop field for attached files

Smoother workflow for required fields

Required fields now show a warning message in-line on the record form, rather than showing a pop-up message that interrupts the workflow. For example, if you enter a value and Tab to the next field, but immediately realize you missed a character, you can now return to the prior field without a pop-up interrupting you.

Note that a pop-up warning is still shown for required linked fields, and if you try to save the record without completing all the required fields.

New Self-Serve licensing option

The new Self-Serve license is ideal for users who deal with a large volume of standardized contracts and only need to perform a few basic duties. It grants limited access to the power-user interface. It allows users to generate and execute contracts using standard, pre-approved document templates. This license gives you a flexible option for users who don't need significant access to the system.

More intuitive field selection in email templates

When you select fields to include in an email template, the list of fields now appears in alphabetical order. This makes it easier and quicker to find the fields you're looking for.

New dynamic symbol option for Currency fields

To better support business that spans multiple currencies, Currency fields now offer a dynamic symbol display option. Simply add a link to the Currency table and point to that linked field to determine the symbol shown next to the numerical value. The simplest way to implement this is to add a field in the Currency table that contains the proper symbol for each type of currency, and then link to that field from the table where you need to show multiple currency symbols. You can even add the linked field to the record view if you want to allow users to manually set a different symbol.

This display option is also available for Calculated Result and Calculation on Multiple Linked Records fields. In the same way, the symbol is selected based on another field in the record.

The setting is located on the Display tab of the field wizard.

Contract Amount showing dynamic currency symbol

Automatically refresh embedded tables

All embedded tables now offer a new display setting you can use to automatically refresh the table data at a set rate. This includes related tables, links to selected fields with multiple values enabled, and embedded search results.

To set an embedded table to refresh automatically, edit the field, go to the Display tab, and change Table View Refresh Rate to Every. Enter the minutes and seconds as desired to automatically refresh the embedded table contents on that interval. To maintain server performance, we recommend setting a refresh rate at or above 30 seconds.

If you leave a field set to Default, it behaves the way it always has, and refreshes only when the main record is saved.

Use Alphanumeric Sender IDs with 2FA

Two-factor authentication now includes an option to use an Alphanumeric Sender ID, a practice that is required in some regions. If you enable this option, SMS messages for two-factor authentication are sent using the Alphanumeric Sender ID instead of the Twilio phone number and country code. 

You can limit this setting to certain countries if desired. If you select a country that does not support Alphanumeric Sender ID, the system automatically uses the phone number instead.

Note that the expectations for Alphanumeric Sender ID differ between countries. In some countries, you are required to pre-register the Alphanumeric Sender ID before utilizing it. It is your responsibility to determine the requirements for the countries where you want to use the feature.

To enable Alphanumeric Sender ID, go to Setup > Access > Two-Factor Authentication, and select the Use Alphanumeric Sender ID checkbox. Enter the Alphanumeric Sender ID you want to use, and then select the applicable countries from the list. Hold the Ctrl key to select multiple countries.

For more information, see Two-Factor Authentication.

Map Salesforce picklists to Agiloft choice fields

You can now sync data from a Salesforce picklist into Agiloft as a choice field, and from multi-select picklists into multi-choice fields. You can map these fields in the Salesforce Managed Package, and then sync them by clicking Upload Mapping.

Once the fields are mapped, you can configure the values that will be synced from the picklist to the choice or multi-choice field by following the steps at Salesforce Integration under the Picklist to Choice List section.

DocuSign tags now support optional fields

Configure your document templates with optional DocuSign tags that allow signers to skip them as needed. As part of this change, DocuSign tags offer several newly supported options. You can append any number of these options by including the appropriate property and setting inside the brackets at the end of the format with the following syntax:


For example, use optional:true to allow signers to skip the tag, or add tooltip:Tooltip Text to include instructions if the signer hovers over the tag. To add multiple properties in one tag, place a comma between the property:value pairs.

DocuSign email tags now available for document templates

Email tags for DocuSign are now supported in document templates, so you can simplify your templates and keep your data sources consistent. To use this tag type, simply enter "EmailAddress" in the tag type position of the syntax:


Then, replace FieldName, RoleName, and Label as needed. For detailed information about using DocuSign tags in document templates, see Create Document Templates with DocuSign Tags.

More intuitive field names in DocuSign setup

To make setup easier to follow, the DocuSign setup page now uses the same terms that DocuSign does. Instead of having to match the Client ID field in Agiloft to the Integration Key provided by DocuSign, Agiloft now uses the same terminology.

Download an OpenAPI JSON file from Agiloft

You can now download a copy of Agiloft's OpenAPI JSON file directly from your KB, which provides examples of REST APIs that are supported by Postman.

To download the file, go to Setup > System > View REST documentation > Download OpenAPI JSON.

Request attachment details with new REST call

Use the new EWAttachInfo operation to request information about a record's attachments in a specified field. The call returns the position, the name, and file size for each attached file. The first file position is 0, not 1. 

For more information, visit REST - AttachInfo.

Lock, unlock, or check lock status of records with new REST call

You can now lock, unlock, or check the lock status of any record using new REST endpoint EWLock. For more information, see REST - Lock.

New Webhook actions to call Integration Hub webhooks

Use the new Webhook action type to manually call a webhook you created in the Integration Hub. Add this action to rules, actions, or action buttons to manually trigger the webhook, and optionally add a history entry to document the event. This makes it easy to run Workato recipes directly from a record. For example, you might automatically run a Webhook action when a contract's end date changes, to sync the new date to Google Calendar.

For more information, see Webhook Actions.

Convert Document Format action now supports MS Word to AAF JSON

Convert Document Format actions now support converting documents from MS Word to AAF JSON format. This new option is useful for importing values found in the content controls of a .docx document into Agiloft. If no content controls are found, the field designated for import is left empty.

To use this new feature, create a Convert Document Format action and select MS Word to AAF JSON from the Options tab. This is a primary process in the Agiloft Contract Assistant for Word's workflow, but is now available in other possible configurations as well.

Convert documents to and from OOXML

When creating a Convert Document Format action, you can now choose to convert a .docx file to OOXML. You can also convert an OOXML file to .docx.

New action types to support AI Platform

To power AI Platform, your system now includes two new action types:

  • The new Data Analysis action is a more label-centric method of extracting data compared to the existing Machine Learning action. Machine Learning actions use one model to extract labels, whereas the Document Analysis action extracts a configurable label list that  can leverage any number of models, including third-party models.
  • The new Publish action is used by AI Platform to publish key terms and clauses that have been extracted from a contract by a data analysis action.

These actions are primarily used behind the scenes by AI Platform workflows, but you can use them on their own if necessary. All require an AI Platform license.

Security enhancements

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

Bug Fixes

Fixed an issue that caused endless loading in the Word app when a user deleted an associated Contract record, and then tried to open the Attachment record in the Word app. Now, the app displays a message saying the information no longer exists or you do not have permission to view it.

Fixed an issue that caused some linked fields with multiple values to appear very wide on the record form. Now, these fields appear as expected.

Fixed an issue that showed a blank exit URL when creating a hyperlink to view a record, even though the exit URL functioned properly. Now, the default exit URL is displayed in the field when creating the hyperlink.

Fixed an issue that caused text to incorrectly appear italicized under some circumstances. Now, this issue is fixed.

Fixed an issue where Calculated Result fields could be configured with a formula that did not output a numeric value. Now, incompatible formulas are not accepted.

Fixed an issue with DocuSign that sometimes caused the current file to appear with a prior file name. Now, the current file name is shown.

Fixed an issue with importing KBs that could cause the process to run slower than usual.

Fixed an issue that sometimes caused required fields to not be enforced on links to single fields from multiple tables. Now, this issue is fixed.

Fixed an issue with Table widgets where expanding the search details for complex searches could result in the actual table view being hidden. Now, the details for complex searches are truncated, and the user can see the full details in a tooltip by hovering over the truncated text.

Fixed an issue where the Contract Amount field in the user interface of the Outlook app occassionally displayed currency in a number format instead of a currency format. Now, the field is always displayed as currency.

Fixed an issue that prevented REST API calls for columns in a table with a vast amount of history data.

Fixed an issue with the Word app that caused Clause records to appear as if they had changed when the record was saved, even if the Clause records had not been altered. Now, this issue is fixed.

Fixed an issue where, if you used Quick Edit to make a change in the table view, and then refreshed the view without saving, the record remained locked. Now, the record is unlocked, as expected.

Fixed an issue where the Outlook app sometimes disappeared when navigating to a shared folder. Now, the app remains accessible.

Fixed an issue that sometimes caused newly-added Clause records to appear edited in the Current Markup field, even though the text had not been altered. Now, this doesn't happen.

Fixed an issue where using Quick Edit on an embedded table sometimes saved only some of the changes made. Now, all updates are saved successfully.

Fixed an issue where related tables did not display loading progress when pointing to a very large table. Now, if a related table is still loading, the progress is shown and the rest of the record form is usable while the related table loads.

Fixed an issue that caused very long formulas to be truncated upon saving. Now, the entire formula is stored intact.

Fixed an issue that caused a new tmp file to be created each time a user logged in.

Fixed an error that occurred in the Agiloft app for Microsoft Word when saving a tag that contains a percentage sign (%).

Fixed an issue with the Agiloft Contract Assistant for Microsoft Word that caused marked-up text tagged to be included in the Text body of the new tag. Now, the marked-up text is not included in the new tag.

Fixed an issue that sometimes prevented email attachments from saving to the Contract record from the Outlook app.

Fixed an issue where the Agiloft Contract Assistant for Word didn't always update the Source Clause ID field of a Contract Clause record when a clause was replaced using the Word app. Now, this field is consistently updated.

Fixed an issue where attempting to save document templates with around 100 or more clauses caused an error. Now, this error does not occur.

Fixed an issue that prevented manually updating a recipient's email address for an Adobe Sign agreement after the agreement had been sent. Now, using the "Update Recipient to Adobe Sign" button works as expected.

Fixed an issue that caused an error when running OCR on a very large file.

Fixed an issue where Excel reports did not include apostrophes or quotation marks. Now, these characters are preserved.

Fixed an issue with database integrations that prevented the Identifying column from appearing. Now, this column is available when configuring database integrations to identify matching records between the KB and the database.

Fixed an issue where record names with multiple sequential spaces were shown with one space in linked field drop-downs, which prevented successful auto-completion. Now, these records can be selected and linked without issue, even when the extra spaces are truncated for readability.

Fixed an issue with mass editing linked fields with multiple values enabled, where mass edit defaulted to overwriting the values instead of appending. Now, the default setting is to append the new values, as expecated.

Fixed an issue that sometimes prevented linked sets from updating when they interacted with a Date/Time field. Now, this issue is fixed.

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 that prevented saving a Google Translate API key. Now, the key can be entered and saved successfully.

Fixed an issue with email hotlinks that caused users to be logged out prematurely when their workflows included secondary records. For example, if you logged in to edit a contract and created a new approval record, when you closed the approval, you were logged out. Now, the user is only logged out when the primary record is closed, as expected.

Fixed an issue that caused some linked fields not to appear on the record form if they were configured to display with a look-up icon. Now, these fields appear as expected.

Fixed an issue with Charts/Reports where a maximum length warning prevented a scheduled report from running at all.

Fixed an issue with Cloud OCR that caused an error and prevented OCR from running.

Fixed an issue where running a search in a table widget caused infinite loading if the saved search had different assigned views in the widget and the source table. Now, the proper view is applied and the search loads successfully.

Fixed an issue that ignored run-time search filters if the search ran without being saved. Now, the run-time filter is applied appropriately.

Fixed an issue that prevented uploading translation files in some cases. Now, these files can be uploaded without issue.

Fixed an issue that caused HTML fields exported in Excel format to include HTML tags in plain text, instead of removing them.

Fixed an issue that caused an error when an OCR action was configured to store a file in the original file field. Now, this works as expected.

Fixed an issue that prevented comments from saving, if a comment was added manually and an action button updated the same comment field during the same interaction. Now, both comments are preserved, as expected.

Fixed an issue that sometimes caused attachments to be sent in the wrong format, with extra characters in the file name. Now, these attachments are processed and sent correctly.

Fixed an issue that caused some linked fields that were configured to search All Text Fields to instead search All Linked Fields. Now, this setting is always respected.

Fixed an issue that prevented adding new groups to the SOAP/REST permission list.

Fixed an issue that sometimes prevented password reset emails from being sent. Now, they are sent as expected.

Fixed an issue that prevented sending emails to CC recipients if the CC recipients were added manually to an email that was written by inserting a template. Now, these emails are sent to CC recipients as expected.

September 2023 Maintenance Release

Fixed an issue where the Tags tab may not appear when clicked in the Document Viewer. Now, the Tags tab shows as expected, instead of just staying on the Details tab.

Fixed an issue that made syncing with another system significantly slower. Now, this issue is fixed.

Fixed an issue where action buttons did not observe the "Wait for Completion" setting when waiting for an interactive conversion to be completed. Now, the action sequence waits until the conversion is complete before proceeding to the next action.

Fixed an issue with Publish actions that caused incorrect formatting of some dates.

Fixed an issue with Teams that sometimes caused duplicate fields to appear in the response. Now, these duplicates do not appear.

Fixed an issue that prevented related contracts from inheriting party information from the parent contract. Now, the correct information is inherited as configured.

Fixed an issue with the cardinal option of the num2words formula, where the formula always included a decimal in the output. Now, if the number ends in .0 or .00, the output no longer includes "point zero" or "point zero zero" and instead ends at the whole number.

Fixed an issue with formulas that did not allow partial bold inside a formula. Now, the $field_from_other_table formula can be called with "skipformulatagging=true" in the parameter list in order to pass through simple bold or italic formatting from the field being inserted.

Fixed an issue that caused an error when email hotlinks included a redirect to a URL that included a space.

Fixed an issue with search that prevented retrieving more than 250 results. Now, this limit is removed.

Fixed an issue that prevented saving the default teams for a navigation menu.

Fixed an issue that caused parent fields not to appear in Formula Help when adding an Update action to a Linked Record action. Now, they appear.

Fixed an issue with Adobe Sign that caused an error when passing information between systems.

Fixed an issue that caused inconsistent results from the same search criteria.

Fixed an issue that prevented the Remove Access button from disconnecting from DocuSign.

Fixed an issue where clicking the "Show tags in document toggle" button in the Contract Assistant for Word did not work in some cases.

October 2023 Maintenance Release

Fixed an issue with action buttons that did not validate all the required fields if the button included saving the record if additional required fields appeared after saving. In these situations, the additional fields should also be required. Now, this issue is fixed.

Fixed an issue where using a conversion to create a new linked record did not automatically refresh embedded tables to show the new record. Now, the embedded table refreshes automatically.

Fixed an issue that prevented the options menu and Copy Link option from appearing for users with the necessary permissions. Now, these appear as expected.

Fixed an issue with reports that caused an error when using a run-time filter on a linked Date/Time field.

Fixed an issue where setting a very low embedded table refresh rate could cause the embedded table to appear to refresh constantly. Now, the rate is respected correctly.

Fixed an issue where editing the formatting of a link in an email template sometimes caused the text to be replaced with the URL.

Fixed an issue that prevented exporting content to Excel when using certain saved searches to filter the records.

Fixed an issue where it was not possible to change the selection of a linked field when editing an Update Fields action that updated that linked field. Now, you can change the selection.

Fixed an issue that caused an error message to appear when using Save & Continue, even though the record saved successfully.

Fixed an issue that prevented copying multiple People records at once.

Fixed an issue that sometimes prevented multi-select fields from copying during a conversion.

Fixed an issue that sometimes caused If-Then-Else rules to incorrectly interpret an Integer field as having changed during the user's last modification even if the field had not changed. Now, this issue is fixed.

Fixed an issue that occurred if an external system tried to create a user record via REST with an email address that was already assigned to another user. Previously, this returned an error, but still created the user record behind the scenes. Now, this returns an error and does not create a hidden user record.

Fixed an issue that prevented authentication of the Teams app via SAML.

Fixed an issue in the saved search wizard where typing part of the condition value and then clicking the suggested text caused the value box to disappear.

Fixed an issue where opening a record pop-over view and clicking an attached file link did not bring the file download window to the front, and instead loaded it behind the pop-over. Now, the download window appears in front, as expected.

Fixed an issue that occurred when documents were uploaded to an AI Project record. Previously, these files were converted and sent as .txt files to the Attachment table. Now, when the Publish action sends files from an AI Project record to the Attachments table, the new Attachment records retain their original file format.

Fixed an issue that sometimes caused Adobe Sign agreements to become stuck on Pending Signature, even when the agreement was signed and finalized. Now, the status updates as expected.

Fixed an issue with Attachment records that prevented versioned files from being superseded and tracked if "Display changes to .docx file" was set to Yes. Now, the records are handled as expected.

November 2023 Maintenance Release

Fixed an issue that caused an error in some circumstances when opening an attached Word document directly from the Attachments table.

Fixed an issue where running a conversion from a hyperlinked text box sometimes caused the text entry field to disappear, leaving only the lookup icon. Now, the entry field remains, as expected.

Fixed an issue that occurred when editing multiple records at once, which caused the Mass Edit window to close unexpectedly and fail to update the records.

Fixed an issue that prevented attaching files while automated rules or actions were running on the same record.

Fixed an issue where fields with conditional visibility were not shown when the conditions were met, until the record was saved. Now, saving the record is not necessary for these fields to appear.

Fixed an issue that occurred when an end user submitted a contract in the EUI, which sometimes caused the record to remain locked until the end user logged out. Now, the record is unlocked when the user closes it, as expected.

Fixed an issue in the EUI where running a run-time saved search and then clearing all filters could cause the action bar to appear even if the EUI template included showToolBar=false.

Fixed an issue that hid the search bar in table widgets, if the table was first filtered to show no records.

Fixed an issue where action buttons running Validation actions did not offer the user the option to ignore the warning and save, even if the Validation action was configured that way. Now, the pop-up offers the options as configured.

Fixed an issue where an action button configured to save and open the record for editing did not consistently apply changes if they were made and then saved using Save and Continue. Now, the changes are saved properly in this situation.

December 2023 Maintenance Release

Fixed an issue that could cause sync to fail when the entity set contained Publish actions.

Fixed an issue that caused dates synced with Integration Hub to be one day ahead on servers whose time zone is behind UTC+0. Now, dates are synced correctly regardless of server time zone.

Fixed an issue caused when Quick Edit changes inside an embedded table were not saved before clicking an action button that utilized the changed values. Previously, this caused a pop-up to appear asking the user to abandon the change or return and save it. Now, the change is applied and the action button automation proceeds.

Fixed an issue that prevented the API status message from appearing after the user clicked an action button that ran an API call. Now, the status message appears at the top, as it did before.

Fixed an issue that prevented applying end user updates to a record's workflow status under certain circumstances.

Fixed an issue that prevented embedded tables from refreshing and showing a new record after a new record was created. Now, the embedded table refreshes and shows the newly added record, as expected.

Fixed an issue with running a run-time search filter on a multi-select field, which sometimes prevented selecting multiple values for searching.

January 2024 Maintenance Release

Fixed an issue when purchasing Adobe Sign agreements, where the pricing tiers were not reflected in the Payment Amount shown. Now, the Payment Amount is displayed correctly, according to the tiers.

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