MySQL - Fixed an issue with output to a container repository caused by a broken dependency update chain (kubernetes-client → YamlDotNet).
On the job details page, the Reports and Logs dropdown list now includes a View Gantt option, which allows you to view where time was spent during job execution. The option is only available for data generation jobs that used the Data Pipeline V2 process.
For the Conditional generator, fixed an issue where when a condition was based on other columns, the generator preview was not correct.
MySQL: Structural now restores preserved tables and triggers in the event of a failure.
SQL Server - Fixed a bug where history table settings and indexes were not appropriately replicated in the destination database.
Webhooks - new GitHub Actions webhook type - You can now configure a webhook that runs a GitHub action when the webhook is triggered. You specify the GitHub repository and credentials, and select the workflow. Structural then prompts you to provide the input values. The original type of webhook is now referred to as a custom webhook.
Webhooks - new schema change trigger type - You can now trigger a webhook when Structural detects a schema change. Previously, you could only trigger webhooks based on a job status.
Fixed an issue where nullable boolean environment settings were saved as null but could not be edited in the application.
Fixed an issue where nullable integer settings with default values could not be set to null when adding or editing.
MySQL - When a workspace writes output to a container repository, if the sql_mode cannot be determined from the source database - either from the SESSION or GLOBAL config - instead of leaving sql_mode unset, data packer now falls back to a sensible default value.
MySQL, Oracle: When calculating the percentage for subsetting target tables, Structural now uses the correct row counts.
Fixed an issue with unexpected behavior when the environment setting TONIC_STATISTICS_SEED is not set.
Updated the styling for Schema Changes view.
On Schema Changes view, added a button to display filtered tDatabase Viewo display all of the schema change columns.
Created a new generator for the Finnish Personal Identity Code.
You must specify a date range, and the generator will validate whether the input data falls within that period and if they are valid identity codes.
After that, a new Finnish Personal Identity Code will be generated so that the new birth date is within the selected range. A random valid century indicator will also be chosen, as well as a sequential number between 002 and 899.
Finally, the check digit will be calculated.
The new generator supports data consistency.
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.
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.
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.
