# Patch 6.2.0.2

Tellius 6.2.0.2 introduces a significant change: "Agentic Workflow" is now "Agentic Missions" across the entire platform. This patch also delivers sankey chart interactivity, multi-BV memory scoping, Deep Insights refinements, and continued Kaiya Apps and Data Architect polish. On the Vizpad side, conditional formatting, filter behavior, chart stability, and backward compatibility with legacy Vizpads receive extensive attention.

## 🚀 **New feature**

### Introducing Kaiya Missions

Agentic Workflows are now Kaiya Missions, and the new name reflects what the capability actually does. A mission is an autonomous, end-to-end analytical operation. You define a business objective, lay out the analytical steps Kaiya should execute, set a recurring schedule, and choose your delivery format. Kaiya runs the mission on cadence and delivers a finished artifact (a PowerPoint deck, a PDF report) directly to your inbox. No manual re-runs, no re-asking the same complex questions every Monday morning.

{% hint style="info" %}
This is not a scheduled report. Every BI tool can schedule a screenshot of a saved dashboard. Kaiya Missions schedules a fresh investigation. Each run reasons about what the data shows right now — which metrics to drill into, what anomalies surfaced since the last run, where variance drivers shifted, what root causes emerged. The analysis is new every time. The output is a storyline-driven deliverable
{% endhint %}

<figure><img src="/files/P1MKJVot1V6a454c9ack" alt="" width="563"><figcaption></figcaption></figure>

#### **How a Kaiya mission works**

* You define the objective once: the metric to track, the analytical steps to execute, the schedule, the audience, and the output format.
* Kaiya lays out the plan: data sources to query, analyses to run, drill-down paths to follow. The plan is explicit, auditable, and modifiable in plain English ("add competitor share data," "exclude specialty pharmacies").
* On each scheduled run, Kaiya executes the full analytical chain against live data, carries context across steps, determines which findings warrant attention based on what the data shows that run, and assembles the output. The finished artifact — a PowerPoint deck or PDF — lands in your inbox on cadence.

All missions are managed under Kaiya → AI Agents → Scheduled Missions. Owners can view, edit, pause, resume, or delete their schedules.

{% hint style="warning" %}
If another user runs the same workflow ad-hoc and a schedule already exists, Kaiya offers to subscribe them to the existing schedule rather than creating a duplicate. Subscribers receive the same output on the existing cadence.
{% endhint %}

All existing scheduled agentic workflows continue to run on their configured cadence. The terminology has been updated across the entire platform — the Kaiya conversation interface, the scheduling UI, navigation labels, and all user-facing text.

## 📈 Enhancements

### **Multi-Business View Selection in Kaiya Conversations**

Kaiya conversations now support selecting up to three Business Views in a single session, allowing analysis to span related subject areas. For example, combining sales and inventory BVs without context-switching. Multi-BV selection is available across Kaiya Conversations, Apps, and Missions.

The first Business View selected acts as the primary BV and drives dialect, calendar, and the date column for the conversation, so order matters when configuring a multi-BV session.

To enable cross-BV analysis, Business Views must be connected through **soft links.** They are shared dimensions such as customer, product, or date that act as join keys between BVs. Soft links are configured under **Data** ➞ **Business Views** ➞ **Linking**, where users can select a Business View, choose the columns from each side that should map to each other, and save the mapping. Multiple column mappings can be added per linked pair.

<figure><img src="/files/96Wkh3TCtsnMsWD34cqK" alt="" width="563"><figcaption></figcaption></figure>

When soft links are configured, Kaiya generates a single merged query that joins across the selected BVs and returns unified results. When soft links are not configured, Kaiya answers from the BVs that can satisfy the question independently. For best results, BVs combined in a single question should share the same SQL dialect.

**Soft links** unlock genuine cross-subject-area analysis without requiring data to be physically merged or remodeled. Teams can keep their Business Views modular and domain-specific (sales, inventory, marketing, finance) while still asking questions that span them. Kaiya handles the joins automatically based on the relationships defined once at the BV level.

### **Personalized tags for Vizpad filters**

Different users often need to see different slices of the same Vizpad — a West region manager wants West data, an East manager wants East data, and so on. Personalized Tags let admins set those default filter values once, so each user automatically sees their own data when they open a Vizpad. No more clicking the same filter every morning.

<figure><img src="/files/I8mwIRHuUBS4cvy04mCL" alt="" width="563"><figcaption></figcaption></figure>

An admin creates a tag (like "*Region*") under **Settings → Identity & Access → Personalized Tags**, links the tag to the matching column in the dataset, and assigns each user their value (Alice → *West*, Bob → *East*). Values can be set one user at a time, or for many users at once through the new **Bulk Personalized Filter Upload** wizard, which accepts CSV, XLSX, and XLS files. Multiple values in a single cell are separated with a pipe (`|`).

When a user opens a Vizpad that already has a filter on the tagged column, Tellius automatically swaps the filter values for that user's personalized values. Users can toggle personalization off in view mode if they want to see the Vizpad's default values instead. If you have both user-based value and a group-based value for the same tag, then the user-based value precedes.&#x20;

### Sankey Charts: Drill-Down

Sankey charts now support interactive filtering and drill-down. Users can click on a flow path or node to drill into the underlying data, and apply filters directly from the visualization. Tooltip and hover behavior has also been corrected for accuracy and consistency with other chart types.

<figure><img src="/files/5bglFijdBPqEZoOTKRI9" alt="" width="563"><figcaption></figcaption></figure>

### **Compact chart scaling for dense Vizpad layouts**

A new setting under **Advanced** **Settings** allows admins to control compact chart scaling directly. When enabled, charts use a tighter layout and scale so more of the visualization fits within each Vizpad widget. This is particularly valuable for dense dashboards where multiple charts need to coexist on a single screen without sacrificing readability — keeping the full analytical picture visible at a glance.

<figure><img src="/files/4XQa41KiTO1ruPLJWs4z" alt="" width="563"><figcaption></figcaption></figure>

For teams building executive dashboards or operational monitoring views with high widget counts, compact scaling means fewer layout compromises and more context per screen. Disable it to revert to standard chart padding and sizing when individual chart clarity takes priority over density.

## 🛠️ Minor Fixes

#### Vizpad - Charts and Layout

* Resolved issues with KPI spacing and chart positioning across save and reload cycles, between edit and view modes.
* Compact mode KPI rendering now maintains proper layout alignment between edit and view modes.
* Resolved the issue with metrics and dimensions ordering in the modern Vizpad to match the classic view sequence.
* Resolved the issue with legacy Vizpad component width properties in the redesigned Vizpad, ensuring older Vizpads open without layout issues in the new interface.
* Vizpads with empty chart placeholders can now be saved.
* Resolved the issue with multi-line chart generation when column role configuration is valid.
* Fixed the issue with Y-axis label display on YoY charts.
* Resolved the issue with bubble chart size bucket columns when applying Market Share filters with percentage change or absolute change aggregations.
* Chart rendering and label formatting consistency has been improved across multiple chart types.
* Resolved the issue with measure duplication across chart buckets when switching between chart types.
* Resolved the issue with grid formatting on dual-axis charts to display Y2 axis ticks, min, and max values.
* Fixed the issue with the benchmark dropdown when selecting "**Fixed Value**", and reloading a Vizpad correctly preserves benchmark settings.
* Custom view actions and the **"Save View"** button behavior have also been improved for consistency.

#### Vizpad - Filters

* Resolved the issue with global filter deletion in edit mode to reflect changes immediately upon saving.
* Resolved the issue with tab and global date filter application when switching chart types or cloning visualizations within the same Vizpad.
* Resolved the issue with tab-level filter saving to preserve filters on other unvisited tabs.
* Resolved the issue with deleted filters and removed visualizations persisting after tab switching or cloning.
* Resolved the issue with numeric value search in pinned filters.
* Resolved the issue with custom time filter application in percentage change calculations.
* Resolved the issue with custom calendar selection persistence when switching between calendars.
* Fixed the issue with custom date range selections respecting the active custom calendar definition.
* Fixed the issue with the "between" filter condition value rendering in Insights.
* The time slice component in Vizpad has been refined with improved popup positioning (no longer overlapping with filter menus when transitioning between Vizpad versions) and general UX improvements for time-based segment selection.
* Select/deselect interactions for filter values have been updated for improved usability. Stepper input fields in filters can now be cleared properly. The "**between**" operator now correctly clears input values when switching to a different operator.

#### Vizpad - Conditional Formatting

* Multiple conditional formatting issues have been resolved, including: correct rule application for display text generation, proper column dropdown behavior showing display names with fallback to original column names, and consistent formatting behavior across all condition types.

#### Vizpad - Pivot Tables

* Pivot tables no longer show a row count exceeded message when *"Show as Rows"* is enabled.

#### Vizpad - Maps

* Fixed the issue with boundary map visualizations displaying measure column aggregations and ColorBy column labels after hyperlink interactions.

#### Vizpad - Drill

* Resolved the issue with X-axis label updates during drill-down operations and drill interaction state when switching to edit mode.

#### Vizpad - Export

* PPT export now completes successfully for Vizpads containing legacy visualization artifacts.

#### Vizpad - Embedding

* Resolved the issue with visualization-level filter preservation via postMessage when Vizpad changes are made and reverted.
* Fixed the issue with embedded Vizpads when switching to classic mode from the embedded view.

#### Vizpad - Backup

* A Vizpad backup list is now available under Advanced Settings, providing visibility into backup history and restore options.

#### Kaiya

* Kaiya now retains context from previous chart and question interactions when generating follow-up visualizations, improving accuracy of chart recommendations in multi-turn conversations.
* Chart summary generation is now appropriately disabled for KPI and Rich KPI chart types, where a narrative summary is not applicable.
* Resolved the issue with DOCX download from Kaiya conversations.
* Agentic mission inputs are now scoped to individual runs and are no longer persisted to Long-Term Memory, ensuring each scheduled execution uses the intended input values.
* Improvements to the **Deep Insights** analysis flow, including refinements to how intermediate results are presented, how edge cases in multi-step analyses are handled, and how chart context is carried between analysis steps for more accurate follow-up visualizations.

  Kaiya Apps receives continued UI polish, including layout refinements, interaction improvements, and version-specific routing so that users can access specific published versions of an app.
* The UI for Kaiya's clarification questions has been improved with clearer presentation and interaction patterns, making it easier to respond to multi-choice prompts during analysis flows.
* The text displayed during Kaiya's intermediate processing steps has been updated for clarity, providing users with more informative status messages as Kaiya works through multi-step analyses.

#### Data and Business Views

* Under **Data → Business Views → Settings,** resolved the issue with Kaiya context editing in Business View settings.
* Fixed the issue with trend driver value display for quarterly periods.
* Resolved the issue with setting hourly resolution on date columns for Fast Query Engine-backed Business Views.
* Resolved the issue with Data Architect validation at the final stage to resolve key references during Business View creation.
* The **Data Architect** interface has been updated with visual and interaction refinements, improving the experience for the conversational BV creation workflow under **Kaiya → Data Architect**.

## 🛡️ Security Fixes

This release includes additional security hardening. Improvements address request validation and rate limiting controls. These changes strengthen resilience against unauthorized or excessive request patterns.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.tellius.com/tellius-6.3/whats-new/release-6.2/patch-6.2.0.2.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
