TEAM v1.6.1

This new update on the Taxonomy of ETL Automation Metadata (TEAM) is meant to work with the Data Warehouse Automation schema v1.2, and therefore fully compatible with the Virtual Data Warehouse (VDW) version 1.6.2 upwards.

The bottom line is that, at this stage, the most recent versions of TEAM and VDW use the same version of the Data Warehouse Automation schema. TEAM can prepare the metadata, which is then saved in the format conform the Data Warehouse Automation schema. VDW can interpret these files and apply a variety of patterns against the metadata to generate code.

A very large number of underlying improvements in look & feel, exception handling and efficiency have been implemented in this version. It's a big release.

From a functional point of view these are the key changes:

• Json files can be exported for v1.2 of the Data Warehouse Automation schema.
• A new form has been created to configure the various Json segments one would like to add to the output.
• Separate connection management screens, with the ability to assign connections to source- and target metadata objects. This also means you can split up functional areas across connections, such as having a PSA defined across multiple technical environments.
• Context menus to create Json files and DDL statements from the various grid views.
• Event log to track what is happening.
• Enabled multiple environments to be defined, replacing the legacy dev/prod switch. You can now create any amount of environments and associated connections dynamically, and switch between then.
• Support for versioning across files, and maintenance of versions across Json files. It is now easier to switch versions.
• Enable / disable flag at Data Object level to only process certain parts of metadata.
• Initial support for transformations, adding hard-coded values in attribute mappings (Data Item Mappings)