---
title: "Release Notes Version 5.5.0"
canonical: "https://docs.vaultspeed.com/space/VPD/3011674136/Release%20Notes%20Version%205.5.0"
format: markdown
---
**Table of Contents**

> Macro (toc)

## Introduction

Welcome to the release notes for VaultSpeed Version 5.5.0. This update brings you enhancements and improvements aimed at refining your experience with VaultSpeed. Explore the following sections to discover the key aspects and changes that this version brings, designed to streamline your data management workflows and offer greater flexibility in leveraging VaultSpeed’s capabilities.

## Vaultspeed Python SDK is available

The SDK is an extensive wrapper on top of the VaultSpeed API with a focus on the user experience. It can be used to easily automate many parts of the VaultSpeed application. Installation instructions, documentation, and examples can be found at [VaultSpeed SDK](https://vaultspeed.atlassian.net/wiki/spaces/VPD/pages/3496575098). Most, but not yet all, actions that can be done in the UI can also be done with the SDK. Access to the SDK requires an additional subscription.

## Added support for dbt (data build tool) on Databricks.

If your Data Vault target platform is Databricks, you can now generate dbt code using Vaultspeed.

![image](media://a249be2b-48e3-4bbb-a0db-ebc5bf15fc43)


## Improved the Google BigQuery integration

- Added support for **stored procedures**. This means you can generate native code encapsulated in stored procedures and no there’s no longer a need for an ETL tool.
  
- Added support for **Automatic Deployment**. This will require the Extended Agent, since the driver is not included in the Agent itself (due to licensing issues).
  
- Added support for **creating Schemas** a.k.a. Datasets.

## Added support for using the business views as the basis of the other Business Vault objects.

PITs, Bridges and Studio objects can now be build on top of the Business Vault Views instead of directly on the Raw Vault objects. This means that they will now also use the business names for their fields.

The below screenshot shows the Business Views are available to be linked to a PIT Template.

![image](media://395f823a-2ab0-4fe7-8933-930f9ffa49e3)


This also required introducing short and abbreviated names for the business views, as shown in below screenshot 

![image](media://527110cb-66d0-45d6-bda9-908cf565f795)

## Added support for OpenJDK 11 to the VaultSpeed Agent. It can now only run on OpenJDK 11

Support for **version 8 has been dropped in the latest release**. Follow the Agent Installation Instructions here [https://vaultspeed.atlassian.net/wiki/spaces/VPD/pages/3011084322](https://vaultspeed.atlassian.net/wiki/spaces/VPD/pages/3011084322) , making sure you have **OpenJDK 11 **installed and configured.

## Added the ability to specify a previous Data Vault Release when creating a new release.

This allows you to reset the Data Vault configuration to a state of an older release, or reset it altogether, instead of every release being based on the last release.  
If there is a production date, then this is limited to the production release and all releases after it.

![image](media://55dd20fd-8be5-4f2b-9838-6f36fe84cbd7)

## Added Documentation to the Delta Generation which describes which changes where detected. 

An extra markdown file will be generated in the Delta Zip file which contains a coarse overview of the type of changes detected by VaultSpeed between two releases.

![image](media://0d8d5717-076e-4f17-8111-528da1cc6d2d)

## Added the ability to specify a format mask for the CDC Timestamp attributes

Before, VaultSpeed used the General format mask, which could not be set differently per object.  
This can be configured through the CDC_TIMESTAMP_FORMAT_MASK Object Level Parameter. The CAST_SOURCE_ATTRIBUTES Parameter must be set to Y to enable the new CDC_TIMESTAMP_FORMAT_MASK Parameter. An example mask would be ‘YYYY-MM-DD HH24:MI:SS’

![image](media://653976f7-9e85-40f0-9aab-cc722ac3061d)

## Added the ability not to cast the CDC attributes (such as the timestamp and sequence) when CAST_SOURCE_ATTRIBUTES = Y. 

This is done by setting the new parameter CAST_VS_MANAGED_ATTRIBUTES to N. This parameter is Y by default and will only have an impact when CAST_SOURCE_ATTRIBUTES is set to Y.

![image](media://b510cdc5-0c4a-43d8-b142-14561f975b14)

## Detailed Overview

For detailed insights into each section, refer to the [Release Notes in Version 5.5.0](https://vaultspeed.atlassian.net/wiki/spaces/VPD/pages/3540779079) page.