Coginiti 26.4 Release Notes

This release reimagines the AI Assistant around two purpose-built personas, significantly expands what the Semantic Layer can model, introduces a lightweight Consumer experience, and redesigns Admin Settings from the ground up. It also adds a Semantic SQL ODBC Driver for connecting external tools, broadens CoginitiScript (CSL) publication support, and ships a range of security and stability fixes.

Major Highlights

AI Assistant Reimagined: Coginiti Smith & Coginiti Guide

The AI Assistant has been rebuilt around two distinct personas so its behavior matches who is asking and what they're trying to do.

What's new

• Coginiti Smith — the data-development persona. Creates catalog folders and SQL entities through natural language, and generates semantic queries that execute and return both the underlying SQL and a formatted results table.
• Coginiti Guide — the consumer-facing persona, grounded in the semantic layer. Translates natural-language questions into semantic queries, executes them, and returns model-consistent results with no SQL required.
• Charts alongside results — the assistant auto-renders a chart next to the result grid, backed by new backend API support.
• Shareable chats — share any AI conversation through a unique link.
• Cleaner conversation UX — truncated previews with split-screen full view for long SQL, a single collapsed tool block per row, and refinements to chat tabs, Mermaid diagrams, and model selection.

Why this matters. Authors and consumers get an assistant tuned to their actual job. Developers can build and query the catalog conversationally, while business users get trustworthy, semantic-layer-grounded answers — with visuals and shareable context — without writing a line of SQL.

New Consumer Role

A lightweight Consumer role for users who interact with data through the AI Assistant rather than authoring it.

What's new

• Focused settings — Consumers see a streamlined Settings experience limited to the AI Assistant (read-only) and Theme (editable).
• Workspace-tab chat sessions — AI chat sessions open as separate workspace tabs.
• Safe role transitions — demoting a user to Consumer cleans up associated connections, templates, and catalog assets, and admins are prevented from reassigning Consumer-owned data to another user.

Why this matters. You can give business users a safe, simple, AI-first way into their data without exposing the full authoring surface — and without risky data hand-offs when roles change.

Semantic Layer: Filtered, Derived & Cross-Entity Measures

The Semantic Layer (SMDL) can now express the real-world metrics analytics teams actually need, closing the gap between simple aggregations and production KPIs. All additions are fully backward compatible — existing models work unchanged.

What's new

• Filtered measures — declare a filter so an aggregation only counts matching rows. Expose completed_revenue, pending_revenue, and cancelled_revenue side by side from one entity, with compound AND/OR conditions, support for every aggregation type, and reusable boolean-dimension references.
• Derived measures — compose measures from other measures (profit, margin, completion rate, net revenue) using post-aggregation arithmetic, with chained derivations, ratios of filtered measures, SQL functions like ROUND/NULLIF, and circular-reference detection.
• Cross-entity references — reference a related entity's columns and dimensions with dot notation (entity.column). The layer resolves the path through existing relationships and generates the joins automatically, including multi-hop paths, with join deduplication and clear errors when no path exists.

Why this matters. You define a metric once and it stays consistent everywhere — no more CASE WHEN logic copied into every dashboard, no more each team inventing its own definition of "margin." Cross-entity references eliminate the manual joins that previously forced authors to denormalize data or pre-join SQL just to filter by a related attribute.

CoginitiScript (CSL) & Publication

CTE support in MS SQL Server publication

What changed. Full-publication CSL blocks targeting Microsoft SQL Server now support query bodies that begin with a CTE (WITH clause). Coginiti materializes the query through a temporary view, builds the target table from it, and cleans the view up afterward — handling single-member, multi-member, and nested CTEs. This also extends to Microsoft Fabric SQL Database.

Why this matters. CTEs are the standard idiom for multi-step transformations and ranked results. You no longer have to rewrite perfectly valid SQL to work around a SQL Server engine restriction.

Note: This path requires the connection's database user to hold CREATE VIEW permission in the target schema.

Exclude columns from incremental MERGE updates

What's new. Incremental publication blocks accept an :exclude_columns parameter that omits the specified columns from the generated MERGE UPDATE SET clause. Matching is case-insensitive, and existing unique_key and update_on_changes_in behavior is unchanged.

Why this matters. Incremental publication now works for target tables with IDENTITY (surrogate key), computed, or system-managed columns — a class of table that previously failed at execution time and blocked the feature entirely for many SQL Server data warehouses.

Editor enhancements: autocomplete, hover & go-to-definition

What's new. The CSL editor gains IDE-style language support — autocomplete suggestions as you type, hover information for symbols and entities, and go-to-definition navigation.

Why this matters. Authoring and navigating CoginitiScript is faster and less error-prone, with less time spent hunting for where something is defined.

Actions & Scheduler

What's new

• Run actions from the editor — trigger an Action's execution directly from the editor toolbar.
• Action file history — view revision history for files in the .actions folder.
• Nested authoring — create entities and inner folders inside the .actions directory.
• Better job control — admins can stop and manage scheduled jobs created by disabled users, and the schedule popup now scrolls so all controls stay accessible.

Why this matters. Action authoring becomes a first-class workflow inside the editor, and admins retain control over scheduled jobs even after the original owner is disabled.

Admin Settings Redesign

What changed. Every Admin Settings screen — Users, Groups, LDAP, OAuth, SAML, SMTP, Proxy, Global Preferences, Manage Connections, Object Store Templates, and Query Execution — has moved from modal popups to refreshable workspace tabs, with inline editing, contextual menus for adding users and groups, "active configuration" indicators in Directory Config, and stricter access control.

Follow-on polish in this release:

• A pre-flight check on user deletion that verifies the reassignment target has no same-named project.
• A fix so editing an external user no longer breaks the local-user editing flow.
• A loading spinner during long-running role-change operations.

Why this matters. Administration is faster and less modal-bound — you can keep configuration open in tabs, edit in place, and trust that destructive operations like user deletion are validated before they run.

Security & Stability

• Cumulative CVE remediation across container images for the release.
• Patched multiple CVEs in UI dependencies, including upgrading axios to v1.15.1.
• Fixed malformed security-log structure on query-execution failure.