Skip to main content

TDM 3.12 Release Notes

· 4 min read
Jake Cave

3.12 Major Release Items​

What's New​

NEW FEATURE: AI Mask Review (AIMR)​

Get your Mask Configurations right before you run them. AI Mask Review checks your configuration against what profiling found in your data, and suggests fixes column by column.

AI Mask Review in action

  • Catch configuration errors before masking runs - Missing lookups, fixed values and date formats, duplicate entries, and unique or key columns that would break.
  • Faster masking runs - Advice on the best masking function, chunk size and table settings for large tables.
  • Don't like the advice? Dismiss it - Dismissed suggestions stay dismissed for that data source, unless the suggestion changes. Your feedback helps shape what AI Mask Review suggests next.

New configurations created by profiling are reviewed automatically. For existing ones, open Pattern Details and click AI Review. See the AI Mask Review guide for details.

Unique and nullable columns are now detected during profiling​

Profiling now records which columns have a unique index or unique constraint, and which columns are nullable. AI Mask Review uses this to keep unique columns unique after masking and to avoid masking key columns.

Database Health Diagnostics, expanded​

Diagnostics introduced in 3.11 now cover more of the supported databases, with fixes for Teradata, Sybase and DB2 checks.

Changes​

Validation now runs with every masking run

  • Validation runs automatically at the end of every masking execution, so every masked column is checked without a separate step.
  • Validation configurations and standalone validation scans have been decommissioned. See the Deprecation Notice below.
  • The compliance PDF and CSV reports have been updated to match.

Cleaner configuration screen

  • Secondary settings on the Data Configuration screen now sit under a collapsible Advanced Configuration section.

TDM Report

  • Long data source and configuration names are now shown in full.

Fixed value masking

  • Clearer log messages, and columns are skipped cleanly when no fixed value is set.

Fixed Issues​

Profiling

  • Oracle profiling no longer fails with ORA-12547 on SSL connections.
  • Teradata profiling now reports the correct Data Length for character columns.

Masking

  • Teradata DATE columns with an explicit FORMAT are now masked.
  • XML masking on Microsoft SQL Server now converts values back to XML correctly.
  • Using NULL as the flag string no longer causes a "NO Data In The Column" error.
  • Fixed bind parameters in an Oracle column comparison query.

Validation

  • "Na" values are no longer counted in the validation score.
  • Multi-condition cross-table masking on MySQL and MariaDB now validates correctly when a flag column is also masked.

TDM Report

  • Validation and masking executions are now listed in chronological order.

Database Diagnostics

  • Teradata "Long Running Queries" now shows only queries that are currently running.
  • Fixed Sybase tablespace utilisation and cache diagnostics.
  • Fixed SQL0206N errors in some DB2 diagnostic queries.

Deprecation Notice​

Validation Configurations and Standalone Validation Scans​

Validation configurations and standalone validation scans have been decommissioned in this release. Validation now runs automatically at the end of every masking run, using that run's masking configuration, so there is nothing to set up.

  • Validation can no longer be configured or run on its own.
  • Profiling no longer creates a validation configuration.
  • Results from earlier validation scans are still available to view.

What you need to know

  • You no longer need to create or maintain validation configurations. Any steps in your process that ran a validation on its own can be removed.
  • To check a result, open the Execution Console after a masking run. See the Validation guide for details.

Known Issues​

Unique_ID Masking

  • Others_UniqueID masking may not preserve uniqueness on some numeric columns.

Sybase Profiling

  • Profiling may fail when the profiling user has only column-level SELECT permissions on the specified columns.

PostgreSQL Masking

  • Many-To-One masking may fail on schemas whose names contain uppercase letters.
  • Self-referenced conditional masking may fail with an exception.

Delta Profiling

  • When using cross-language profiling, applying a delta profile scan to an existing Mask Configuration with Update may leave the Country and Language values blank on the existing rows. The newly added row is not affected. As a workaround, use Create to build a new configuration from the delta profile scan.