# Aisera Product Release Notes - April 8, 2026

## Features

The following features have been added to the Aisera Gen AI Platform in this release.

### Interoperability with Automation Anywhere

If you use both Aisera Gen AI and Automation Anywhere A360 platforms, you can use your Aisera assistant to get RAG based answers grounded in customer data from the A360 platform.

You can upload documents to your Aisera tenant data source and then connect to it using the Model Connection object in Automation Anywhere A360.

Information about this feature is available in the Automation Anywhere A360 Documentation.

<div align="left"><figure><img src="https://2983236984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiZkLJr3EjXkd2tHYiQJP%2Fuploads%2Fhplm43dGYtIGB7VqmUfo%2Frn1.gif?alt=media&#x26;token=f6186ebe-ef74-4874-bf7f-a18b2a36caad" alt=""><figcaption></figcaption></figure></div>

Before you use this feature, set the Automation Anywhere Product Integration checkbox in the Feature Flag in your Aisera Tenant Configuration.

### Knowledge Generation

The following feature has been added to Knowledge Generation in this release.

#### AI Generated Documents Window Updates

Previously, the Content Generation Menu allowed you to access two different windows for Knowledge Generation from Tickets.

<figure><img src="https://2983236984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiZkLJr3EjXkd2tHYiQJP%2Fuploads%2F1Wst5IJgzVQr9ukPC3mN%2Frn2.gif?alt=media&#x26;token=87a4678e-3683-49bf-a88d-964635ec2535" alt=""><figcaption></figcaption></figure>

Now both the Individual Ticket generation and the Clustered Ticket generation are together on the **AI Generated Documents** (previously Knowledge Generation) window as separate tabs.

<figure><img src="https://2983236984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiZkLJr3EjXkd2tHYiQJP%2Fuploads%2Fox0na74eVFYMLPBrb1Rt%2Frn3.gif?alt=media&#x26;token=d3c888e0-d150-4665-a720-b77a50b1e0c9" alt=""><figcaption></figcaption></figure>

Choose **Content Generation > AI Generated Documents** to access the window that now includes 2 tabs in the upper-left corner - **Bulk** and **Single**.

<figure><img src="https://2983236984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiZkLJr3EjXkd2tHYiQJP%2Fuploads%2FrWsWhT9C5xZAPRwQui4i%2Frn4.gif?alt=media&#x26;token=58783564-5218-4dbf-b026-c5d260a56bc4" alt=""><figcaption></figcaption></figure>

The **Bulk** tab on the **AI Generated Documents** window displays the Knowledge Base Articles that were generated from **Bulk Tickets** to create information **Clusters**.&#x20;

<figure><img src="https://2983236984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiZkLJr3EjXkd2tHYiQJP%2Fuploads%2F7UeHhEfwfL2bUpyUXqeg%2Frn5.gif?alt=media&#x26;token=563ed918-c668-42b6-96c0-3d01a9ab0d35" alt=""><figcaption></figcaption></figure>

The **Single** tab on the **AI Generated Documents** window displays the Knowledge Base Articles that were generated from **Individual Tickets**.

**Delete & Regenerate Docs to Improve Quality**

The release introduces the ability to delete documents that are not helpful, allowing their associated tickets to be reconsidered in future job runs. You can now regenerate documents from the same tickets after adding new comments.

**Document Deletion Capabilities**

A new **Delete Document** option is now available in the Actions dropdown, in both the **Bulk** and **Single** tabs of the **AI Generated Documents** window. You can select one or multiple documents within a cluster and go to **Actions > Delete Document**.

<figure><img src="https://2983236984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiZkLJr3EjXkd2tHYiQJP%2Fuploads%2F6JiZywZzd7AqYVZlT1k6%2Frn6.gif?alt=media&#x26;token=39b9a789-8069-4dde-8f51-48f25c06285f" alt=""><figcaption></figcaption></figure>

A confirmation message appears: "Are you sure you want to delete the selected 1 document(s)?”

<figure><img src="https://2983236984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiZkLJr3EjXkd2tHYiQJP%2Fuploads%2FLsCyQnOJ3pmQH4ncLX5t%2Frn7.gif?alt=media&#x26;token=0a3f97bd-f05c-43f4-90a6-24b7e1fdf504" alt=""><figcaption></figcaption></figure>

Deleted documents are greyed out in the UI rather than removed, ensuring the **Data Processing Funnel** remains consistent with the original cluster count.&#x20;

If all documents within a cluster are deleted, the job is also deleted. The corresponding **Job Name** is automatically removed from the **Job Filter** dropdown.

<figure><img src="https://2983236984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiZkLJr3EjXkd2tHYiQJP%2Fuploads%2FkXEQCGXDp3WbIGPRzEQn%2Frn8.gif?alt=media&#x26;token=039bbb75-82d6-427a-9761-77e56f475b1f" alt=""><figcaption></figcaption></figure>

The corresponding **Job Name** is automatically removed from the **Job Filter** dropdown.&#x20;

For the documents deleted from Single tab of the AI Generated Document page then the document will be removed instead of greyed out because document generation from a single ticket doesn’t use a processing funnel.

Greyed-out documents are non-clickable and non-actionable.

**Deleted Documents in the Similarity Page**&#x20;

When an AI-generated document is approved and committed, it becomes part of the **similarity check**. If a committed document is later deleted from the **AI Generated Documents** page, it will be removed from the similarity dropdown for any document it was previously matched with, and the similarity count will be updated accordingly.

If the deleted document was the only similar match, the similarity status will be updated from **Yes** to **No**.

## Issues Resolved in the Release

<table data-header-hidden><thead><tr><th valign="top"></th><th valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top"><strong>Aisera ID</strong></td><td valign="top"><strong>Product Area</strong></td><td valign="top"><strong>Summary</strong></td></tr><tr><td valign="top">4.8.2026.1</td><td valign="top">Conversation</td><td valign="top">User unable to get response for 1.0 App - Neural Search is Failing</td></tr><tr><td valign="top">4.8.2026.2</td><td valign="top">New request isn’t getting created in 2.0 apps for the follow up query after Fallback</td><td valign="top"></td></tr><tr><td valign="top">4.8.2026.3</td><td valign="top">Action executor service not registered with Routing Service</td><td valign="top"></td></tr><tr><td valign="top">4.8.2026.4</td><td valign="top">Deleting bot deletes tenant level index.</td><td valign="top"></td></tr><tr><td valign="top">4.8.2026.5</td><td valign="top">Run Tenant-Level RAG Indexing in batches</td><td valign="top"></td></tr><tr><td valign="top">4.8.2026.6</td><td valign="top">Remove Casual/Gibberish classifier from Conv Server</td><td valign="top"></td></tr><tr><td valign="top">4.8.2026.7</td><td valign="top">Workflows and Hyperflows</td><td valign="top">Excluded Domain Validation for HF &#x26; WF import</td></tr><tr><td valign="top">4.8.2026.8</td><td valign="top">WF Exp/Imp - Workflow Import Field Values Update</td><td valign="top"></td></tr><tr><td valign="top">4.8.2026.9</td><td valign="top">Enable HF testing for various LLM providers</td><td valign="top"></td></tr><tr><td valign="top">4.8.2026.10</td><td valign="top">Unable to import workflows: Upon flow import upload the imported file is saved to S3 before reading and processing the file</td><td valign="top"></td></tr><tr><td valign="top">4.8.2026.11</td><td valign="top">Unable to import workflows</td><td valign="top"></td></tr></tbody></table>

&#x20;

&#x20;

&#x20;

&#x20;