Bi-Weekly Product Release Notes - Oct 29, 2025

Features

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

Channels

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

New What’s App Channel

The Aisera Gen AI platform now supports adding a What’sApp channel to your application/bot.

To add the WhatsApp channel to your Tenant:

1. Navigate to Settings > Channels.

2. Click the + New Channel button in the upper-right corner of the window.

3. Start to type WhatsApp in the Search field, and you will see the WhatsApp icon.

1. Select the WhatsApp icon and choose Next.

Fill in the information for these required fields:

• Channel Name

• Phone number ID

• Access Token

• Phone number

• WhatsApp Business Account ID

• App ID

• End chat phrase

The WhatsApp Admin can collect this information for you using the WhatsApp API.

1. Click the OK button.

After the WhatsApp channel exists on your tenant, you can associate the WhatsApp channel with your applications/bot.

To associate a WhatsApp channel with your application/bot:

1. Navigate to Settings > AiseraGPT.

2. Choose the application/bot that you want to associate with the WhatsApp channel.

3. Double-click to open the application/bot to the AiseraGPT Details window.

4. Scroll down the window until you see the + Add Channel button.

1. Click the + Add Channel button.

2. Type part of your WhatsApp channel name into the Search field or choose from the list of channel names in your tenant that appear in a pull-down list.

3. Click OK.

The WhatsApp channel supports attachments and Live Agent connection.

Enhancements

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

Data Ingestion

The following enhancement has been added to Data Ingestion in this release.

Set Schedule with UNIX Cron Job Parameters

A cron expression is a string used to define a schedule for running tasks at specific times or intervals. It is commonly used in Unix-based systems for scheduling repetitive tasks. A typical cron expression consists of five fields (or six, if seconds are included), each representing a different unit of time:

1. Minute (0 - 59)

2. Hour (0 - 23)

3. Day of the month (1 - 31)

4. Month (1 - 12)

5. Day of the week (0 - 7, where both 0 and 7 represent Sunday)

For example, the cron expression 0 3 * * 2,4 is used to schedule a task to run at 03:00 AM on Tuesdays and Thursdays 1.

Cron expressions can be complex, especially when specifying multiple schedules or excluding specific dates.

To set a cron expression for a Data Ingestion Schedule:

1. Navigate to Settings > Data Source.

2. Open an existing data source.

3. Choose the pencil icon in the upper-right corner to edit the data source.

4. Make sure you're in the Configuration tab of the Edit Data Source window.

1. Select Custom from the pull-down list of items for the Schedule field.

2. Using UNIX Cron Job syntax, as described above, set the schedule to the exact days and times you want the job to run. The screenshot example matches the Cron Job explanation example.

Knowledge Generation

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

Search for Jobs with Knowledge Generation in the Name

In the Name pull-down list at the top left of the Jobs window, you can now search for jobs that have Knowledge Generation in the name.

Connectors

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

Azure AD Can Use Select and Expand in Queries

The Azure AD Connector now supports arbitrary query parameters, specifically the select and expand parameters, for API calls within the Custom Query field of the Data Source Configuration window in the Aisera Admin UI.

This allows you to define arbitrary query parameters for each content type (such as User or UserProfile) separately.

Example:

{
  "User": {
    "$select": "id, name, country",
    "$expand": "transitiveMemberOf"
  },
  "UserProfile": {
    "$select": "id, name, country",
    "$expand": "transitiveMemberOf"
  }
}

Arbitrary query parameters are values that are not explicitly defined or expected in the API's specification. These parameters provide you with greater flexibility and control over the data retrieved from Azure AD. Previously, the Azure AD Connector used an $expand parameter that was hardcoded to transitiveMemberOf.

With this enhancement, you can now specify your own values for both $expand and $select, to enable more tailored and efficient data synchronization.

Changes to Hyperflow Permissions

In previous releases, Hyperflows were managed (both Read and Write) using the AI Workflow Write permission.

After this enhancement, Hyperflows are only visible to users who have Hyperflow Read permission.

• Users with Read permission can view Hyperflows, but cannot create, edit, or delete them.

• Users with Hyperflow Write permission can create, edit, and delete Hyperflows.

Hyperflows include a parameter to add Functions (Action, API, and Workflow).

• Data for Actions and APIs are only visible if you have Integration Read permission.

• Data for Workflows are only visible if you have Workflow Read permission. Therefore, you cannot add new functions if you don’t have these respective permissions.

Issues Resolved in the Release

Aisera ID	Product Area	Summary
10.29.2025.1	Connectors	ServiceNow Connector: Process custom fields from standard Templates for KB Learning
10.29.2025.2		Confluence Connector: Image Failures (icons, emojis) due to malformed download url
10.29.2025.4	Workflows and Hyperflows	"Add a comment" button replaces the description instead of adding a comment
10.29.2025.5	Azure EU	Custom table query returns only 100 records
10.29.2025.6	Conversations	Form Node data not displaying in conversation history
10.29.2025.7		File upload functionality is not working in the SNOW live agent chat from Slack
10.29.2025.8		RelayState Too Large - Causing Co-pilot SSO Failures
10.29.2025.9		Issue delivering campaigns using MS Teams channel
10.29.2025.10	Live Agent	Live Agent language changes mid-conversation
10.29.2025.11		Issue with bot response in carousel language translation
10.29.2025.12		Access Attribute Extraction Job is not removing attributes when tags are no longer applied
10.29.2025.13		Language detection issues with Prompts
10.29.2025.14	AWS	Issue with ACL Service catalog
10.29.2025.15		2.0 TC responses not showing consistently
10.29.2025.16	Agent Assist	Low field prediction for assignment group
10.29.2025.17	Analytics/Test Suite	Discrepancy with Number of requests showing for a subflow in Workflow analytics
10.29.2025.18	Ontology	Ontology Generation Job not working due to dependency issue