AG Studio Go-Live
Introduces the composer UI for building analytics dashboards with AG Grid and AG Charts.
shipped
Pivot and hierarchical widgets and WCAG 2.1 AA accessibility have now shipped, bringing analytical depth and enterprise readiness to Studio. The rest of Q3 turns to a visual data expression builder, global undo/redo on the canvas, server-side pagination, and the Studio Agent Framework. Planned items reflect current intent; timing may shift as priorities evolve.
Introduces the composer UI for building analytics dashboards with AG Grid and AG Charts.
Lets developers place custom HTML/JS or framework components on the Studio canvas alongside native charts and grids.
Unblocks customers who need bespoke visualisations without leaving Studio.
Runs sum, count, avg and other aggregations on the server rather than in the browser.
Handles enterprise-scale datasets that would otherwise blow browser memory limits.
Lets report users edit field formatting, labels and display from the edit panel.
Gives report builders direct control over how fields are presented, reducing the need to pre-configure everything at the data source level.
Lets users navigate and control the dashboard by keyboard, with context-aware shortcuts.
Speeds up power users and lays the groundwork for meaningful accessibility compliance.
Lets users group and analyse date fields by chronological and cyclical calendar units such as year, quarter and month.
Removes the need to manually construct time-based expressions for common patterns like period-over-period comparisons and year-to-date calculations.
Exposes Studio's AI tools through the AI Toolkit, callable independently of the assistant.
Gives developers the flexibility to integrate Studio's AI capabilities into their own workflows and interfaces, and forms the foundation for everything that follows.
Audits and remediates Studio against WCAG 2.1 AA for keyboard, screen reader and contrast.
Meets a baseline expectation for enterprise software and a common requirement in procurement processes.
Adds pivot tables, hierarchical charts and multi-level category grouping as new widget types.
Gives enterprises the standard way to explore and visualise the hierarchical, multi-dimensional data they work with every day.
Lets users create calculated fields using a visual expression editor.
Makes custom metrics accessible to non-technical users who cannot write raw expressions.
Lets users undo and redo every edit mode action, including widget placement, resizing and configuration.
Underpins a confident editing experience as dashboards grow in complexity.
Offers several ways to integrate Studio's agentic capability into an existing workflow, with configurable behaviour.
Gives teams flexibility in how they wire AI into Studio, rather than locking them into one integration approach.
Lets developers handle page requests on the server through an API, across all widget types.
Keeps Studio performant when working with datasets that cannot be loaded client-side in their entirety.
Explores how Studio can participate in server-side agentic workflows through emerging frameworks.
Prepares Studio for emerging server-side agentic workflows, moving deliberately as industry standards mature.
Streams partial dataset updates to widgets without a full data reload.
Enables live and near-real-time dashboards without the overhead of re-fetching entire datasets on each update.
Lets users explore detail from a chart or grid, or jump to linked dashboards carrying filter context.
Lets users move from summary to detail without leaving their workflow, a standard interaction in analytical products.
Adapts dashboard layouts to phone and tablet screens, alongside broader polish of the layout and panel experience.
Keeps dashboards usable on the phones and tablets they are increasingly opened on, where a fixed desktop grid breaks down, and keeps building and navigating them smooth as Studio matures.
Combines server-side and client-side execution in one data engine for developers building custom data integrations.
Gives integrators a supported way to combine server-side execution with Studio's client-side capability, rather than building it from scratch.