---
title: "What's New"
canonical: "https://help.agiloft.com/space/HELP/43715649/What's%20New"
format: markdown
---
The Agiloft release cadence is as follows:

- **Agiloft Core Platform:** Releases this February, July, and November with new functionality, plus monthly maintenance releases.
- **Connected Services: **Monthly releases with new functionality, plus anytime maintenance releases.

This page includes the full list of changes for the listed version of the Agiloft Core Platform, including monthly maintenance releases, plus changes to Connected Services during the same period.

This page covers updates for **Release 34.** The previous version was [Release 33](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/779092083).

To jump to a section of this page:  

> Macro (toc)

# Agiloft Core Platform July 2026 Release

## Introducing SCIM provisioning

You can now automate user lifecycle management in Agiloft CLM with System for Cross-domain Identity Management (SCIM) user provisioning. With SCIM, your identity provider (IdP) serves as the source of truth for user accounts, automatically provisioning, updating, and deactivating users in your KB as changes occur in the IdP. When you enable SCIM, your IdP can automatically: 

- Create user records in your KB when users are onboarded
- Update user information in your KB when it changes
- Deactivate users in your KB when they’re removed or deactivated
- Reactivate users when they become active again

For more information and setup instructions, see [Provision Users with SCIM](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/779649034).

## Improved security for Integration Hub connections

The Agiloft CLM Integration Hub connector is enhanced to improve the security and reliability of integrations. With this update, Agiloft CLM adds environment-specific details and a signature to webhook requests before sending them. When a request is received, the connector validates the request source and signature. If validation succeeds, the connector triggers the recipe. If validation fails, the connector rejects the request and the recipe is not triggered.

This enhancement helps ensure that:

- Recipes are triggered only by requests from the intended KB. For example, requests from a development environment can't trigger recipes for a production environment.
- Only authentic webhook requests that haven't been altered are processed.

This change is automatically applied to new recipes. Simply stop and restart your existing recipes to pick up the new connector behavior and enforce the validations for the recipes.

## Improved Word app login behavior

To prevent tedious login prompts, after you log in to the Word app once, you no longer need to click the Login button at the start of every session. Instead, your credentials are applied to future sessions automatically until you manually log out.

## New, easy user deactivation

Easily activate and deactivate users in your system, without losing audit data and without extra steps. When you deactivate a user, they can no longer log in; any active sessions are immediately ended; they stop receiving outbound emails; and any inbound emails they send to the system are treated as emails from a non-user. You can also reactivate a user if needed, to reverse all these changes.

To enable the new user status management, simply go to Setup > Access and click Deploy User Status Management. This adds the new User Is Active field to your People table and its subtables, and adds it to the layout for each one. From there, you can simply change the field from True to False and save the record to immediately [deactivate a user](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/43717058).

By default, User Is Active can only be edited by admins, but you can grant other groups access to view or edit the field as needed.

## Improved email handling for replies to comment notifications

When recipients reply to comment notification emails, rather than opening the comment in Agiloft CLM to reply, these emails are now automatically discarded instead of being subject to your inbound email handling rules. This avoids creating confusing or extraneous records in the system, and makes it clear to users that their reply was not saved as a comment. 

Now, comment notification emails are automatically sent from no-reply@agiloft.com, so that responses are not caught in inbound handling. If desired, you can change this From address in **Setup > Email and SMS > Email Server Settings** by entering the new address in No-Reply Email for Comment Notifications.

## Improvements to new drop-downs

This release includes several improvements to the new drop-downs, if you're already using them:

- When multiple values are selected in a multi-select drop-down, the selected values are now shown at the top of the drop-down list to make it easier to see what has already been chosen.
- Your search terms are treated as the beginning or entirety of a term, so the drop-down no longer suggests results where your term appears in the middle or end of a longer term. For example, "Agi" will return Agiloft Inc. and Agile Technologies, but not Fragile Corp.
- Clearing a selection using X has more intuitive behavior, retaining focus if the drop-down is not open, and keeping the drop-down open if it is already.
- New drop-downs now support the Source Field Display & Table Search display setting for linked fields, which references the display selected for the field being linked to.

## Dashboard localization now supported

Localization files now include dashboard names, widget names, and filter names to give multi-language users an improved experience with home pages and dashboards.

## Filter dashboards by Choice fields

Filter your dashboards by your own Choice and Multi-Choice fields for more flexibility and versatility. When creating a dashboard filter, simply select Choice Based and then choose a field from the drop-down menu.

## Improvements to entity set sync reports and communications

This release features several improvements to post-sync processes for entity set sync:

- The post-sync email report is now sent only to the user who initiated the sync process, rather than to every administrator.
- The post-sync email report now shares the success or failure of the sync and directs the admin to the system to see details, rather than sending the entire transfer report in the body of the email.
- Entity sync reports are now saved to the sync logs, so they can be accessed for reference and troubleshooting. These reports list the entities and records that were created or updated by the entity sync. To see the reports, simply go to Sync History and download the logs for the sync.

## Fine-tune the start time of time-based rules

For time-based rules that run on minute-based schedules, you now have the option to offset the start time by five-minute intervals. Previously, when a rule was configured to run every N minutes, the Start Time field was disabled and the schedule always started from minute :00 of each hour. Now, you can shift the schedule by selecting a start minute. For example, if a rule is scheduled to run every 30 minutes, and Start Time is 5 minutes, the rule runs at :05 and :35 of each hour.

**Note**: The start minute offset is only applied to rules that run every 5, 10, 15, 20, or 30 minutes. For rules that run at other intervals, the start minute selection is ignored, and the rule runs at system-determined times like the previous behavior.

## Use $global.null to clear an entire linked set

If you use $global.null to clear the value of one field in a linked set, previously, the system did not clear the rest of the linked set, and your cleared value simply refreshed using the data from the other fields. Now, if you use $global.null in this fashion, you can set the new cascade_null_lf global variable to Yes to adjust this behavior so the entire linked set is cleared if $global.null is applied to one of the fields in the set.

Note that if a linked set accepts loose links, applying $global.null to a field with a loose link will clear only that specific field, not the entire set. 

By default, the old behavior is retained in existing KBs, and the new global variable is set to No.

## Removing obsolete integrations

You might notice the Setup > Integration menu has less clutter, with several obsolete integrations removed from the list. Removals include Bomgar, Twitter, Alexa, Payments, and others.

## Fix to ACCM Upgrade

> 📝 This fix requires manual remediation if your KB is affected.

Fixed an issue that could cause the Current Version linked fields in the Attachments table to become unlinked after upgrading Agiloft Contract Concept Mapping. If the fields became unlinked, the Make This Attachment Current Version and Supersede File action buttons in Attachment records stopped working. Also, the tree view of superseded documents displayed incorrectly. Previous versions were nested under one another instead of appearing as direct children of the current version. 

This release prevents the issue from appearing for future Agiloft Contract Concept Mapping upgrades. If the issue occurred in your KB before it was upgraded to this release, you may need to manually restore the linked fields and related version control actions. To determine if your KB requires repair:

1. Go to Setup Attachments and click the Fields tab.
2. Find the Current Version, Current Version ID, and Current Version Title fields.
  - If the fields are a linked set with a "Link to: selected fields from other table Attachment" data type, no action is required.
  - If they're separate fields with different data types, proceed to the next steps to restore the linked set and related version control functionality.

<details>
<summary>To restore the linked set and fix your KB...</summary>

1. Rename the Current Version, Current Version ID, and Current Version Title fields by adding `zz` as a prefix.
2. Create a new "Link to selected fields from other table" field:
  1. Select Attachment as the table.
  2. Do not allow the fields to hold multiple values.
  3. On the Fields tab, select Attached File and enter Current Version as the field label. Select ID and enter Current Version ID as the label, and select Title and enter Current Version Title as the label.
  4. Set permissions and options as needed and save the set.
3. Now that the linked set is created, go to the Actions tab and update three linked record actions:
  - L:Supersede Previous Versions of Edited Document:
    - Update the chain to: Attachment/Source Attachment ID for Revision -> Attachment <- Attachment/Current Version,Current Version ID,Current Version Title
    - At the Attachment level, add these two actions: U: Set Current Version from New Revised Attachment and U: Set Status to Superseded
    - At the Attachment/Current Version,Current Version ID,Current Version Title level, add these actions: U: Set Current Version from New Revised Attachment and U: Set Status to Superseded
  - L:Update Current Version in Child Superseded Files - Make Current Version:
    - Update the chain to: Attachment/Current Version ID -> Attachment <- Attachment/Current Version,Current Version ID,Current Version Title
    - At the Attachment/Current Version,Current Version ID,Current Version Title level, add this action: U: Set Current Version from Attachment
  - L:Update Current Version in Child Superseded Files - Supersede File:
    - Update the chain to: Attachment/File to Supersede ID -> Attachment <- Attachment/Current Version,Current Version ID,Current Version Title
    - At the Attachment/Current Version,Current Version ID,Current Version Title level, add this action: U: Set Current Version from Attachment
4. Now that the linked set and actions are repaired, the last step is to check for any dependencies with the fields you renamed and then delete the fields:
  1. Go to the Fields tab.
  2. Select one of the existing fields that are now prefixed with `zz` and click Check Dependencies.
  3. If there are dependencies, resolve them by changing the dependent item to use the newly created fields from the linked set.
  4. When there aren't any dependencies, delete the field.
  5. Repeat these steps for each of the renamed fields.
</details>

## Bug Fixes

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

Fixed an issue where printing records sometimes caused the system to stop responding.

Fixed an issue where selecting a different language redirected the user to the home page, rather than staying on the current page.

Fixed an issue where uploading multiple attachments from Outlook to Agiloft CLM simultaneously could cause errors in the upload process. Now, attachments are uploaded individually to prevent errors.

Fixed an issue where Date or Date/Time linked fields sometimes showed display options that were not actually supported. Now, unsupported options are disabled in the display options.

Fixed an issue where Calculation on Multiple Linked Records and Calculated Result fields did not offer the Deletable option in the field wizard.

Fixed an issue where Oracle integrations did not create a webhook for each connection.

Fixed an issue where copying a group with a Standard or Admin license type created a new group with the Requester license type instead. Now, the license type is copied, as expected.

Fixed an issue where some instances of client IDs and secrets were displayed by default, rather than requiring interaction to display the values.

Fixed an issue where linked fields with "Allow entries not in source table" enabled did not consistently save manual entries. Now, manual entries in these cases are saved correctly, as expected.

Fixed an issue in AI Projects that sometimes caused necessary fields to display outside of the visible window.

Fixed an issue that sometimes caused errors when trying to rename an attachment that already had many versions saved.

Fixed an issue where, in some circumstances, using a multi-choice field as a search parameter was not handled properly if no values were selected.

Fixed an issue where the Formula Help variables list did not show the current labels of fields. For example, updating a legacy field to begin with "zz" was not reflected in the list and did not move the field to the bottom of the list.

Fixed an issue where the Formula Help variables list did not include both fields if a field was renamed and a new field was created using the original name of the older field.

Fixed an issue where the status window for field deletion stalled at 100% without completing.

Fixed an issue where selecting a saved search with a specified view did not consistently update the filters in the Quick Search pane.

Fixed an issue where special characters, such as letters with accent marks, did not display correctly in notifications.

Fixed an issue where merging documents sometimes altered the placement of comments and tracked changes.

Fixed an issue on the Options tab of the Export wizard where the list of views in the Fields section showed views' logical names rather than their user-friendly labels.

Fixed an issue where Quick Search filters on dates sometimes did not respond to the user clicking Done to apply the filter.

Fixed instances where the drop-down list of time zones was shown in a non-standard order.

Fixed an issue where the error URL, exit URL, and cancel URL global variables did not properly handle ampersands (&).

Fixed an issue where the dashboard widget setting "Do not include an Action Bar with the table" was not consistently respected.

Fixed an issue where some table wizards did not successfully generate HTML files from the Download HTML button on the API tab.

# Connected Services July 2026 Release

## Access Astra analysis directly from Ask AI

You can now send documents to Astra directly from Ask AI, offering a quick path to move from your CLM KB into Astra analysis. Simply Ask AI to send a contract, select it, and confirm your choices. Ask AI then links directly to the document's location in Astra, so you can click the link and move seamlessly into Astra analysis.

For more information, visit [Ask AI](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/43718504).

## Create new records automatically with Ask AI

Easily create new Contract and Attachments records by uploading files directly in Ask AI. To do so, simply navigate to the Ask AI page and drop in a file, or ask it to help you create a contract record. This makes it easy to create multiple contract records quickly and accurately, all without leaving the Ask AI interface. 

After Ask AI extracts the contract data, it prompts you to review and approve any extracted fields before finalizing the record and creating it in Agiloft. You can make edits directly if needed. For more information, visit [Ask AI](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/43718504).

![Ask AI showing pre-populated fields for creating a new contract record](media://aa1f66bb-a3a4-4815-930e-e76d53c19698)

## Update contracts directly from Ask AI

Complete more of your tasks from within Ask AI with the newly added power to update records directly in an Ask AI conversation. Now, you can follow a structured conversation with Ask AI to update values and replace or add files in existing records. Simply access Ask AI, provide the IDs of the contracts along with the field names and new values, verify the changes, and Ask AI handles the rest. 

For more information, visit [Ask AI](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/43718504).

![Ask AI showing drafted updates based on prompt](media://29f6b232-4f23-4de0-aab2-175f6f13f985)

## Additional Improvements to Ask AI

Enjoy several additional improvements to Ask AI Beta: 

- Better visibility to progress while Ask AI is working on a query
- The ability to search across multiple tables, records, and files in a single query
- Better processing of complex table data inputs from contracts, such as pricing exhibits, SOWs, and order forms
- Better output of complex table data in responses

## Better table data extraction from OCR documents

Significant improvements have been made to data extraction from OCR-processed documents that include complex tables, providing more reliable and accurate extraction data for sources like pricing exhibits, SOWs, and order forms. 

This applies to all features in Agiloft CLM that rely on ingesting documents, including but not limited to Ask AI, Prompt Lab, and workflows using [Document Analysis actions](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/43718436).

## Bug Fixes

Fixed several issues in Ask AI, including:

- Unclear messaging and error handling
- Inconsistent formatting for tables and links provided in responses
- Having to repeat prompts multiple times
- Incomplete search results
- Inability to load or view any additional records if an answer contains over 50 records
- Occasional outputs of irrelevant responses
- Inconsistency around handling user requests that include first person pronouns or contract requester names
- No results showing for time-based queries, despite matching tasks existing
- False, perpetual In Progress status for some documentation-related queries
- Losing example queries when refreshing the page

Fixed an issue where if certain models were deprecated by their hosting site, users would get errors when running an AI action that used that model.

Fixed an issue where users could see data discrepancies in their KB after running screen run actions, particularly if the action produced a large number of fields with significant amounts of text. Now, KBs reflect screen run data comprehensively, as expected.

Fixed an issue where some files processed in AI Platform could have errors in how dollar signs were displayed. Now, dollar signs appear as expected.

# Agiloft Core Platform August 2026 Release

## Sync e-signature objects with Agiloft for Salesforce integration

The Agiloft for Salesforce managed package now includes Signature Agreement and Signature Recipient objects for e-signature integrations. Together with synchronization of approvals, tasks, and obligations, these new objects bring greater visibility into key contract lifecycle activities directly within Salesforce. You can track approval progress, manage tasks, monitor obligations, and view signature status all without leaving Salesforce.

For information about setting up the integration and synchronizing data with Agiloft CLM, see [Salesforce Integration](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/43717944).

## Bug Fixes

Fixed an issue where attempting to access your KB through the integrated Microsoft Outlook app resulted in a blank screen.

Fixed an issue where exporting a scheduled chart report to another KB through a sync set sometimes did not include the selected Team.

Fixed an issue in the Microsoft Word app where the Manage Clause Library option was available when viewing attachments that were already associated with a Contract record. Now this button is hidden in this context.

Fixed an issue where if a linked field was connected to two or more tables, the field's dropdown list showed values from only one of the linked tables. Now, all available values are shown, as expected.

Fixed an issue that prevented uploading a file to a file field, deleting that file, and uploading it again in the same modal interaction.

Fixed an issue where sync did not correctly update the "Update all inbound email filter" setting in Inbound Email Accounts.

Fixed an issue where permission to export tables was improperly considered when evaluating the group's license type. This setting no longer affects a group's license type. As part of this fix, upon upgrade, all Standard license type groups in your KB are reevaluated to make sure the correct license type is assigned.

Fixed an issue with displaying linked Phone fields. Now, these fields always use Source Field Display for a consistent experience.

Fixed an issue with Modal actions where required fields that were hidden by visibility conditions were still treated as required. Now, this behavior is consistent with the main record view, and hidden fields are not treated as required.

Fixed an issue where Calculated Result fields did not consistently apply the selected setting for rounding.

Fixed several issues that occurred when assigning the same email address for multiple Docusign recipients.

Fixed an issue where email notifications for new record comments did not include email addresses that appeared in the comments. Now, this text is included, as expected.

Fixed an issue where browser pop-ups were still leveraged in certain workflows where the user opened a record from a dashboard and then used an action button to create a related record. Now, browser pop-ups are not needed, as expected.

Fixed an issue where printing a chart from a dashboard sometimes included many unnecessary blank pages with the chart.

Fixed an issue where using a direct link to a record did not respect the current user's preferred interface. Now, the record opens in the appropriate interface based on the role of the current user.

Fixed an issue where dependent fields sometimes did not refresh their contents when the source field was updated.

Fixed an issue that sometimes prevented importing data into Question Description fields.

# Connected Services August 2026 Release

## Update multiple contracts at once with Ask AI

Building on the Contract Update feature recently introduced to Ask AI in Release 34, you can now ask Ask AI to update multiple contracts at once, even in a single request. For more information, visit [Using Ask AI](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/779518250).

## Easily configure Ask AI with the new Ask AI Setup page

Setting up Ask AI just got much easier with the addition of a new Ask AI Setup page. You can now navigate to **Setup > Ask AI Setup** to see the settings you already have configured, as well as any additional steps needed to use Ask AI.

For more information on Ask AI, and for detailed steps on how to use the new page, visit [Setting Up Ask AI](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/778960941).

## Updated models for Prompt Lab

For Agiloft-hosted KBs using the default Prompt Lab setup, the following models have been updated: 

- Azure OpenAI GPT3.5 has been replaced with OpenAI GPT-4.1 mini
- Azure OpenAI GPT4 has been replaced with OpenAI GPT-5 mini
- Claude 3 Haiku has been replaced with Claude 4.5 Haiku

## Bug Fixes

Several improvements have been made to contract intake experience with Ask AI, including:

- DateTime fields provide clearer format guidance, and display a user-friendly validation message when an invalid format is entered
- Currency fields or float fields can now be marked as conditionally required fields without causing errors
- Linked fields are no longer unexpectedly marked as required
- Better error messages and clearer messaging around limitations and unsupported contract types
- General user experience in contract intake workflows, such as confirming actions with "Yes" or "Sure" in text and a smoother path when changing to a new task

Several improvements have been made to the contract update workflow in Ask AI, including:

- Better indication of milestones and confirmation for completed updates
- Improved handling around relative date terms, such as "today," and improved mapping for Start Date values
- Tables are now recognized in both the singular and plural form
- Clearer Save button to prevent users navigating away prematurely
- Better validation of entries in required fields

Several improvements have been made to the general Ask AI platform, including:

- Better processing for queries with multiple search requests, specific contract IDs, date ranges such as "the next 60 days," and more
- Answers now include the documents sourced for that answer, with clickable links
- Improved recall for information from previous conversations
- Helpful milestone formatting, without duplicate milestones
- Lists or how-to steps included in responses are now consistently formatted with numbering and with proper spacing
- Higher accuracy in table data, especially for queries with a single table, and consistent display of radio buttons and checkboxes
- Fewer errors when sending documents to Astra
- Fewer issues where user requests occasionally failed to register
- Removing some extraneous information like excessive timestamp data

Fixed an issue with Publish actions where they sometimes failed to set or overwrite Linked, Choice, and Multi-Choice fields with AI-extracted metadata.

Fixed an issue where using the Publish action from a table other than AI Project Document sometimes created a new Attachment record instead of using the existing Attachment ID provided.

Fixed two issues with republishing, which sometimes failed to update the fields and sometimes created duplicate AI metadata records instead of updating the existing associated record.

# Agiloft Core Platform September 2026 Release

## Bug Fixes

Fixed an issue where linked fields that pointed to multiple tables did not offer partial matching on results from both tables, and instead offered matches only from one of the tables.

Fixed an issue that sometimes prevented proper display of HTML fields that contained bulleted lists.

Fixed an issue in document templates where related tables with empty rows sometimes caused errors.

Fixed an issue where standard licenses and floating licenses were not distinguished clearly in the Manage Licenses table. Now, they are shown as Standard Users and Standard (Floating) Users, respectively.

Fixed an issue that sometimes caused entity set exports to fail if they included Update actions referencing records that had been deleted.

Fixed an issue when creating new tables where the Date Created and Date Updated fields did not have default values set automatically.

Fixed an issue where localized grouping separators for numerical values sometimes reset to the default upon clicking into the field and then out of it.

Fixed an issue that sometimes caused linked field selections to appear blank until the record was saved.

# Connected Services September 2026 Release

## Bug Fixes

Fixed an issue where having your Agiloft session time out used to direct you to a Help page, if your KB did not have a custom logout URL configured. Now, you are instead directed to your KB's login page, so you can log back in if you need to.

Fixed an issue where importing multiple documents via legacy import sometimes caused the Document Analysis action to fail, if there was an issue with the AI model configured with the action. Now, if a model fails, the system uses the next healthy model by default, or returns a clear error message if no healthy models exist.

Fixed an issue in Agiloft CLM where templates still appeared in Prompt Lab after having their Status changed to Inactive. Now, only active templates are available in Prompt Lab, as expected.

# Agiloft Core Platform October 2026 Release

## Bug Fixes

Fixed an issue in document templates that sometimes prevented $field_from_other_table from properly evaluating contents from tables other than the Clause Library table.

Fixed an intermittent issue where using a link in a record to open another record in a modal window and then closing the modal caused the navigation bar options to become unresponsive.

Fixed an issue where running a Screen Run action sometimes caused the user to be unexpectedly logged out.

Fixed an issue with group permissions where choosing to copy a group's field permissions sometimes unexpectedly copied menu or record permissions as well.

Fixed an issue where OCR did not consistently set the OCR Language field, even when configured to set it automatically.

Fixed an issue where extracted clauses sometimes did not save the link to the contract ID.

Fixed an issue where end users who log in using a SAML SSO link, and then click a second SAML SSO link, are logged out of the first session. Now, both sessions operate concurrently, as expected.

Fixed an issue where upgrading or redeploying Astra entities orphaned any custom additions to the linked field sets or permissions. Now, these customizations are preserved.

Fixed an issue that allowed rules and hyperlinks to update records by ID without evaluating user permissions. Now, the system evaluates the permissions of the user triggering the rule or clicking the hyperlink before applying updates to a record this way.

# Connected Services October 2026 Release

## Customize terms for use in Ask AI

Instead of requiring all of your users to know the specific names of tables, fields, values, and other terminology in your system, you can program Ask AI and global search to recognize more general terms. For example, you can map "deal value" to the Contract Amount field. 

You can create three layers of semantic mappings: Business Term, User Language, and Terminology.

- Business Terms map to field names, such as the Contract Amount example above.
- User Language maps to field values, such as Active in regards to contract Status.
- Terminology allows you to identify synonyms that act as redirectors in your search, as opposed to being mapped directly to parts of your system.

For more information on creating semantics, visit [Setting Up Ask AI](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/778960941).

## Write additional clause data back to your KB from Astra

Previously, if a screen required the use of a fallback clause to pass a standard, only a Pass or Fail value would be written to the Screen Runs table. Now, the table indicates specifically whether a preferred or fallback clause was used.

## Bug Fixes

Fixed several issues in Ask AI:

- You can now successfully attach documents, or replace an existing document
- Clearer error messaging, specifically for permission-based failures and for contracts locked by other users
- Fixed HTTP 500 errors appearing after user confirmations, especially around Contract Type
- The same question is not answered in a consistent answer format, such as always in a table or in markdown
- Better visibility for reading markdown-rendered tables

Fixed an issue in Ask AI results where links to records were not clickable.

Fixed Ask AI handling of incomplete contract update requests, so that Ask AI now requests the missing information before moving forward, and handling of time-based language like "today".