TEAM 1.5.4.1

Changes between 1.5.4.0 and 1.5.4.1:

• Removed some hard-coded index names
• Added correct Primary Key names (constraint names) for the sample data
• Added variable table and key prefixes for the sample data

This is tested with VEDW 1.4 and with the DIRECT build (master) as of today.

TEAM 1.5.4.0

Changes between 1.5.3.0 and 1.5.4.0:

• Minor bug fixing for validation on data sources that run off the PSA
• Added generation of configuration settings, DIRECT and default configuration settings can be easily restored from the repository management
• Minor bug in sample code, added 'renewal_code' attribute to support SAL samples

TEAM 1.5.3.0

Fully operates on both JSON and SQL Server, including versioning and virtualisation. This is an end-to-end code refactor that has improvements across the board. Specific functionality includes:

• Toggle between different environments, to switch between settings
• Revamped connection management
• Performance improvements, especially around activation of metadata
• Validation of metadata, including configuration of validation rules
• Persistence in JSON files to allow for better merging to a central repository
• Sample schema included in code, to quickly generate code using VEDW

TEAM 1.5.2.1

A large step into the new direction to leverage file based data stores (JSON).

• Moved the physical model metadata to the ETL generation metadata screen
• Enhanced graph handling
• Bug fixes around metadata saving
• Mnemonics and tab handling
• Supports JSON for table, attribute and physical model metadata

TEAM 1.5.1

• Setup component
• Created separate configuration screen, with supporting classes in the base form to get/set changes in configuration variables
• Created separation, and storage of, output and configuration paths to allow different configurations to be saved in separate locations
• Created support for JSON for saving, opening and editing Table Mapping and Attribute Mapping metadata. Note that a SQL Server back-end is still required for activation.
• JSON based data stores for the physical model storage (MD_VERSION_ATTRIBUTE table)
• Remove legacy Driving Key Indicator in the physical model, this has been superseded as metadata that is required in the Table Mapping. This is also a repository change because the info does not need to be stored anymore
• Update the repository version to v.1.4.1 to reflect the change to drop the DRIVING_KEY_INDICATOR