New workspace Version History with filter and restore options
For each workspace, the new Version History displays the list of changes to:
Column sensitivity
Generator assignment
Generator configuration
Table mode assignment
Post-job scripts
Subsetting configuration
The Version History is intended to replace the Protection Audit Trail that was on Privacy Hub, as well as the undo and redo options. We will remove those items soon.
To display the Version History, in the workspace heading, click the clock icon.
The changes are grouped by calendar date and then by time slot. For each change, the list includes:
The type of change
The user who performed the change. If the Structural Agent performed the change, then it is listed as performed by the Agent on behalf of the user.
You can filter the list to show:
Changes that occurred within a specified timeframe
Specific types of changes
Changes that were made by specific users
You can restore the workspace to a specific version.
For data connectors that upload objects to Amazon S3 - including Amazon Redshift, Databricks, the file connector, and Snowflake - to ensure that tags are applied, the IAM user must have s3:PutObjectTagging on the destination S3 bucket. To prevent jobs from failing, when the permission is missing, Structural logs a warning and continues to upload without tags.
Salesforce - GlobalValueSet picklist constraints are now lifted and restored. Managed-package fields are skipped.
Salesforce - Fixed an issue where Tooling API queries might not have returned all records.
By default, self-hosted customers who have not either set up an LLM or opted out of LLM use are connected to Structural’s hosted LLM. This enables self-hosted customers to have immediate access to Structural’s AI-powered features. For existing customers who upgrade to this version, sharing of sample data with the LLM is disabled automatically.
Hosted LLM for self-hosted customers - Structural now provides a hosted LLM for that self-hosted customers can use instead of connecting to their own LLM.
For the Date Truncation and Timestamp Shift generators, you can now optionally configure a fallback generator, to accommodate datetime values that the generator cannot process. The available options are Fail on error (the default), Passthrough, Constant (where you provide the value to use), or Null.
MySQL - Tailscale tunneling is now supported for MySQL.
Fixed an issue where the IBAN generator would throw errors when the source value was not a fully valid IBAN. Validation has been relaxed for non-primary key fields or when consistency is not enabled, allowing a new IBAN to be generated when:
The bank code is preserved. The source value no longer needs to be a valid IBAN. However, the bank code is only preserved only if the source contains a valid country code and a bank code of the correct length.
The country code is preserved.
The country code is missing. When the source value's country code is unknown or missing, the generator now falls back to a randomly selected valid country code.
Added support to use the Structural agent to diagnose datasource connection test failures. For failed tests, an Ask AI prompt allows you to ask an LLM to troubleshoot the issue and suggest next steps.
Controlling AI access to sample data - Added an option to control whether AI features have access to sample data. When true, AI features can retrieve sample data from the workspace source database to improve functionality and output quality. When false, AI features only have access to database schema information. The default value is true.
For self-hosted instances, the option is on the Structural AI Settings page or as the environment setting TONIC_LLM_ENABLE_SAMPLE_DATA. On Structural Cloud, the option is on the Organization Settings page as TONIC_LLM_ENABLE_SAMPLE_DATA.