English
Breadcrumbs

Release note - beVault 3.9

We are thrilled to announce the release of beVault 3.9, bringing powerful new capabilities to our data vault automation tool. This version focuses on expanding platform integrations, improving automation capabilities, and enhancing the overall user experience with critical improvements to data lineage and modelling workflows.

Check out this release note to see what's new and stay tuned for new incoming releases in 2025 🚀

API Key Management

beVault 3.9 introduces comprehensive API key management, opening new horizons for automation and integration. This feature provides complete lifecycle management for API keys, allowing you to create, view, duplicate, assign specific rights, and delete API keys directly from the platform.

This powerful addition enables seamless automation of beVault operations and synchronization with your broader data ecosystem:

  • Synchronize your external data catalog: Keep your enterprise data catalog in perfect sync with beVault's metadata

  • Take control with AI agents: Enable intelligent automation by giving AI agents secure, controlled access to beVault operations

  • Streamline tool integrations: Connect beVault with your CI/CD pipelines, monitoring tools, and custom applications

  • Granular access control: Assign specific rights to each API key, ensuring secure and controlled automation

This feature transforms beVault from a standalone tool into a fully integrated component of your modern data platform, ready for the era of automated data management.

List of changes

API key management

  • Complete API key lifecycle management: create, view, duplicate/renew, assign rights, and delete API keys for tool integrations

Lineage visualization

  • Added a new lineage graph in the information marts' scripts based on the metadata encoded

Performance & stability

  • Reviewed state machine deployment to improve performance

  • Reviewed how actions are written in the Git repository to avoid project corruption

  • Reviewed the deployment of state machine to improve performances

UI/UX Improvements

  • Filter capability in dropdown lists

  • Review modelling environment tooltips

  • beVault branding set as default

  • Display deployment error messages

Bug fixes

  • Prevent the creation of multiple mapping when clicking multiple times on the save button

  • Resolved deployment modal empty project issue

  • Corrected state detection after unclean shutdown

  • Fixed state machine execution tracking discrepancies

  • Resolved L2 staging table dependency errors

  • Fixed popup persistence when deleting an information mart’s script

  • Increased reverse proxy file upload limit (removed 10MB restriction)

  • Updated used libraries to reduce CVEs

Small enhancements

  • Auto-initialize business names and descriptions from staging tables when creating satellites

Components' version

Component

Version

UI Version

1.11.2 🆙

Metavault Version

5.1.0 🆙

States Version

2.3.0

States UI Version

1.3.3 🆙

Workers Version

1.11.2

Fix Versions

Title Release Release Date UI Version Metavault Version States Version States UI Version Workers Version Summary
Release note - beVault 3.9.4

3.9.4

1.11.2

5.2.3 🆙

2.3.0

1.3.3

1.12.0

  • Improvement of performance on the /model call with numerous entities

  • Fix a bug preventing deletion of column in multi-active satellites

  • The limit of the hashdiff computation of multi-active satellites on IBM Db2 has been pushed to 32k.
Release note - beVault 3.9.2

3.9.2

1.11.2

5.2.1 🆙

2.3.0

1.3.3

1.11.2

  • Fix a timeout issue during the creation of staging tables in certain cases
Release note - beVault 3.9.3

3.9.3

1.11.2

5.2.2 🆙

2.3.0

1.3.3

1.12.0 🆙

  • Split the insertion in the meta schema to avoid overly long queries being blocked by some databases

  • Fix an issue with project creation

  • Fix an issue that prevented changing the case sensitivity of the business key for the hubs

  • Allow ANSI-encoded files in the worker SQLBulkInsert

  • Improve the performance of the generation of the meta schema, reducing the deployment time

  • Optimize calls to get the links and hubs, reducing the loading of mappings in the staging tables
Release note - beVault 3.9.5

3.9.5

1.11.2

5.2.4 🆙

2.3.1 🆙

1.3.3

1.12.1 🆙

  • Metavault - Fix an issue preventing the user from seeing his projects when the SSO doesn’t provide the name of the user

  • States - Fix several issues where failed executions remained in the Redis

  • Workers - exportToCsv - The OutputFileCulture is now correctly applied on numerical values
Release note - beVault 3.9.6

3.9.6

1.11.2

5.3.0 🆙

2.3.2 🆙

1.3.3

1.12.1

  • Metavault - Fix wrong type change detection issue affecting columns with String type and Length = 0, preventing unnecessary ALTER TABLE operations during deployment

  • Metavault - Add API call to search data package tables by name, data package name/id, or source system name/id

  • Metavault - Review and improve error messages in the application to make them more understandable for end users

  • Metavault - Fix default user rights for new projects to properly display projects on the homepage and assign correct module permissions

  • States - Fix archiving of executions to avoid race condition when using the worker ExecuteStateMachine
Release note - beVault 3.9.7

3.9.7

1.11.2

5.3.2 🆙

2.3.3 🆙

1.3.3

1.12.1

  • Metavault - Restored error message when attempting to update an existing mapping to a full load when one already exists for the same entity and source within a project

  • Metavault - Database Analysis Optimization: Limited database analysis to only schemas handled by beVault when deploying new versions, preventing errors on unmanaged database objects.

  • Security - Review access rights on some API calls
Release note - beVault 3.9.1

3.9.1

1.11.2

5.2.0 🆙

2.3.0

1.3.3

1.11.2

  • Fix an issue preventing the creation of columns in the information mart scripts

  • Fix a timeout issue during the creation of staging tables in certain cases

  • Review limits of description fields and in the meta schema (now 2000 characters) to avoid issues during the deployment of the tables in the meta schema.