# Aisera Product Release Notes - May 2026
Expected Release Date: May 26, 2026
## Documentation
As of this release, the Aisera Release Schedule has moved to a Monthly and Monday GA cadence.
The expected release dates for the next 3 releases are:
Monday, June 15th, 2026
Monday, July 13th, 2026
Monday, August 10, 2026
However, these releases will be implemented in a staggered schedule, so ask your Aisera Team or Customer Support for the exact schedule for your implementation. The release dates above are subject to change, but your customer team will let you know about changes in advance.
#### No Pre-Release Notes
Future releases will not include Pre-Release Versions of the Release Notes, to conform with Automation Anywhere documentation policies.
#### Availability
The Aisera Product Release Notes will continue to be available on both the [Aisera Product Documentation Portal ](https://docs.aisera.com)(bookmark these) and the [Aisera Customer Support Portal](https://support.aisera.com).
## Features
The following features have been added to the Aisera Gen AI Platform in this release.
### Copilot
The following feature has been added to **Copilot** in this release.
#### AI Lens Now Available for Copilot
The AI Lens testing environment used to be only available for Webchat channels. Now applications/bots with a Copilot channel attached correctly default to Copilot mode in AI Lens and applications without a Copilot channel correctly default to Webchat mode.
#### AI Workflow Studio Now Available for Copilot
The AI Workflow Studio workflow-building feature used to be only available for Webchat channels. Now applications/bots with a Copilot channel attached correctly default to the Copilot mode in the AI Workflow Studio, and apps without a Copilot channel correctly default to the Webchat mode.
### Knowledge Generation
The following feature has been added to **Knowledge Generation** in this release.
#### Addition of Details Side Panel
The **Knowledge Document** **Details** page now includes a right-side panel with a **Details**section that links to specifics for the specific document.
The **Details** section displays the following fields (these are the same as those in the **Similar Documents** page):
* **Data Source**
* **AI Generated Document**
* **Total tickets (total tickets from all AI suggested documents)**
* **Last Updated Date** (document update date)
* **Created On** (date crawled from external source)
When any of AI generated document is unlinked or deleted, the total number of tickets is adjusted as per the active generated documents.
### AI Workflow Studio
The following feature has been added to **AI Workflow Studio** in this release.
#### New Secure Field for User Input Node
This release includes a new field called **Secure Field** in the **User Input Node** that allows you to register a secure variable for your workflow execution.
#### Ability to Search Workflow/Hyperflow Registries
When a workflow or hyperflow is associated with an application/bot, it is added to the Registry for that application/bot.With this release, a search field has been added at the top of the Workflows / Hyperflow registry page, so you can search for associated workflows and hyperflows by name.
#### Workflow Export/Import Includes Sub-Flows
The Workflow Export/Import feature now allows you to include sub-flows within your export/import. Note that after importing, you must publish each sub-flow before publishing the parent flow.
### Live Agent
The following feature has been added to **Live Agent** in this release.
#### Ability to Disable Bot Typing
Customers using Live Agent integration sometimes experience API rate limiting due to a high volume of typing from the application/bot. Therefore, some customers have requested the ability to enable or disable the typing indicator API calls for specific Live Agent integrations via the Live Agent Configuration on the Aisera Application/Bot Details page.
**To disable typing input while using the Live Agent feature:**
1. Navigate to **Settings > AiseraGPT**.
2. Choose the application/bot you want to modify.
3. Select the **pencil icon** in the upper right corner.
4. Scroll down to the **Live Agent** section.
5. Select the **Edit Live Agent** button.
6. Deselect the **Enable Typing Indicator** checkbox.
### Notification
The following feature has been added to **Notification**in this release.
#### Notification for Connection Status
All Aisera applications/bots now contain a visual indicator when the chat connection is lost and reconnecting. The reconnect message gives you an indication of why messages are not being sent/received and lets you know when the connection is restored.
If the reconnection fails, that message is also displayed.
## Enhancements
The following enhancements have been added to the Aisera Gen AI Platform in this release.
### Casual Conversation
The following enhancements have been added to **Casual Conversation** in this release.
#### Enhanced Small Talk and Toxicity Option
Choose the **Handle Small Talk and Toxicity** option when you’re creating an Aisera 2.0 Application/Bot to override the previous Casual Conversation feature with the updated Small Talk and Toxicity option.
This updated option incorporates the context of the conversation as well as the different search features available for each bot.
### Prompt Studio
The following enhancements have been added to **Prompt Studio** in this release.
#### Azure Open AI GPT-5.5 Added to Prompt Playground
If you have the appropriate Administrator permissions, you can now add and edit prompts for Azure Open AI GPT-5.5.
### Data Sources
The following enhancements have been added to **Data Sources** in this release.
#### File Data Connector Allows More Mime Types
Adding a File Data source to your Application/Bot allows you to upload files that your bot can use as a Fulfillment source.
This release includes all supported MIME types in the **Select Files** pull-down list within the **File Data** configuration.
#### New Permissions Checkboxes for SharePoint
SharePoint Connector Includes **Fetch Permissions** and **Fetch Site Page & Drive Items Permissions** checkboxes in the Data Source Configuration parameters.
* The **Fetch Permissions** checkbox is unchecked by default.
* The **Fetch Site Page & Drive Items Permissions** checkbox allows you to enable/disable ingestion of permission metadata for Site Pages and Drive Items (these include group permissions and siteGroups permissions).The permission metadata ingested for SharePoint **Site Pages** and **Drive Items** allows you to:
* apply **ACL tagging** / controls
* map permissions into **TagKeys/TagValues** for downstream use cases
**NOTE:** When the Admin UI opens the Configuration of an old Sharepoint Data Source that does not have a key-value pair for the new field (fetchPermissions), the corresponding check box should be displayed as active (checked).
#### Restrictions Removed from Simplr Connection
The required fields for the Simplr connection are no longer required, and this connection has become a more generic connector that uses only the OAuthClientCredentials Auth type.
Therefore, you will see the following changes in the Aisera Admin UI:
* In the integration section, the OAuthClientCredentials Auth type has been added another authorization types have been removed.
* In the Data Source Configuration, the following fields are no longer mandatory:
* Instance URL
* Search Term
* Size
#### Jira Service Desk Connection
In previous releases, if the Aisera Admin UI was unable to fetch the chosen Project, the data source addition was blocked.
Now if the Admin UI cannot fetch the Project, you can type it in manually, and the creation wizard will not be blocked.
### Unified Language Support
With this release, there are new parameters that determine the language in the conversation of the Webchat and AI Chat applications/bots.
Currently, when you open an application/bot, Webchat or AI Chat, the bot always starts the conversation in English, or it will be in the bot’s default language, regardless of the language setting of the user’s browser.
For instance, if a your browser is set to Spanish, the bot will still start the conversation in English.
Now you can set the application/bot to match the language set in the bot user’s browser.
**To set Auto Detection:**
1. Navigate to Settings > AiseraGPT.
2. Choose the application/bot that you want to modify.
3. Select the pencil icon to edit the application/bot.
4. On the Details page, scroll down the page to the View Conversations link.
5. Select the link.
6. Modify the initial conversation messages to create or choose some initial messages in the languages your bot will support.
7. Go back to the application/bot Details page and scroll to the Channels section.
8. Select the Webchat or AI Chat channel.
9. On the Edit Channel window, select the Use Browser Language checkbox.
#### Live Language Assignment
If the user has not logged into the application/bot before, their user profile in the Aisera Gen AI platform is created to with the default language they have specified in their browser.
#### Localization of Error Messages
Error messages and other UI content will appear in the same language as the Webchat or AI Chat conversation.
## Issues Resolved in the Release
| **Aisera ID** | **Product Area** | **Summary** |
| ---------------- | ---------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **5.18.2026.1** | **Workflows and Hyperflows** | Duplicate Names Detected for Workflow Imports Upon **Import**: Detect duplicate flow name, allow the import, update the target Workflow by adding the exported version on top of its existing version history. |
| **5.18.2026.2** | | Workflows added in Draft Mode In the previous release, a Workflow configured by the builder was imported in Published Status. Prerequisites for Workflow export/import:
- In 5/18 it is imported in Draft status.The source and target tenants/environments must be on the same deployment level across all components. Any differences or inconsistencies between the environments may cause the feature to malfunction.
- As the 5/18 release includes updates to both export and import functionalities, it is advised to re-export the Workflows and then import them to prevent potential errors or issues.
|
| **5.18.2026.3** | | Admin has the ability to Edit the flow after import and before publishing it so that they can review and publish for any changes or actions that were not brought over correctly from other tenants or environments. |
| **5.18.2026.4** | | Mask sensitive input variables in debug nodes |
| **5.18.2026.5** | | Handle sensitive variables in Subflow, HTTP, Parallel node execution |
| **5.18.2026.6** | | Mask sensitive data in action executions table |
| **5.18.2026.7** | | Multiple integrations that need update after Hyperflow import cross tenant or cluster are not displayed on Import job error page |
| **5.18.2026.8** | | Hyperflow that has pending Actions to be handled is not marked as Draft after import |
| **5.18.2026.9** | | Support 'Laptop Hardware Troubleshooting' Hyperflow |
| **5.18.2026.10** | | HyperFlowDebugInfo contains false modelInfo data in case of llm-gw |
| **5.18.2026.11** | | Export should include all HF versions |
| **5.18.2026.12** | **UI** | Enable .xls/.xlsx Support and Implement Custom Sheet Selection |
| **5.18.2026.13** | **Conversations** | helpful and not helpful flag to help AI suggested content |
| **5.18.2026.14** | **KBA Generation** | Bring Total tickets in UI and it should be dynamic upon delete and consistent with AI suggested document count |
| **5.18.2026.15** | | Remove the condition of not showing the first section if no content exist |
| **5.18.2026.16** | | Clicking on unlink should show the window that has a feedback option |
| **5.18.2026.17** | | Pre-import step didn’t detect any integration or data source mapping, however, import step failed with warning that data source needs mapping |
| **5.18.2026.18** | | The campaign metrics does not consider the buttons within the message node |
| **5.18.2026.19** | | Add eCharts download feature like High Charts |
| **5.18.2026.20** | | Add Data Test ID for Automation Testing |
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.aisera.com/product-release-notes/2026/aisera-product-release-notes-may-2026.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.