> For the complete documentation index, see [llms.txt](https://docs.aisera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aisera.com/product-release-notes/2026/aisera-product-release-notes-june-16-2026.md).

# Aisera Product Release Notes - June 16, 2026

## Conversational AI <a href="#conversational-ai" id="conversational-ai"></a>

### What's New <a href="#whats-new.3" id="whats-new.3"></a>

#### **Contextual Information for Fallback Answers in ConvAI 2.0 Applications/Bots**

The ConvAI 2.0 version of Aisera application/bots now provide intelligent, context-aware fallback responses when the requested information cannot be retrieved.

Instead of returning a generic fallback message, the application/bot analyzes the user's intent and responds with a more helpful explanation based on the situation:

* **No answer available**
* **Access-restricted information**
* **Configurable response format**

This enhancement improves transparency, reduces user confusion, and ensures users receive the most relevant guidance available, even when a direct answer cannot be provided.

**To enable contextual information for ConvAI 2.0 fallback messages:**

1. Navigate to **Settings > AiseraGPT** in the Aisera Admin UI.
2. Verify that your application/bot is set to use **Conversational AI v2.0**.
3. Note that intents for Conversational AI 2.0 applications are detected using the Title or Description field in a Workflow or Hyperflow.
4. Select the application/bot that includes the messaging that you want to modify.
5. Choose the **Advanced** tab on the application/bot **Edit AiseraGPT** window.

<div align="left"><figure><img src="/files/XbSlgGzowmLvOrsUwbJ5" alt="" width="501"><figcaption></figcaption></figure></div>

4. Select the checkbox next to the **Add contextual information fallback answers** option.

[Creating Intentless Workflows](https://docs.aisera.com/aisera-platform/ai-automation-optimize-flow/ai-workflow-studio/building-workflows/creating-intentless-workflows#flow-titles-descriptions)

## Flows (Workflows and Hyperflows) <a href="#flows" id="flows"></a>

### What's New <a href="#whats-new.4" id="whats-new.4"></a>

#### **Consolidated Hyperflow configuration management**

Hyperflow tenant-level settings now live in one place: **Settings > Configuration > Hyperflow**. Previously, these settings were spread across multiple tabs, which made administration harder.

[Tenant Level Hyperflow Configurations](/aisera-platform/tenant-setup/aisera-platform-configuration/tenant-configuration-settings/hyperflows.md)

#### **Tenant-level model configuration for Hyperflows**

You can now set default LLMs for Hyperflow execution and testing at the tenant level. This centralizes model selection across the organization while still allowing app-specific overrides when needed.

[Hyperflow Execution Model](/aisera-platform/tenant-setup/aisera-platform-configuration/tenant-configuration-settings/hyperflows.md#hyperflow-execution-model)

#### App-level model configuration for Hyperflows

You can now set the LLM used for Hyperflow execution and testing at the application level. This give you flexibility to optimize performance by selecting the most appropriate model for each bot or application.

This configuration is located at the top of the **AI Automation > Hyperflows** page. The configuration will only be visible if you have disabled the **Enable Hyperflow V1** configuration. This configuration can be found under **Settings > Configurations > Hyperflows**

#### **Bulk flow registry operations**

You can now activate, deactivate, or delete multiple Workflows or Hyperflows simultaneously from an application. When activating or deactivating, the available bulk action updates based on the current selection all active flows show a deactivate option, all inactive flows show an activate option. Mixed-status selections do not support bulk activation or deactivation.

### What's Changed <a href="#whats-changed.4" id="whats-changed.4"></a>

#### **Enhanced workflow function export/import alignment**

To ensure consistency with standard Workflow export/import behavior, Workflows used as functions (tools) in Hyperflows now export their last published version.

When importing to a target Application or Tenant, if a Workflow with the same name already exists, the exported version is imported as a Draft on top of the existing version history, preserving all previous versions while safely adding the new functionality.

[Export and Import Workflows](/aisera-platform/ai-automation-optimize-flow/ai-workflow-studio/export-and-import-workflows.md)

#### **Enhanced validation for application-level workflow publishing**

The system now validates that required metadata, description and category, is complete before allowing imported workflows to be published in 2.0 applications.

Description enables conversational triggering and category is required for organization. Workflows missing either field are block from publishing.

Validation applies only to application-level workflows imported from 1.0 applications to 2.0 applications.

#### **HTTP node variable selection**

HTTP node functionality has been aligned with other nodes. Headers and Body configuration now supports easy selection from existing variables, resulting in a faster and more intuitive node building process.

#### **OAuth variable handling in flow execution**

OAuth user input variables are now securely processed as sensitive data, remaining encrypted during execution and masked in execution logs, channel messages, and debug information.

### Fixes <a href="#fixes.4" id="fixes.4"></a>

Corrected Workflow import behavior to ensure repeated imports of the same Workflow overwrite existing Draft versions rather than reverting Published versions to Draft status.

Fixed an issue where a performance regression introduced in the previous release caused significantly slower workflow import times.

## Ingestion and Connectors <a href="#ingestion-and-connectors" id="ingestion-and-connectors"></a>

### What's New <a href="#whats-new.5" id="whats-new.5"></a>

#### **Desk Connector Available in the Aisera Admin UI**

Introducing a new out-of-the-box **FreshDesk Connector** that replaces the previous generic/override-based workaround. This productized connector natively integrates with FreshDesk and supports the full Knowledge Base Article hierarchy, including sub-folders.

This pre-mapped connector provides a scalable, maintainable, and fully supported integration path for FreshDesk customers with multi-level knowledge base hierarchies (such as **Category > Folder > Subfolder > Article**).

This new connector includes the following capabilities:

**KB Learning - Full discovery path:** Categories > Folders > Subfolders > Solution Articles. Supports filtering by status and visibility fields.

**User & User Profile Learning:** Ingests FreshDesk Agents data.

**Ticket Learning:** Ingests **FreshDesk Tickets** with date-range filtering support via DS Configuration.

For detailed information about how to use the **FreshDesk** connector, see **FreshDesk Connector**.

#### **Disable Archiving Options for Incremental Data Ingestion**

Incremental fetches do not see "old but still valid" docs, so these remain in a 'to be deleted' state and get archived, even though they still exist in the external system.

For example, in testing, this resulted in a drop from \~1k+ docs down to 200+ docs in SOR during incremental runs. Switching to a full (on-demand) fetch restored all docs.

Now you can set an option on your **Data Source Configuration** to prevent the incremental data ingestion from archiving 'old but still valid' article.

**To set Disable Archivng Option:**

1. Navigate to **Settings > Data Sources**.
2. Choose the **Data Source** that you are ingesting data from on an incremental schedule.
3. Select the **pencil icon** to open the **Edit Data Source** window.

<div align="left"><figure><img src="/files/dKj2jpSyxsvBdi2qE7t3" alt="" width="375"><figcaption></figcaption></figure></div>

4. Enable the checkbox for **Disable Archiving**.

This will ensure that **incremental sync jobs do not archive or delete Knowledge Article documents** simply because they were not updated in the source.

[Incremental Data Source Schedule](https://docs.aisera.com/aisera-platform/adding-data-to-your-tenant/integrations-and-data-sources/creating-a-connector/adding-and-managing-data-sources-in-your-tenant/data-source-configurations#setting-a-custom-recurring-schedule)

### What's Changed

#### **The Box Connector now supports extracting metadata (metatags) from .boxnote files during ingestion**

This enables the RAG layer to filter and serve knowledge articles based on attributes such as **region**, **audience**, **access level**, **content type**, and other custom metadata fields configured in the **Box Data Source**.

**Key Capabilities of Metadata Extraction:**\
**Metadata Extraction:** A new "Fetch Metadata" checkbox is available in the Box integration configuration. When enabled, the connector calls Box's metadata API endpoints to retrieve all metadata templates and their field values attached to .boxnote files.

**Downstream Propagation:** Extracted metadata is included in the ingestion payload under a customMetaData object, preserving the full template structure (e.g., template name, field keys, and values).

**ACL-Based Filtering via Custom Scripts:** Administrators can apply custom transformation scripts in the field mapping configuration to map specific metadata fields (e.g., region) to tagKeys and tagValues. This enables attribute-based access control and filtered retrieval at query time.

**Multi-Value Support:** Array-type metadata fields (e.g., a file tagged to multiple regions like \["AMER", "EMEA"]) are correctly parsed and mapped as individual tag entries.

**To Enable Metadata Fetching:**

1. Navigate to **Settings > Connectors** in the Aisera Admin UI.
2. Open the **Box Connector Data Source**.
3. Select the **pencil icon** to open the **Edit Data Source** window.
4. Choose the **Configuration** tab.

<div align="left"><figure><img src="/files/lrl40pRutmwICrDrxglY" alt="" width="375"><figcaption></figcaption></figure></div>

5. Enable the **Fetch Metadata** checkbox.

<div align="left"><figure><img src="/files/FXGW2sS6GOSeSI1L3I6w" alt="" width="563"><figcaption></figcaption></figure></div>

5. Configure field mappings to map your desired metadata fields to **tagKeys/tagValues** using a custom transformation script.
6. Enable auto-commit on the datasource and attach it to the target bot.
7. Validate that metadata appears correctly in the **System of Record (SOR)** and that retrieval respects the configured attributes.

[**Box Connector**](https://docs.aisera.com/aisera-platform/adding-data-to-your-tenant/integrations-and-data-sources/connectors/box-connector)

## Issues Resolved in the Release

The following table includes bugs that were fixed in this release.

<table data-header-hidden><thead><tr><th width="159.47552490234375"></th><th width="191.0760498046875"></th><th></th></tr></thead><tbody><tr><td><strong>Aisera ID</strong></td><td><strong>Product Area</strong></td><td><strong>Summary</strong></td></tr><tr><td><strong>6.16.2026.1</strong></td><td><strong>Agent Assist</strong></td><td>Agent Assist w/Zendesk widget is not scrollable to the bottom when wrap up card is available</td></tr><tr><td><strong>6.16.2026.2</strong></td><td></td><td>Agent Assist w/Zendesk prediction cards are appearing as collapsed irrespective of the widget config settings</td></tr><tr><td><strong>6.16.2026.3</strong></td><td></td><td>In Agent Assist w/Salesforce, the <strong>Next</strong> button should be disabled or greyed out upon reaching the final page</td></tr><tr><td><strong>6.16.2026.4</strong></td><td></td><td>Discrepancy in the value of Analyzed and Agent action values in the 'Agent Assist Aggregate over time' graph</td></tr><tr><td><strong>6.16.2026.5</strong></td><td><strong>Webchat, Chatbot, Copilot, and Universal Bot</strong></td><td>Screen repeats "Message from bot" multiple times before displaying the actual message</td></tr><tr><td><strong>6.16.2026.6</strong></td><td></td><td>Webchat: Privacy Policy Message is not translating for Webchat Channel</td></tr><tr><td><strong>6.16.2026.7</strong></td><td></td><td>Chatbot: while using slack sdk bolt, links are rendered incorrectly</td></tr><tr><td><strong>6.16.2026.8</strong></td><td></td><td>Chatbot: Missed link rendering when img appear inline and error on switching between normal and bolt mode during same session</td></tr><tr><td><strong>6.16.2026.9</strong></td><td></td><td>Chatbot: Slack even after updating the tenant level flag the switch to new sdk is not happening</td></tr><tr><td><strong>6.16.2026.10</strong></td><td></td><td>AI lens is failing to load - If co-pilot channel and webchat channel co-exist</td></tr><tr><td><strong>6.16.2026.11</strong></td><td></td><td>Chatbot: Conversation Action Labels Using App Language Instead of Chat Language</td></tr><tr><td><strong>6.16.2026.12</strong></td><td></td><td>Copilot: Citations Fix active badge color, sidebar rendering, and post refresh pill rendering</td></tr><tr><td><strong>6.16.2026.13</strong></td><td></td><td>Names not shown in UI for copilot channel</td></tr><tr><td><strong>6.16.2026.14</strong></td><td><strong>Campaigns</strong></td><td>Form Submit is failing in conversation server in Campaigns</td></tr><tr><td><strong>6.16.2026.15</strong></td><td></td><td>Campaign flows fail validation with "missing a description" error when publishing under a Conversational AI v2.0 bot</td></tr><tr><td><strong>6.16.2026.16</strong></td><td><strong>Connectors</strong></td><td>Known credential Expiration Date Field should not be a mandatory field In Create/Edit Integration Page</td></tr><tr><td><strong>6.16.2026.17</strong></td><td></td><td>Datasource Execution Summary page is not showing graph section</td></tr><tr><td><strong>6.16.2026.18</strong></td><td></td><td>Error on field change - FileData</td></tr><tr><td><strong>6.16.2026.19</strong></td><td><strong>Flows (Workflows and Hyperflows)</strong></td><td>Huge delay with Flow import process after 5/15 release</td></tr><tr><td><strong>6.16.2026.20</strong></td><td></td><td>Repeated Flow Import Incorrectly Converts Published Version to Draft Instead of Overriding Existing Draft [No Changes Are Made Before Publishing]</td></tr><tr><td><strong>6.16.2026.21</strong></td><td><strong>Notification</strong></td><td>Credential Expiration date is not saved as expected in DB while creating Notification setting for a specific Integration</td></tr><tr><td><strong>6.16.2026.22</strong></td><td></td><td>Credential Notification Emails: Fix formatting of special Characters</td></tr><tr><td><strong>6.16.2026.23</strong></td><td></td><td>Credential Notification Screens Issues</td></tr><tr><td><strong>6.16.2026.24</strong></td><td><strong>User Profiles and Roles</strong></td><td>Credential Notification Emails: Fix formatting of special Characters</td></tr><tr><td><strong>6.16.2026.25</strong></td><td></td><td>Credential Notification Screens Issues</td></tr><tr><td><strong>6.16.2026.26</strong></td><td></td><td>User Profile Service: Prevent Duplicates Values in Group Names List</td></tr></tbody></table>