> For the complete documentation index, see [llms.txt](https://help.tellius.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tellius.com/whats-new/release-6.3/patch-6.3.2.md). # Patch 6.3.2 Tellius 6.3.2 concentrates on the surfaces people work in every day: how work is shared, how it is exported, and how it is administered. * Kaiya conversation sharing moves to a read-only model with an explicit option to continue a shared conversation as your own copy. * Vizpad Custom Views become independently shareable, and Selective Export gains section-level selection with section ordering. * Super Users can now see and manage scheduled jobs across all users. * Kaiya answers produced by a Mission now name the Mission and version behind them, and access to the Context module can be restricted by role. * The release also adds a home page tour for new users, table header background colour, and refinements to sidebar navigation. ## **🚀 New Features** ### **Scheduled Jobs management for Super Users** Under **Notifications →** **Scheduled Jobs** page now supports platform-wide visibility for Super Users while leaving the experience unchanged for everyone else. Regular users continue to see only the jobs they created. A Super User can view scheduled jobs created by any user, with a **Created By** filter that defaults to the current user. Super Users can view job details, view failure details, and delete a scheduled job, subject to the authorization rules already in place. Scheduled jobs can also be enabled and disabled, and a disabled schedule is held from executing until it is enabled again. Server-side authorization is unchanged. ### **Home page tour for new users** A guided tour now introduces the home page to users signing in for the first time, walking through the home page, Kaiya Architect, and collapsible left pane so a new user has a starting point and a guided step-by-step walkthrough.
### **Guard rail validation for Deep Insight summaries** Every Kaiya **Deep Insight** summary now passes through a lightweight validation step before it is shown. The check uses the dataframes the run executed and the citations it emitted, and looks for three specific conditions: * a unit or dimension mentioned in the summary that does not exist in the Business View or in the executed data * a value that does not trace back to the run and is presented without a note explaining its origin * a summary that addresses a different topic from the question that was asked. Depending on severity, a flagged summary is held back, surfaced to the user with an explicit note, or re-attempted. This complements the validation already applied to generated PDF, PowerPoint, and DOCX artifacts, covering the summary those artifacts are built from. ### **Conversation sharing without cloning** Sharing a Kaiya conversation now shares a reference to that conversation rather than creating a copy for the recipient at the moment of sharing. The recipient opens the conversation in read-only mode and can read the full exchange as it stands. In place of the query input box, a **Continue this Conversation** option is offered. Choosing it clones the entire conversation under the recipient's own account, at which point they can carry it forward independently. The clone carries the conversation's full working state, so actions that depend on the underlying results behave the same way they did in the original conversation. This includes export queries and PowerPoint export, and applies to conversations built on live Business Views. Conversations can now be shared with user groups as well as with individual users. Conversations shared before this change continue to appear for their recipients, and a tooltip explains that a shared conversation opens read-only and that continuing it proceeds as a separate conversation. ### **Vizpad Custom View sharing** A single **Custom View** of a Vizpad can now be shared with specific users or groups, at either read or write permission. A Custom View is a saved overlay on one Vizpad — its filters, per-tab state, widget formatting and sorting, metric switches, and layout. The recipient opens only the view that was shared, along with the base Vizpad it renders on; the owner's other Custom Views on the same Vizpad remain private.
Sharing a Custom View automatically grants view access to the parent Vizpad, since the view needs it to render, and the Vizpad opens in read-only mode for the recipient. The view dropdown then lists the shared view and the base Vizpad only. * With read access, a recipient can view the shared view, build a new Custom View from it, and set it as their default, but cannot overwrite, rename, or delete it. * With write access, a recipient can additionally overwrite, rename, or delete the shared view. The current user along with anyone the view is already shared with are excluded from the share search. Revoking a user's Vizpad access also revokes their access to any Custom Views shared from it, and the sharing dialog indicates when a user being revoked also holds Custom Views from that Vizpad. ### **Mission attribution in Kaiya answers** When a Kaiya answer comes from a Mission, the answer now carries a line identifying the Mission that produced it, the version that ran, and how the run was started (Scheduled, Chat, or Run manually). The Mission name and the accompanying arrow both open that Mission in a new tab, at the results of that particular run rather than its most recent one. The detail appears once per answer, even where an answer is assembled from several parts such as steps, a chart, and a summary. Answers that did not come from a Mission show nothing extra. What is shown is captured at the moment the Mission ran. Renaming a Mission or publishing a new version afterwards does not alter an older answer, and each run in a conversation opens its own results. Where a user does not hold access to the Mission, or the Mission has since been deleted, selecting it returns a clear message. ### Minimum-role configuration for Context module access Access to the **Context** module can now be set by minimum role. If set to Admin, the module is restricted to admin and above, and users below that level do not see it at all.
## :chart\_with\_upwards\_trend: **Enhancements** ### **Section-level selection in Selective Export** Selective Export now allows an entire section to be selected in one action, rather than requiring each chart within that section to be selected individually. Exports also preserve section order, so charts from the first section appear first, followed by those from the second, and so on, matching the arrangement in the Vizpad. This applies to both standard and selective PowerPoint and PDF exports. ### **Sidebar navigation in collapsed and expanded states** The collapsed sidebar now shows only the configured primary navigation items (New chat, Kaiya, Context, Missions, Explore, Data and Apps), keeping the rail focused; the **More** items are held until the sidebar is expanded.
The expanded sidebar continues to present the **More, Starred**, and **Recent** sections. When the sidebar is expanded and a user selects a navigation item, the sidebar collapses automatically to return the maximum working area. ### Filters affecting a Vizpad A new action in the Vizpad header opens a popover listing every filter currently acting on that Vizpad. Filters are grouped by the scope they come from (Global, Tab, Section, and local chart) so it is clear not only which filters apply but where each one was set.
Only filters applicable to the selected visualization are listed: a scope filter appears when it targets the same Business View as the visualization or shares a common column with it, and the visualization's own local filters always appear. Previously only local filters were visible from the chart itself. ### Briefings for manually run Missions The Briefing page previously listed only Missions executed on a schedule. A briefing is now recorded and displayed regardless of how the Mission was triggered, including a run started from the **Run** button and a run started through a query in a Kaiya conversation. ### Pagination defaults for charts Pagination is now enabled by default across chart types, with the default row count raised to 500. The configured count is also retained when a column is added to a bucket, where it previously reset to a lower value. ### **Pivot table export volume** Pivot table exports to Excel and CSV now return well beyond the previous default row count, with an information tooltip in settings and on the Vizpad showing the limit in effect. Excel export for pivot tables also writes rows as they are generated rather than holding the full set in memory first. Large pivot exports therefore complete under a lower memory ceiling. ### Brand Name for branded deployments Branding now carries a dedicated Brand Name property, used wherever a customer or brand name is displayed in the application. It is held separately from Tab Name, so deployments that already configure Tab Name are unaffected and the existing behaviour of that setting is unchanged. ### License expiry alerts A license expiry alert is now sent daily, beginning 20 days before the expiry date and repeating until expiry. This applies across all deployments. ## :tools: **Minor Fixes** #### Kaiya 1. Improved the responsive layout of the Kaiya chat interface across embedded and iframe views, so the redirect control sits in the corner without additional spacing on the right, the Business View hover card displays in full, and the chat panel remains reachable by scrolling while the window is resized. 2. Refined the export options presented for a conversation result so a single set of options is shown. 3. Improved chart tooltips in Kaiya so hovering over a text-rendered chart displays the dimension value. 4. Improved connection handling in the Voice Assistant so a disturbed connection recovers, and a spoken question is carried through to the transcript. 5. Improved authentication validation for the extension so it completes within the expected time. 6. Several adjustments have been made to the home page. * The input area in Missions, Apps, and Kaiya Architect now uses an increased maximum height. * Business Views are excluded from the **Recently Used** section. * Kaiya chart history has moved to the top left corner of the page. The **Briefings** empty state is not shown to a new user. 7. Queries no longer fail when a user belongs to several groups that assign the same security tag with different values under the same operator. The applicable values are resolved. #### Kaiya Apps 8. Improved the **Cancel** and **Confirm** controls in the App chat session for clearer visibility. 9. Improved conversation history handling for remixed Apps that have no chat messages, so the history request settles on load. 10. Improved App editing so that a request to change an existing section resolves against the App's content despite whitespace and line break differences, and the edit completes rather than continuing to retry. 11. Improved metric queries in Apps built across linked Business Views, so a metric requested across those Business Views resolves in a single analysis step rather than being assembled from separate ones. 12. An App's plan and complete generated code can now be copied to the clipboard in a single action. 13. An App edit that requires no change to the generated interface now completes as a valid no-op, so an edit driven by analysis or query corrections finishes. 14. The timeout for App creation is now configurable rather than fixed, which allows longer builds to run to completion. 15. Row-level permission validation now handles filter dropdown queries that cannot be combined with a permission column because of deduplication, so live Apps continue to load. 16. Improved recovery for App services, so a failed instance is restored and published Apps remain reachable. #### Kaiya Missions 17. Improved the Mission creation flow so the **Save** and **Continue** action proceeds when a Mission name has not yet been generated or the generated title is long. Where no name has been generated, the workflow or version name is displayed in place of the first conversation query. 18. Skills are now applied during Mission planning, so relevant Skills are surfaced and used as a Mission's plan is built. 19. Inputs collected during a Mission's first execution, including time-filter values, are now retained and reused when the plan is patched and executed again. This means the templated SQL receives the same input values on every subsequent execution of a patched plan. 20. A storyline supplied during Mission setup is now applied to the export produced on creation. 21. A report storyline can be added to a published Mission and saved. 22. Running a Mission from the listing or detail page now opens a Kaiya conversation carrying the Mission detail, with execution status updating as the run progresses, in place of an empty page. 23. Mission chat now runs on the same synchronous flow used by Kaiya chat and Apps, which resolves intermittent run failures. 24. Plan generation now returns an error where no steps are produced. A plan is resolved against the version being executed rather than falling back to the active Mission's steps, and the plan and patch prompts are cached. 25. A Python step now waits for the SQL step it depends on to complete. This removes intermittent Deep Insight and Mission failures where a run reported nothing to process and the summary was then held back. #### Vizpads 26. Improved the location map so zooming continues to the maximum level, including where no markers fall within the current view. 27. Improved cache invalidation for Vizpads when the underlying Business View is refreshed. 28. Improved direct navigation to the required Vizpad so the interface renders when the address is entered directly. 29. For list-type dynamic parameters, the available values now display as tag chips constrained to a single line, with the full list available on hover. The edit panel therefore keeps a consistent height regardless of how many values a parameter holds, and the **Save** control stays in view. 30. Refined the pagination stepper in Advanced Settings. 31. An invalid, removed, or inaccessible Vizpad address now opens a clear error state with a route back to the listing page. #### Vizpads - Formatting 32. Improved conditional formatting so it applies to a pivot table containing a calculated column that carries a table calculation, matching the behavior already present in Excel export. 33. Refined conditional and gradient formatting so the measure list matches the columns present in the table when the same measure is added twice with the same aggregation, so formatting applies to the measure shown. 34. Converting a **Table** to a **Detail Table** carries forward formatting only for the column types that Detail Tables support, and formatting configured on a column is retained when that column is removed from the **Sort By** bucket while remaining in the configuration. Formatting is also evaluated for pivot tables containing zero values. 35. Refined the colour picker in table header formatting for stable display in View Mode. The picker presents the supported set of colour options for this setting. 36. Refined conditional formatting behavior for bar and line charts, where formatting applies to one measure at a time, in contrast to tables where all formatting is applied together in precedence order. 37. Refined value formatting options for pivot tables so only the options that apply to pivot tables are presented. 38. Table headers now support a configurable background colour. The selected colour is saved with the table configuration and persists with it. #### Vizpads - Filters and Metrics 39. Refined the pinning and unpinning options in the filter panel so the controls presented match the actions available. 40. Improved metric switch configuration so a metric switched in View Mode is not carried into the measure bucket in Edit Mode, and the chart configuration panel opens in Edit Mode only. 41. Improved metric switch behavior so a switch applied at tab level is reflected at section level, and chart headers display the metric name as it appears in the metric switch list, with a tooltip for longer names. 42. Improved chart loading when a switch metric is applied to a calculated column after change aggregation columns have been removed, and added a clear message where a market share calculation is configured with more than the supported number of groupings. 43. Refined saving of tab-level and global filters through the expansion control. #### Vizpads - Export 44. Improved capture of table charts in PDF and PowerPoint export so a table is exported as a single unit rather than split across pages or slides. 45. Ensured a bar chart's stack-by column is represented as a stack rather than a colour grouping in PDF and PowerPoint export, including when the Vizpad contains several charts. 46. Included applied global and tab-level filters in Excel and CSV exports. 47. Ensured table header background colour is carried into Excel downloads. 48. Excel exports now serialize the download when the underlying data is large, which gives exports over high-volume tables a more predictable path to completion. 49. Number formatting applied to a calculated column is now carried into Excel export, matching the treatment already given to regular columns. 50. Export now completes for tables carrying conditional formatting defined with custom colour values. #### Data and Datasets 51. Improved the dataset metadata screen so the publish action completes after column-level display names, descriptions, or synonyms have been added. 52. Business Views built on a fiscal calendar now calculate the number of periods in a year from the calendar's own configuration. Calendars defined with thirteen or a different period count are validated correctly at both daily and monthly resolution. 53. Security tags applied to a Business View column are retained across the publish operations that previously cleared them: renaming a column at dataset level, deselecting and reselecting a column, adding or editing a grouping, publishing calculated columns or date mappings, and paging through columns on the Edit Business View page. 54. Leaving the Business View edit page by switching tabs now behaves predictably, with the edit state cleared. #### Administration and Access 55. Improved row-level permissions so a permission created with the NOT IN operator displays its configured values when the group is reopened. 56. Improved user export so a download started after selecting all matching users returns the same result as a download without bulk selection. 57. Improved group export so a download following a substring search returns the groups matching that search. 58. Refined the notification shown when a license is approaching expiry so it is presented once per occurrence. #### Embedding 59. Improved access control for embedded links carrying a UTM source, so access stays scoped to the embedded page the link was generated from. 60. Improved token handling for direct access to an embedded Vizpad so the link resolves consistently. 61. Time resolution is now applied for view mode in embedded links. #### Notifications 62. Added a clear message when navigating from a notification to an object that has since been removed. 63. Notifications for jobs that complete with a **Failure** or **Partial Success** status now carry the reason in the interface, so the cause can be read from the notification detail. This covers custom SQL load refreshes and scripting dataset updates. 64. Values shown in **Synchronous Jobs** are rounded for readability, in the **Time Taken** column and in the **Time Breakdown** detail. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://help.tellius.com/whats-new/release-6.3/patch-6.3.2.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.