Tonic Structural release notes

v1011 - v1017
v1011 - v1017
Removed
October 27, 2023

Apply recommended generators to multiple detected sensitive columns - On Privacy Hub, a new banner displays the number of detected (not manually designated) sensitive columns that are not protected. From the banner, you can display the list of columns, grouped by sensitivity type. For each sensitivity type, for the selected columns, you can:

  • Apply the recommended generator
  • Ignore the generator recommendation
  • Mark the columns as not sensitive
  • There is also an option to apply the recommended generators to all of the selected columns across all of the sensitivity types.

    Writing destination data to container registries (beta feature) - For data connectors that support it, you can now configure a workspace to write destination data to container artifacts on a container registry instead of to a database server. The Job History view provides access to the generated artifacts for each job.

    Other updates

    Fixed an issue where generated API documentation did not exclude endpoints and schemas from API versions other than the version being viewed.

    Fixed an issue where the Protection Audit Trail displayed the incorrect override status of columns in child workspaces.

    On the System Status tab of Tonic Settings, fixed an issue where the Data Sharing section incorrectly showed logging as unable to connect.

    Databricks

    • On the table mode selection panel, for workspaces that write to Databricks Delta tables, disabled the Error on Overwrite table configuration for tables. The setting is not used in this case.

    File connector

    • In the file group configuration, added options to skip lines from the beginning or end of CSV files.

    MongoDB

    • On Collection View, fixed an issue that prevented array fields from displaying in the Hybrid Document View of a collection.

    Oracle

    • For new workspaces, the Preserve source database file storage preferences setting is now off by default instead of on. Existing workspaces are not affected by this change.