2024.3 Release Notes

Validatar has a new release! From major updates to minor bug fixes, we’re constantly working to improve your Validatar experience so you can continue to build trust in your data. Learn about what’s new below.

What’s New!

Test Execution Custom Actions

Users can now define custom actions on a standard test that are processed following each test execution. A custom action is defined as a trigger condition along with one or more steps that are executed when the trigger condition is applicable. The following trigger conditions are supported:

• Test Ran

• Test Resulted In <result-status>

• Test Overall Status Changed To <overall-status>

Each action step can be configured using several variables with details about the completed test execution. The following are the types of steps available:

• Run a Standard Test

• Set Linked Object Metadata Value

• Set Test Metadata Value

• Run a Script

• Run a Macro

• Send an Email

Benefit: Test actions provide the ability to create and automate custom workflows that run at the end of each test execution. The ability to run a Python script provides extensive options for integrating with 3rd party systems.

Test Execution Custom Actions is a licensed feature. Please contact sales@validatar.com for more information.

Launch Profiles From the Explorer

One-time profile retrieval can now be launched directly from within the Explorer. This allows the user to quickly populate one or more profiles on the selected metadata object(s).

Benefit: Users no longer need to switch over to the Settings > Data Sources area and create a separate profile set in order to run one-time profiles for a given metadata object.

Tests Support All Profile Types

Prior versions of Validatar only supported numeric scalar profiles within tests. Now any type of profile is available to be used when creating a test, including both scalar and multi-value profiles as well as numeric, string, and date profiles.

Benefit: With more profiles available to choose from, it’s easier than ever to create tests that monitor changes to your profiled data.

Updated Python Runtime

Prior versions of Validatar used Python 3.8 as the runtime engine when executing custom Python scripts and also within the Snowflake data processing engine. With Python 3.8 reaching end-of-life status in October 2024, both the built-in and Snowflake processing engines have been migrated to Python 3.11.

Benefit: Migrating to Python 3.11 extends support out to October 2027.

Updated .NET Runtime

With .NET 6 reaching end-of-life status in November 2024, Validatar, Validatar Data Agent, and Validatar CLI have all been updated to .NET 8.

Benefit: Migrating to .NET 8 extends support out to November 2026.

Data Agent Upgrade

Because of the .NET runtime change, updating the data agent cannot be triggered from within Validatar. To update the data agent, download and run the data agent installer. Make sure you run the updated data agent service using the same account as before so that prior Python libraries will automatically be migrated to the new Python version.

Highlighted Enhancements

• When defining a profile within a Data Source Template, users can now choose from either .NET Calculation or Python Calculation when entering a data source calculation expression instead of being limited to .NET calculations.

• When profiles are refreshed using a Data Source linked to a Snowflake Data Processing Engine, inserted or updated profile values are now processed entirely within the Snowflake environment instead of first being returned back to the Validatar engine.

• Profile storage location settings are no longer defined at a global level. Users can now specify whether to store latest profiles or historical profiles separately for each Data Processing Engine.

Bug Fixes

• Fixed standard test execution error when the test data set returns no records and the control data set is defined as comparing to prior test results.

• Removed duplicate rows in the Test Execution History and Tests reports for materialized tests that are linked to more than one metadata object in the test or control data sets.

• Fixed bug when saving User API Tokens that are scoped to a subset of the active projects.

• Changed how records are matched when using a control data set of Previous Test Results to fix a remote possibility that keys are not matched correctly between test and control data sets.