Textual customers who use Okta on Textual Cloud must now configure an organization-specific sign-in URL in their Okta application. The redirect URL is displayed on the Single Sign-On tab of the Permission Settings page.
You can now create a Textual dataset that connects to a SharePoint repository.
The dataset details page now includes the option to share access to the dataset. Previously, the option was only on the Datasets page.
Support cloud storage and JSON output for datasets - When you create a dataset, you can now choose whether to upload files from a local file system or to select files and folders from Amazon S3. For Amazon S3 datasets, Textual generates the output to a configured output location. You can also configure a dataset to generate JSON output instead of redacted files. The JSON output matches the output currently produced by Textual pipelines. Note that after we add support for Azure and Sharepoint datasets, we plan to deprecate and remove pipelines.
On self-hosted instances, you can now include SSO group names in the value of the SOLAR_ADMINISTRATORS environment variable, which determines the assignment of the Admin (Environment) permission set.
For .txt, .csv, and .docx files, the file preview now allows you to select the entity type handling option. To select the option, in the right-hand pane, click the value, then click the handling option. The selected option is applied to all instances of that entity type.
The Textual REST API now provides endpoints to perform the following actions:
- Retrieve information about and share dataset access
- Retrieve information about permission sets
- Retrieve information about an organization’s users
- Retrieve information about an organization’s SSO groups
