Verity Insights 7.2

Release date: 01 - 22 - 2026

Release 7.2 of Verity.Insights delivers significant enhancements focused on integration, performance, personalization, and automation. This version strengthens customers’ ability to connect their systems, optimize calculations, streamline operations, and improve data governance.

Webhook Notification to Queues

The platform now supports sending event notifications not only to HTTP endpoints but also to major queue systems such as RabbitMQ, Kafka, and MQTT. This enables real-time integration with customers’ cloud and messaging infrastructures.

See documentation

New Alarms

A new alarm engine allows customers to compare consumption across periods (day, week, month, year) and trigger alerts based on absolute or percentage deviations. Designed to support compliance with the French Tertiary Decree, it fully integrates with existing alarm types.

See documentation

Deactivate Calculated Variable

Users can now temporarily deactivate Calculated Variables to stop any processing especially useful during large data uploads. Reactivation is controlled and does not trigger a full retroactive recalculation by default.

Calculate Server Engines

Administrators can fully manage calculation engines (create, edit, delete) and assign them to client accounts. Account managers can then select the default engine or choose one per calculated variable from admin-approved options.

See documentation

Data Forwarding Service

A new, reliable service for automatically forwarding data to customer data lakes, with advanced error handling and reconnection capabilities.

See documentation

Data Ingestion Webhook Triggered

All file processors can now be triggered via a dedicated ingestion webhook, configurable at the FileTrigger level through UI or API.

No Processing Calculated Variable

Allows users to disable automatic recalculation when creating or updating a calculated variable essential for high-volume historical imports. Available via API or UI depending on environment settings.

Account Theming API

A new API enables account-level customization of themes and color palettes, improving brand alignment and user experience.

Enable a graph to be autonomous from a filter only

Before 7.2 a tile could only be either:

  • independent from all filters, or
  • dependent on all filters.

A single toggle controlled this behavior.

Now a tile can be made autonomous:

  • from the Time filter only
  • from the Geozone filter only
  • from both filters
  • from none

See documentation

API Impact
The dashboard controller now supports two new flags when getting, creating or updating a dashboard:

  • TimeFrameStandalone
  • GeoZoneStandalone The legacy flag Standalone becomes deprecated and will be removed from the API in a future version.

Compatibility rules:

  • If the legacy Standalone flag is present and set to true, then TimeFrameStandalone = true and GeoZoneStandalone = true.
  • If Standalone is present and set to false, then both new fields are set to false.

For new integrations, clients must only send TimeFrameStandalone and GeoZoneStandalone, and should stop using the Standalone flag.

Hard Delete Support for Managers

There are scenarios where a complete account reset is required, including the removal of all associated data, variables, sources, and sites.

The existing DELETE /sources endpoint supports a hard delete option that performs a full cleanup, but this capability has historically been restricted to Administrator roles.

To better support operational workflows and automation, the hard delete option is now available to Manager roles as well. This eliminates the need to rely on administrator credentials for routine cleanup tasks and aligns permissions with practical usage requirements.

This change improves usability for teams that frequently perform full environment or tenant deletions and need a secure, role-appropriate way to do so efficiently.

Bug Fixes

  • Fix Various UI/display issues
  • Fix Account deletion not working
  • Fix Zooming on a map reset the time filter
  • Fix Usage of the lastetLoggedInAccountId field in master data
  • Fix Specific customer issues