Tonic Structural release information

When using Google SSO, if TONIC_SSO_DOMAIN is configured, only users with a matching domain are permitted to log in.

For an individual column on Database View or Table View, the option to apply a recommended generator is now included in the column configuration panel, under the generator selection dropdown. Previously it was a separate panel.

Fixed an issue with the Constant generator where the time could not be set for timestamps that included a time zone.

Bug fixes and other internal updates.

Bug fixes and other internal updates.

For workspaces configured with an upstream filter, fixed an issue where the invalid upstream WHERE clause error continued to display after the WHERE clause was corrected.

On Structural Cloud, the login screen now includes a Remember Me checkbox. When checked, you are not prompted to re-enter your email address the next time you return to the login screen. To switch accounts, click Back to email login. This returns you to the email entry page. You can then enter a different account.

Bug fixes and other internal updates.

Fixed the help icon display for fields in Document View.

In Collection View and Document View, fixed the view more examples button for fields inside arrays.

Oracle: GRANT statements for users and roles that do not exist in the destination are skipped

File connector - You can now configure a different file mount for each workspace.

Fixed an issue with batch schema change resolutions that involved generator removal.

To ensure uniqueness, the names of replacements created in Collection View or Document View now incorporate the data type.

PostgreSQL - Improved the performance of loading workspaces and testing database connections.

New Document View option to configure file connector JSON columns - For JSON file connector columns, instead of the JSON Mask generator, you can use the new Document View option to view the JSON structure and to assign generators to each combination of path and data type within the JSON. On the column configuration panel for a file connector JSON column, toggle Use Document View to the on position. Document View displays as a new tab on the workspace management view.

On the recommended generator panel for columns, fixed an issue where the preview data was not generated.

SQL Server - The TONIC_SQL_SERVER_SCRIPT_NO_FILE_GROUPS configuration setting is now respected when creating constraints in the destination database.

SQL Server - Improved column length mismatch handling for SQL Server bulk copy.

File connector - For a workspace that uses a file mount as a file source, you can now write the output files to Google Cloud Storage.

Oracle - Fixed an issue with the creation of synonyms that reference objects in other schemas.

File connector - On self-hosted instances, you can now configure a file mount as the source for file connector workspace files. After you set up the file mount, to enable the file mount option, you configure the file mount path as the value of the environment setting TONIC_FILE_MOUNT_POINT. For a file mount workspace, you can write the output to Amazon S3 or back to the file mount. Similar to cloud storage workspaces, you can select files or folders, and filter the file types to include.

SQL Server - Structural now skips creating Plan Guides that have null characters in their names.

SQL Server - Fixed an issue that caused data generation on Tonic Structural Cloud to fail when Tonic Ephemeral Cloud was the output location.

Bug fixes and other internal updates.

Bug fixes and other internal updates.

Database View now uses the full width of the browser.

Bug fixes and other internal updates.

SQL Server - Added additional enhancements and a new configuration setting to more gracefully handle null characters in object names.

MongoDB - Enabled the Timestamp Shift generator.

MySQL - In MySQL workspaces, you can now provide custom names for the destination schemas. Note that if you create the database schema yourself, you cannot rename the destination schemas.

Bug fixes and other internal updates.

MySQL - Resolved an issue that occasionally caused errors when getting the schema scan history.

PostgreSQL - Improved the performance of connection tests for large databases.

Bug fixes and other internal updates.