Release note - beVault 3.7

We are thrilled to announce the release of beVault 3.7, bringing significant enhancements to our data vault automation tool. This version focuses on improving user experience, and enhancing data accessibility with a complete rework of the Graph Editor.

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

Graph Editor rework

At the heart of beVault 3.7 is a completely reimagined Graph Editor within the Build module. This overhaul is designed to tackle the challenges of managing large-scale data models while significantly enhancing metadata accessibility. Key improvements include:

• Advanced filtering system with intuitive search capabilities

• Visual enhancements, providing clear graphical cues to navigate complex models effortlessly

• Streamlined access to entity metadata through an optimized interface

• Expanded export options for comprehensive documentation and reporting

These enhancements work in concert to deliver a more intuitive, efficient, and powerful data modeling experience, enabling you to handle even the most complex data architectures with ease.

List of changes

• Graph Editor

  • Add the possibility to filter based on the entity type

  • Reference tables can now be seen in the graph

  • Add the possibility to filter based on the sources the entities are mapped to

  • Add the possibility to search for an entity based on its name

  • Add a descriptive panel for the entities to provide quick access to its metadata

  • Add the possibility to open the dynamic tab of an entity directly from the graph

  • Add the possibility to export in SVG format

    • The export now takes into account the current filters

• Workers

  • SqlToJson

    • Allow to export rows in multiple files instead of an array

    • Possibility to export SQL Arrays in the JSON

  • Http

    • Possibility to not put the content of the response in the result of the activity

• Information marts

  • The IMs' metadata is now deployed in the meta schema of the environment’s database

  • Automatic generation of a state machine in the orchestrator for each information mart to execute their scripts

• User experience & quality of life

  • Changes unique checkboxes by choice buttons

  • Preselect the type “Relationship” when creating a link

  • Prefill the staging table name with the following format : [Source code]_[Data package name]

  • Preselect the hub mappings while mapping columns from a staging table to a link

  • Automatically open the execution of a state machine when starting a new one

• Minor UX/UI improvements & bug fixing

Components' version

Fix Versions