We’ve introduced a new table view to better represent hierarchical data in reports.

What’s new:

• Hierarchical table view. Group data into a structured hierarchy with expandable rows and subtotals at each level.
• Multi-metric support. View multiple metrics side-by-side within the same roll-up table.

Why it matters:

• The roll-up table provides a clearer way to analyze grouped data, making it easier to understand relationships between parent and child dimensions. This gives users more flexibility in how they explore and present report data.
  
  

We’ve expanded Custom Metrics to support building formulas across aggregated values.

What’s new:

• Aggregate formula builder. Define variables (for example, A, B) and combine them into a final KPI using arithmetic operators in a simple formula editor.

Why it matters:

• This enhancement gives users greater flexibility to define business-specific KPIs, making it easier to express relationships between aggregated metrics directly within Ternary.

We’ve introduced the Notification Center, a centralized place to manage subscriptions across Ternary.

What’s new:

• My Subscriptions. View and manage all active subscriptions in a single table. Filter by type, trigger, or delivery channel, and edit or unsubscribe directly.
• Owned Content. See who is subscribed to reports, dashboards, budgets, and alert rules you own, and manage subscribers without leaving the page.
• Supported subscription types. Reports, Dashboards, Budgets, and Alert Rules are all supported.

Why it matters:

• Previously, subscriptions were managed across individual resource pages with no centralized view. The Subscription Center brings everything into one place, making it easier to manage notifications and understand who is receiving updates.
  
  

We’ve added support for configuring organizational relationship terminology during tenant setup.

What’s new:

• Pre-configured terminology. Solution Architects can now define relationship labels during tenant configuration so customers see purpose-built terminology from day one.

Why it matters:

• This reduces the need for post-deployment customization and streamlines onboarding by ensuring the platform reflects the customer’s organizational structure from the start.
  
  

We’ve added forecast overlay capabilities to the Ternary Reporting Engine.

What’s new:

• Forecast overlays. Reports can now include a forecast data layer that projects trends based on historical data.

Why it matters:

• This allows users to visualize projected trends alongside actuals in a single chart, making it easier to plan ahead and understand potential future spend.

Report table configurations now persist across sessions.

What’s new:

• Saved table preferences. Selections such as Time Series and Show Totals are now saved per report.

Why it matters:

• This ensures a consistent experience when revisiting reports, eliminating the need to reconfigure table settings each time.

  
  

  
  

We’ve improved the configuration experience for value-based Custom Labels.

What’s new

• Updated configuration UI. The new design introduces a clearer step-by-step structure, improved key and value mapping visualization, and more descriptive guidance.

Why it matters:

• This update makes it easier to create and manage value-based labels, reducing friction and improving usability.

Custom Labels now support fallback logic.

What’s new:

• Else condition support. You can now define an else condition when configuring a Custom Label.

Why it matters:

• This provides more control over how unmatched values are handled, ensuring complete and consistent label outputs.

We’ve improved how you explore AI-generated label suggestions.

What’s new:

• Direct report links. AI-assisted label groupings now include links to view suggested values directly in a report.

Why it matters:

• This makes it easier to validate and explore suggested groupings, providing a faster path from recommendation to analysis.

We’ve added safeguards when deleting custom metrics.

What’s new:

• Impact visibility. You can now see which reports are affected before deleting a custom measure.

Why it matters:

• This helps prevent unintended disruptions by making downstream impacts clear, allowing users to make more informed decisions when managing metrics.