Bi-Weekly Product Release Notes - Aug 22, 2025
Features
The following features have been added to the Aisera Gen AI Platform in this release.
Universal Bot
The following feature has been added to the Universal Bot in this release.
List of Languages to Detect or Translate
You can now provide a list of allowed languages that your Universal Bot can detect or translate, as well as providing a fallback language.
To set allowed languages:
Navigate to Settings >AiseraGPT.
Choose your existing application/bot.
Click the pencil icon to edit the AiseraGPT Details window.
Select the Advanced tab on the Edit AiseraGPT window.
Check the Multi-language Handling checkbox.
This allows you to fill in the other language parameters:
Default Language: Choose a default language. Support all 85+ languages: Check if you want to support all 85 languages in the Supported Language List. Supported Language List: Choose languages from the list to restrict your application/bot to only those languages.
If a user Request is detected to be in a language other than the allowed list, your Universal Bot will fall back to its default language (in this case English).
Integrations
The following feature has been added to the Integrations/Connectors feature in this release.
Generic Integration Supports Body Parameters
When you choose the Generic integration option to connect your data source with your Aisera tenant instance, you can now successfully connect to APIs that require additional form parameters during authentication.
To add an integration that requires API body parameters:
Navigate to Settings > Integrations in the Aisera Admin UI.
Choose the + New Integration button.
Select the Generic integration option.
The optional Body Parameters text field is visible in the Generic API Integration OAuthPassword configuration form.
Add a string to the Body Parameters field in key=value&key=value JSON file format.
Data Source Ingestion
The following feature has been added to the Data Source Ingestion feature in this release.
Ingest PDFs with the Docling Document Converter
The Aisera Gen AI Platform now uses the Docling tool to convert PDF documents to HTML behind-the-scenes.
To use the Docling Document Converter in your file ingestion:
Navigate to Data Sources.
Choose the + New Data Source button.
Select File Data from the Data Source options.
Click Next.
Name your Data Source.
Choose Knowledge Base as the Data Type.
Select Uploaded Files or Cloud Files.
Browse for a PDF file to upload.
Choose On Demand for the Schedule.
Choose Next.
Add a Template or skip the Template window and click Next.
Use the default options and check Document Converter (near the middle of the window).
There are 3 options below the Document Converter checkbox that you can select if you’re using the Document Converter option.
Accurate Table Parse: Use this option if you require exact parsing. The Docling Converter includes two modes for parsing tables - Fast and Accurate. Fast is the default. If you only need accurate parsing for specific PDFs, enter the PDF names (without extensions, comma-separated) in the PDF Names input box.
Bypass Cache: Smart caching avoids redundant processing by skipping PDFs whose content hasn't changed, significantly reducing load. Use this option if you don’t want to use smart caching.
Force OCR: Optical Character Recognition (OCR) is automatically enabled for PDFs containing images. To apply OCR to all PDFs, check the Force OCR option. For selective OCR processing, enter the PDF names (without extensions, comma-separated) in the provided input box.
Click OK to start the ingestion job.
Knowledge Base Article Generation
The following feature has been added to the Knowledge Base Article Generation feature in this release.
Set Recurring Knowledge Generation Jobs
You can now set a schedule for recurring Knowledge Generations Jobs.
Previously, you could set the knowledge generation job to run when the number of tickets reaches a specified threshold (because more tickets create more accurate knowledge generation).
Now you can set a recurring schedule to ignore the threshold and run the knowledge generation job periodically (regardless of the number of tickets in your system). This allows you to review the results at specific times, instead of at random intervals.
To set the recurring schedule:
Navigate to Settings >Content Generation >Knowledge Generation.
Choose the Actions button in the upper-right corner of the Knowledge Generation window.
Select Set Recurring Schedule.
Pick Monthly, Bi-Monthly, or Quarterly as the recurring values.
Choose a Start Date from the Calendar option.
Set the Ticket Threshold option to Yes or No.
Set the Conditions, Field Assignments, and Pre-Generation Configuration.
Click the OK button.
Schedule Configuration Details
Frequency Selection: You can select a recurrence frequency (Monthly, Bi-Monthly, Quarterly).
Start Date: Specify the Start Date in UTC. The Start Date determines when the recurring KB generation job will begin. All past dates are disabled and you can choose future dates.
Ticket Threshold Setting: To ensure high-quality clustering, a minimum of ~40,000 tickets is recommended. Lower ticket volumes result in looser clusters with broader topics and less meaningful document generation. The Aisera Gen AI platform allows you to generate documents with minimal tickets because it is not realistic that every customer has 40K tickets for every configuration.
If Enabled:
On the scheduled job run date, the system checks the total ticket count.
If the ticket count is below the threshold, the knowledge base will not be generated. You can still view the job details in the job filter dropdown. Upon selecting it, the user will see a message:
The KB generation did not run because the defined ticket threshold is 50K, while only 30K tickets were available at the time of execution.
If Disabled:
The system will ignore the ticket count threshold and process all available tickets on the job trigger date.
All other options — such as Ticket Conditions, Knowledge Field Mapping, and Pre-Generation Configuration — will remain the same as those available for a regular job run.
After you set the recurring option and return to the Set Recurring Schedule window, the Job will trigger on… field will be displayed below the Start Date (UTC). This value is dynamic. For example, if the schedule is monthly and the job ran yesterday, the Job will trigger on field displays the next run date.
Wait After Setting Schedule or Job Configuration
Setting Knowledge Generation schedules at the Bot level, instead of at the tenant level gives you the ability to create different generation schedules for different bots.
However, this change means that you need to wait 10 minutes after you set up the Job Configuration, so the Directed Acrylic Graph (DAG) that gets created by the configuration can be created and associated with your bot.
After you’ve waited for the DAG to get created, you can click the Generate Knowledge button to begin the Knowledge Generation Job.
Enhancements
The following enhancements have been added to the Aisera Gen AI Platform in this release.
Workflow Debugging
The following enhancement has been added to the Workflow Debugging feature in this release.
Debug Information with Text Filter
You can now verify which workflows are triggered and inspect variable extraction and execution details when using AI Lens while running Workflows.
To use the text filter: 1. Navigate to the bot you want to test.
2. Choose AI Lens from the left menu in the Aisera Admin UI.
3. Ask the bot a question.
4. Choose the Show More link to see the flowDebugInfo and flowDebugInfo2 methods as they are running.
Notifications
The following enhancement has been added to the Notifications feature in this release.
Notification to Zoom Users
Aisera now supports sending Campaigns and/or Notifications to any Zoom user in your organization who has access to your AI agent. More specifically, this release extends support to users who’ve been given access, but have never previously interacted with your AI agent.
Last updated
Was this helpful?