New Features
-
New Special Permission: Manage Enterprise Sources It is now possible for authorized members to add enterprise sources in Onna. To enable this feature follow the steps below:
Step 1An Onna admin user adds the special permission ‘Manage enterprise sources’ to the member user from the ‘User management’ page.
Learn more about Managing User Roles and Special Permissions in Onna. |
|
Step 2An Onna admin user shares the correct authorized connection with the member who has the ‘Manage enterprise sources’ special permission
Learn more about Creating and Managing Authorized Connections in Onna. |
|
Step 3The Onna member with the new ‘Manage enterprise sources’ permission is now able to add a source using the authorized connection. They can see they have access to this authorized connection in the ‘Authorized Connections’ section of their user profile.
Learn more about Getting Started with Sources. |
|
-
Platform API General Availability
The Platform API is now generally available for all Onna enterprise customers. The API allows you to ingest data into the Onna platform for processing, as well as manage workspaces and folders. Visit the Developer Hub to find API reference documentation, sample code, and tutorials. -
Platform API Sandbox
Onna users can now create Platform API sandbox accounts. The sandbox is a temporary, isolated environment to test authentication, send sample API requests, and validate responses. The sandbox simulates Onna's production environment, with a few key limitations. For more information about the new Platform API Sandbox, visit the Developer Hub.
Improved Features
-
Onna will now process individual files up to 10 GB in size. Files larger than 10 GB in size will not be processed, but remain available for export. The previous file size limit was 2 GB. Learn more about How to review unprocessed files in Onna.
- When embedded links that require different credentials to access are unable to be processed the user will now receive a message indicating that the link was not able to be processed.
New and Updated User Guides in the Help Center
Getting Started
Admin
Connect and Collect
Search
Export
Fixed Issues
Platform
-
Beginning February 7, 2023, Onna is no longer offering Pay-as-You-Go pricing models or free trials.
-
The issue causing an inability to log in as users were rerouted back to the log-in page has been fixed, and users are now able to log-in as expected.
Admin
-
The issue causing random fails when enabling/disabling sources in the ‘Admin preferences’ section has been fixed. Sources can be enabled/disabled as expected.
-
We have enhanced the performance of identity mapping within the platform.
Preservations
-
The issue causing “shared with users”, who don’t have access to the original data sources included in a preservation, the inability to see the content of the preservation has been resolved. If a preservation is shared with a user they are now able to see the content of the preservation regardless of whether they had access to the original data source or not.
Connect & Collect
-
The issue causing users to see “Adding suspended” next to an authorized connection when adding is not suspended has been resolved and users will no longer see the message if access is granted.
-
The issue where there are unprocessed items from a Google Workspaces sync, but the user is unable to download a CSV of those unprocessed items has been resolved. Users are now able to download a CSV summary of all unprocessed items in a sync.
-
Datasources that are synced without any resources will no longer generate a ‘datasource ready’ email notification for users.
-
The issue leading to no results being returned when performing identity searches in Quip Enterprise has been resolved and identity searching is now returning results as expected.
Export
-
The issue causing incorrect metadata fields to show in exports has been resolved and metadata are now showing correctly upon export.
-
The issue in export listing metadata extensions incorrectly has been fixed. Metadata extensions are now listed correctly and if the correct metadata extension is not found, no file extension will be listed in the export.
-
The issue when exporting neighboring Slack conversations has been fixed and neighboring conversations are exporting as expected.
Comments
0 comments
Please sign in to leave a comment.