--- title: "May 2026" slug: "may-2026" updated: 2026-09-22T06:59:09Z published: 2026-09-22T06:59:09Z canonical: "docs.databee.buzz/may-2026" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.databee.buzz/llms.txt > Use this file to discover all available pages before exploring further. # May 2026 ## Feature Enhancements - Product branding is updated to display trademarked names for DataBee RiskFlow™ and DataBee BeeKeeper™ in key navigation areas. - Test connectivity supports JWT-based authentication, improving validation and setup for supported integrations. - Compliance remediation actions workflows are updated to support Iceberg data lake. - Performance improvements are made to Exposure Management and Inventory experiences. - Feed configuration forms dynamically display and validate input fields based on the selected event type. - Device encryption status is available in CDP Device through the new is_encrypted field. - Added Cloud Security Posture Management (CSPM) reporting for Azure Secure Score report, providing visibility into secure scores, resource health, compliance trends, and subscription-level posture metrics. - Configuration rules that use editable arrays display as expandable cards with inline editing, reordering, duplication, deletion, and simplified item management. - The Business Continuity report view is enhanced to support person-level reporting using Resolved Person ID from the User Entity view. - The Vulnerability Compliance report supports additional custom fields from OSINT inventory data. - Administrators can configure multi-tree organizational hierarchies through the new allow_multi_tree_org_hierarchy setting in User Entity configuration. - Owner and organizational hierarchy information in the Vulnerability Compliance report is now resolved using a person-typed user. - Collection creation supports CDP tables, with schema-aware table selection for improved query and search workflows. - Data quality alert emails include the configured data source label alongside the data source ID, improving readability and clarity. - Newly created conversations now immediately appear in RiskFlow chat history, ensuring chat history updates without requiring a page refresh. - ServiceNow integration connections can be enabled, disabled, or deleted from the Integrations configuration page. ## Bug Fixes - The issue where Whistic test connectivity checks could fail with a "Result store not found within batch context" error is fixed. - The issue where unavailable views could prevent workflow editing is fixed. Users can continue editing workflows and update the view selection when needed. - The issue where the Last Edit field was not displaying correctly in Workflows is fixed. - The issue where potential owners remained visible after an owner was selected is fixed. - The issue where duplicating a console from the Security Overview page could fail with an error message is fixed. - The issue where searches using collection identifiers could return incorrect results is fixed. - The issue preventing the creation of Business Continuity Management policy documents is fixed. - The issue where policy documents do not deploy for certain enabled dashboards is fixed. - The issue where bar charts intermittently fail to load until the page is refreshed is fixed. - The issue where Cyber Vulnerabilities data can become stale and not reflect the latest ingested vulnerability findings is fixed. - The issue where multiple active organizational hierarchy records can be created for the same user is fixed. - The issue causing incorrect active entity counts in Iceberg-based CDP views is fixed. - The issue where the Integrations page fails with a 500 error for new tenants is fixed. - The issue where workflow run notes (ServiceNow ticket details) are not displayed in the DataBee UI for successful executions is fixed. - The issue where Azure Secure Score records displayed missing subscription names is fixed. - The issue where RiskFlow returned inaccurate results when querying Tableau data is fixed. - The issue where Qualys vulnerability records had empty CVE identifiers in the Cyber Vulnerabilities data is fixed.