Release v3.7

v3.7

This release offers permission-scoped API tokens and a new settings-only IT role.

Rule and ruleset changes now become visible to every user in the tenant without a reload.

Every API token now carries a permission: Read-only or Read & write.
A token can be scoped to a single group — it then only reaches that group's resources — or left tenant-wide.
Tenant-wide tokens can additionally be allowed to manage groups, settings, and tags.
The token list shows the remaining validity ("Expires in N days") and the state (Active, Expired, Revoked); tokens can be revoked. The secret itself is shown once at creation only.

A settings-only role for IT departments: IT admins manage tenant settings, users, and groups, but have no access to tables, data, or issues.
This makes it possible to hand over user administration to internal IT without giving that team sight of business data.
Groups created by an IT admin are created without an owner — an owner is assigned afterwards in the group details.

The Validation API now also executes cross-table and multi-table custom SQL checks against the submitted payload, using an in-memory engine — no round-trip to a database is needed.

The data enrichment agent can now open image URLs and analyse them visually, for example to read missing attributes off product photos or scanned data sheets.

Row filters now support boolean columns with an "equals" condition and the values True and False.

Changes to rules and rulesets are now pushed to all users working in the same tenant, so a colleague's new or edited rule shows up immediately instead of after a manual reload.
API responses are additionally marked as non-cacheable, so browsers and intermediate proxies can no longer serve an outdated rule state after a reload.

Improvement workflows now show a Data out of sync state when the underlying data has changed since the last run, so it is visible when a result no longer matches the current data.
The "Workflows" column on rulesets is now called Linked actions.

Ruleset instructions are now taken into account when rule names and descriptions are generated, so generated rules follow the naming conventions defined for that ruleset.
Assistant status messages and in-platform navigation guidance now follow the user's profile language.
The chat has a "Scroll to bottom" button, and long unbroken strings no longer overflow the chat window.
Accepting or dismissing a rule suggestion is now confirmed explicitly.
The assistant now reads table context the same way the user sees it, including empty columns.

Profiling shows more rows and states clearly when not all rows were taken into account ("Estimated from X of Y profiled rows").
In issue tables, the cell-value viewer is separated from the rule-context tooltip, so both can be read without getting in each other's way.

Several user-interface inconsistencies were cleaned up (initials, picker dialogs, ruleset icon, dashboard labels).

Virtual tables are not offered for Microsoft Fabric sources, because Fabric does not support the temporary tables they rely on. Use a database view or a custom SQL rule instead.