Consistency for many generators, including the Name generator and the Address generator, now ignore whitespace when deciding consistency. This helps when these generators are applied to fixed width columns, such as char(40). This update does not affect other generators, such as the Character Scramble generator and Timestamp Shift generator.
Name generators that are consistent with another column now derive each part of the name (first, middle, and last) from the corresponding part of the source value. Because of this change, the output from the Name generator might differ than the output generated by earlier versions, including for workspaces that have a fixed statistics seed. Within the same version, the output is still deterministic and consistent.
v1806 was not released because of technical issues.
Snowflake - For Snowflake on AWS, you can now use an assumed role for the credentials to connect to the temporary storage location on Amazon S3.
Fixed an issue where users on the same machine and browser shared a Structural Agent chat.
The Finnish Personal Identity Code generator no longer rejects valid Finnish PICs that use the century indicators B–F and U–Y.
The Finnish Personal Identity Code generator no longer rejects codes that contain an individual number in the reserved test/temporary range (900–999). These are now accepted and masked within their own range. A test PIC always maps to another test PIC, and a real PIC always maps to another real PIC.
The Finnish Personal Identity Code generator no longer rejects source PICs that have a date of birth that falls outside the configured date range. The date range now only controls the dates of birth in the generated output. Source values that are outside of the range are accepted and mapped to a date within the range.
The Finnish Personal Identity Code generator is now available for all data connector types. Previously it was only available for PostgreSQL and MySQL workspaces.
For the Alphanumeric String Key generator, added a configuration option to preserve a specified number of characters at the end of the source value.
Spark and Databricks - For the Regex Mask generator, before a job runs, Structural now rejects patterns that mix named and unnamed capture groups, or that use .NET-only syntax such as (?'name'...) or (?#...). This is because the .NET and Spark/Java engines handle these patterns differently. Instead, use only named or only unnamed groups. The validation applies only to jobs that run on the Java/Spark engine, like Spark (Hive SDK) sources and Databricks on Spark 3.3 or later. This limitation does not affect other data connectors.