Aisera Product Release Notes - Mar 11, 2026

Features

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

Applications/Bots

The following feature has been added to Applications/Bots in this release.

AI Ops Terminology Updated

In previous releases, groups of serious tickets could be categorized as Major Incidents. The term Major Incidents has been updated in this release to the more specific Potential Issues.

The change will only affect new AMIs going forward, with no plans to migrate or alter historical data more than 3 months old. Therefore, lists of Potential Issues (PIs) may contain some data that is still identified as AMIs.

Analytics and other data around Major Incidents will be tracked as Potential Issues as of this release.

Connectors

The following feature has been added to Connectors in this release.

Happy Fox Connector Added

This release includes integration and data source connections for Happy Fox software ticketing systems.

Adding a Happy Fox Tenant Integration

To add a Happy Fox integration to your tenant configuration:

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

2. Choose + New Integration.

3. Start to type, Happy Fox into the Search field.

4. Select the Happy Fox icon.

5. Choose Next.

6. Name the Integration.

7. Add the endpoint for your Happy Fox application.

8. Add the authentication parameters.

Note that Happy Fox integration only supports Basic Authentication.

1. Type in the name of the Service User who will connect to Aisera from Happy Fox.

2. Add the password for the Service User.

3. Select OK.

Adding a Happy Fox Tenant Data Source

To add a Happy Fox Data Source to your tenant configuration:

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

2. Choose + Data Source.

3. Start to type, Happy Fox into the Search field.

1. Choose the Happy Fox icon.

2. Select Next.

3. Add a Name for your Data Source.

4. Select the AI Functions that you want your Data Source to perform.

5. Choose the Name of the Integration that you created in the previous steps.

6. Set the Schedule for data integration for this source. Choose On Demand, if you don’t know the schedule yet.

7. Set the Data Retrieval type as Incremental.

8. Set the Language that you want the data to be stored and returned in.

1. Select Next.

2. Fill in optional configuration parameters.

1. Add a Template for KB Article Generation or use the default.

1. Leave the default options for Ingestion Configuration.

1. Include Override Configurations and/or Data Transformation scripts.

1. Select OK.

Using the Happy Fox Connector in your Application/Bot

1. Navigate to Settings > AiseraGPT in your Aisera Admin UI.

2. Choose an existing application/bot.

3. In the application/bot Details window, select + Add Data Source.

1. Enter part of the name of the Happy Fox Data Source that you created previously.

2. Select the checkbox next to the name of your Data Source.

1. Choose OK.

1. Now the Happy Fox connection and integrated data can be used by your application/bot.

Roles and Permissions

The following feature has been added to Roles and Permissions in this release.

Ability to Restrict Editing to a Single Bot

If the Admin for your organization wants to restrict application/bot editing to a single bot for some users, you can now set up this scenario with a combination of Role and Access settings.

To restrict editing to a single bot for a user role:

1. Navigate to Settings > User Accounts.

2. Switch to the Role tab.

3. Select + New Role.

1. Enter a Role Name and Description for your New Role.

2. Select Next.

3. Keep selecting Next until you reach the window with the AiseraGPT option.

1. Select None for the AiseraGPT option. This will disable the AiseraGPT menu for users with this role. This is a tenant-level permission.

2. Assign a user to this role.

To over-ride the Role for a Specific Bot:

1. Navigate to Settings > AiseraGPT as an Administrator and choose an application/bot.

2. Open the application/bot Details window.

3. Scroll down to the bottom of the window, to the Access Attributes section.

4. Select + Assign Access Attributes.

5. Choose roles from the left pull-down menu.

1. Select the checkbox next to the name of your custom role that restricts access.

2. Choose Read/Write or Read, depending on the privileges that you want the user to have for this application/bot. Now you can see the role over-ride at the bottom of the application/bot Details window.

Enhancements

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

Connectors

The following enhancements have been made to Connectors in this release.

Freshworks Supports OAuth Authentication

In previous releases, the Freshworks connector only supported token authentication. It has been enhanced to support OAuth with this release.

Workflows and Hyperflows

The following enhancements have been made to Workflows and Hyperflows in this release.

Enhanced Documentation for Workflow Actions

The Aisera AI Workflow Studio allows you to create workflows that trigger actions by adding an Action Node to the flow when you drag it onto the AI Workflow Studio Canvas.

This release includes information about the following Action Node options:

• Execute REST Call Action

• Generate RAG Answer

• Send Notification

• Fetch LLM Chat Answer

• Create Ticket

• Close Ticket

• Get Ticket Details

• List Tickets

• Reopen Ticket

• Update Ticket Action

• Add Attachment Action

• Add Ticket Comment

Equivalent Workflow and Hyperflow Action Parameters

Some Actions for Workflows do not include the same configuration parameters when used in a Hyperflow. As a result, you may see differences between how an Action appears in a Workflow versus a Hyperflow.

The Actions listed below are the first set that have been synchronized, so that you will now see the same parameters and tooltips when adding Actions in either Workflows or Hyperflows. The Actions listed in this section are not the only ones that can be used as Hyperflow functions/tools.

• ExecuteRestCallAction

• FetchLLMChatAnswerV2

• SendNotification

• GenerateRagAnswer

• AddAttachmentAction

• Add Ticket Comment

• Close a Ticket

• Create Ticket Action

• Get Ticket Detail

• List Tickets

• Re-open a Ticket

• Update Ticket Action

For descriptions of how to add an Action to a Hyperflow, see Create a Hyperflow and review the Action Parameters when you get to Step 7.

Workflows Validate Registration Before Deletion

Both Tenant and Application workflows are validated before a workflow can be deleted.

Tenant-Level Scope

If you attempt to delete a registered, tenant-level Workflow you will receive the following message in the Aisera Admin UI: This Workflow cannot be deleted because it is currently registered in one or more applications. Please remove it from Registered Flows before attempting deletion.

Application-Level Scope

If you attempt to delete a registered, application-level Workflow you will receive the following message on the UI: This Workflow cannot be deleted because it is currently registered in the application. Please remove it from the Registered Flows before attempting deletion.

Hyperflows Validate Registration Before Deletion

If you attempt to delete a registered Hyperflow (Hyperflow associated with a specific application/bot) you will receive the following message in the Aisera Admin UI: This Hyperflow cannot be deleted because it is currently registered in the application. Please remove it from the Registered Flows before attempting deletion.

Issues Resolved in the Release

Aisera ID	Product Area	Summary
3.11.2026.1	Analytics/Test	App Import Job Failure during checksum computation
3.11.2026.2	Conversation	RAG debug info for GenerateRagAnswer exposes flow search results
3.11.2026.3	In SNOW Live agent communication, when text is present after link, Link and text together are hyperlinked
3.11.2026.4	After deflection in 2.0, resolution status is not marked as ASSISTED
3.11.2026.5	Deflection doesn't work for create ticket flow in 2.0
3.11.2026.6	Investigate copilot breaking on specific template workflow
3.11.2026.7	Platform	CSV Export: Query Takes a Long Time to Execute
3.11.2026.8	Copilot file upload is not working with Minio
3.11.2026.9	Flows	Requests are being marked with Blank resolution status even though the fulfillment is provided by the bot
3.11.2026.10	Unable to update a flow name in one bot to match the name of an existing flow in a different bot.
3.11.2026.11	Connectors	OAuth option is not visible for Fresh integration
3.11.2026.12	When we change the href link toggle, all data sources are updated
3.11.2026.13	KB Gen	When a document is deleted from SOR -> Knowledge page, user getting redirected to cluster page
3.11.2026.14	Downloaded csv should not contain records that are deleted
3.11.2026.15	Ontology	Ontology Job Failure due to library import error
3.11.2026.16	Testing	AI Lens Requests Counting as Event Studio Requests