Tonic Textual release information

Bug fixes and other internal updates.

Bug fixes and other internal updates.

Bug fixes and other internal updates.

Added configuration to send server-side encryption headers for uploads to Textual's internal S3 bucket.

Bug fixes and other internal updates.

Fixed an issue with configuring the encryption keys to use for the Amazon S3 connection for a dataset.

When you filter the Datasets list, Textual now preserves the filters when you go to another page and then return.

Improved performance and quality of synthesis for dates and dates of birth.

Fixed ordinal-only date synthesis so repeated detected ordinal dates are replaced consistently and generated suffixes such as 21st, 22nd, and 23rd are formatted correctly.

Fixed XML redaction for xml:space attributes.

Fixed date replacement for unusually long extracted date values so that de-identification no longer fails during date conversion.

Bug fixes and other internal updates.

Fixed an issue with tables in .docx files not rendering previews correctly.

Fixed signature detection failures on oversized PDF pages.

Fixed V1 PDF image redaction colorspace failures.

For Okta SSO, Textual can now support the authorization code flow with PKCE. To enable this flow on a self-hosted instance, set SOLAR_SSO_OKTA_USE_PKCE=true. For the Cloud SSO configuration, check the Use PKCE flow checkbox..

Fixed an issue where PDF de-identification could fail while detecting styles for documents with large word payloads.

Improved PDF redaction style detection for documents that reference non-embedded fonts.

Make PDF stitching tolerate missing font resources.

Added support for custom CA certificates.

Fixed a dataset file preview issue where the first row of a CSV file was not visible.

For easier navigation, when you preview a dataset file, Textual now displays the main dataset details tabs.

Improved PDF table entity detection consistency so sensitive values in tables are classified more reliably across repeated scans.

When you use a Helm chart to install Textual, you can now set a custom database schema for the application database.

Fixed an issue with the scrolling for dataset file previews.

Fixed an issue where the Creator filter for custom entity types did not work.

Improved PDF de-identification font matching for text-backed redactions.

Copying settings from another dataset - On the dataset details page, a new Import Settings option allows you to copy the project and entity type settings from another dataset. You cannot copy settings from a dataset that you do not have access to.

The Date Truncation generator is now available as a synthesis option for all datetime entity types. Previously it was only available for birthdates.

On a self-hosted instance, you can now use environment variables to customize the schema name for the Textual application database. You can also configure whether to automatically create the schema if it does not exist when Textual starts.

Fixed an issue with pagination for model-based custom entity types.

Fixed an issue with the dataset file preview for CSV files.

Fixed an issue with deleting PDF redactions in a guided redaction project.

Improved NER benchmark report provenance diagnostics.

Updated the file preview for JSON output datasets to include a view of the JSON output.

Redesigned the file preview for datasets.

Bug fixes and other internal updates.

Users can now configure Amazon Bedrock as an LLM to use for the Textual Agent.

Bug fixes and other internal updates.

Bug fixes and other internal updates.

Bug fixes and other internal updates.

Textual Agent - The new Textual Agent provides an AI-based chat interface to Textual datasets. You can ask questions about the dataset data and detected entities, and configure entity type handling.

On the Datasets page, the Creator filter now always displays the current user at the top of the list.

Added an option to export an individual model-based custom entity type to an encrypted file. When you export the entity type, Textual provides the decryption key for you to copy. You can then import the entity type into another instance. When you import the entity type, you provide the decryption key. The imported entity type is inactive by default, regardless of its status in the original instance.