Aisera Product Release Notes - Feb 23, 2026

Features

The following feature has been added to the Aisera Gen AI Platform in this release.

Application Details

The following enhancements have been added to Application Details in this release.

Links to Registered Flows

Registered Workflows and Hyperflows listed on the AiseraGPT Details page now link to their respective flows. This change allows for easy access to viewing and editing flows registered to a specific application/bot.

To view this change:

1. In the Aisera Admin UI, navigate to Settings > Aisera GPT

2. Select the desired application/bot.

3. Under Registered Flows on the Aisera GPT Details page, click a Workflow or Hyperflow to navigate directly to the Workflow Details or Hyperflow Details page.

Ingestion and Connectors

The following features have been added to Ingestion and Connectors in this release.

Delete Generated Knowledge Documents from Document Details Page

Previously, generated documents could be deleted from the Knowledge Cluster and Single Document pages. This release extends the delete capability to the generated document’s Details page. Deleting a generated document releases the associated representative ticket, allowing it to be reused in future knowledge generation runs.

To delete a Knowledge Document from the Document Details Page:

1. In the Aisera Admin UI Navigate to either Content Generation > Knowledge Generation Individual Ticket or Knowledge Generation Clustered Tickets.

2. Select the desired document

3. In the top right corner of the Knowledge Document Details page, click the Delete icon.

Links in Responses are now Toggleable

This feature adds a configuration that allows you to control whether or not links are displayed in bot responses for specific data sources.

To toggle this feature:

1. Navigate to Settings > Aisera GPT in the Aisera Admin UI.

2. Select the application/bot you would like to configure.

3. In the Aisera GPT Details window, under Data Sources, locate the Data Source you would like to configure.

4. To allow links from data sources to appear in application/bot responses, toggle the button under HREF Links to the right side.

Transformation Scripts Support for File Data Source

You can now add transformation scripts when you use the File Data Data Source. File Data is used as a data source for crawling or uploading documents.

To add a transformation script:

1. Navigate to Data Sources under the Settings tab in the Aisera Admin UI.

2. Select the File Data Data Source you would like to edit, or create a new File Data Data Source.

3. Select the Pencil icon in the top right corner of the Data Source Details screen to begin editing the data source.

4. Under the Configuration tab of the Edit Data Source window, insert the transformation script into the Transformation Script field.

5. Select OK to save the changes.

File Status Tracking APIs

Two new public API endpoints are introduced in this release, providing visibility into file ingestion status for webhook-based uploads. These endpoints allow you to troubleshoot and track the document upload and processing phases on the Aisera Gen AI Platform.

The existing /files endpoint now returns a Tracking ID in successful responses. This ID is used to monitor the status of your file’s processing.

New Endpoint 1: Get File Status by Tracking ID

This new endpoint gets the status of a specific file using the provided tracking ID.

GET /api/v2/file-status/tenant/{tenantId}?trackingId={trackingId}

This endpoint will return the file metadata, processing status, processing history, and error messages, if any.

New Endpoint 2: List All File Statuses by Data Source

This new endpoint returns the status of all file uploads for a specific data source, when you provide the data Source ID.

GET /api/v2/file-status/tenant/{tenantId}/data-source/{dataSourceId}

This endpoint will return a list of all files uploaded to the specified data source, their statuses, and error information if any.

To locate the Data Source ID:

1. In the Aisera Admin UI, navigate to Settings > Data Sources.

2. Select the data source you would like to query.

3. The ID will be displayed on the right side of the Data Source Details page.

Data Source Configuration Safety Features

Proactive warnings have been added to the Aisera Admin UI to prevent unintentional data loss when modifying Data Source configurations. These warnings are displayed if you are about to modify a data source configuration that could lead to mass data loss or the deletion of previously ingested documents.

Specific configuration changes that could lead to data loss include:

- Changing the date range for data ingestion

- Modifying custom queries

- Switching a data source from Incremental to Fixed Date Range

Upon modification of these configurations, a warning is displayed to notify you that changing the configuration could lead to data loss. After discarding changes, you receive a suggestion to create a new data source with different configurations or separate data sets.

Conversation

The following features have been added to Conversation in this release.

Channel Metadata Filters

You may now specify metadata tags as key-value pairs during channel configuration for use in RAG searches. When a RAG search is invoked, the metadata tags are appended to the end of the user’s query, allowing different channels to return tailored results while still utilizing the same bot.

To configure Metadata Filters:

1. Navigate to Settings > Channels in the Aisera Admin UI.

2. Select the desired channel or create a new channel.

3. On the Channel Details page, select the pencil icon in the top right corner to begin editing the channel.

4. Select Metadata Filters in the Edit Channel window.

5. Click + Add Metadata Filter to add a blank metadata filter.

6. Input metadata filters and select OK to save changes to the channel.

Enhancements

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

AI Ops

The following enhancements have been added to AI Ops in this release.

Aisera Major Incidents Renamed to Potential Issues

To provide a more accurate reflection of incident severity, all references to Aisera Major Incidents (AMI) within the Aisera Gen AI Platform have been renamed to Potential Issues (PI). This change ensures that high-volume system noise is not mischaracterized as a confirmed critical failure.

Conversations

The following enhancements have been added to Conversations in this release.

Newlines in Webchat

If you’re using the Webchat channel for your application/bot, you can now use Shift + Enter to add new lines to your messages in the Aisera Webchat bot.

This functionality prevents users from prematurely sending messages before they are complete.

Issues Resolved in the Release

Aisera ID	Product Area	Summary
2.19.2026.1	Analytics/Test Suite	CSV download is a Write permission
2.19.2026.2		AI Lens requests counting as Event Studio requests
2.19.2026.3		Requests with a service catalog response are displaying as blank in Test suite
2.19.2026.4		Intentless applications show flows in the request field.
2.19.2026.5	Ingestion & Connectors	SharePoint connector only ingesting the last site provided when multiple sites are provided to the Data Source Configuration
2.19.2026.6	Conversational AI	Links in KB answers are displayed as broken images rather than links.
2.19.2026.7		Context Disambiguation Service inconsistently triggers.
2.19.2026.8		Slot-filling resulting in null slot values
2.19.2026.9		Registered Hyperflows not triggering
2.19.2026.10	KB Gen	Similar Documents page does not open when clicking “Yes” on the Similar Documents option in the knowledge Generation page.
2.19.2026.11	Admin UI	Email ID is masked for Administrator with custom roles
2.19.2026.12		Bot repeats disambiguation phrases after user clarification in requests page.
2.19.2026.13		Tenant level Role Based Access Controls (RBACs) are being overwritten by Application level RBACs
2.19.2026.14	Conversation	Public Search will return not valid if any of the results return a validation error
2.19.2026.15		Co-Pilot/Webchat SSO Authentication sign in fails with internal server error