Hi there,

We'd like to share with you what’s new in Onna for this month. This article lists what’s new, improved, or fixed in the platform as of August 2022.

New features

These are the new features you can enjoy in Onna starting from this release.

Onna Platform API

Our new Platform API enables programmatic access to the Onna platform services so that you can push any data into Onna even without a connector. The initial release allows you to manage workspaces and folders, and ingest raw files or ticket data from customer service and helpdesk applications like Zendesk, ServiceNow, JIRA, HubSpot, and Salesforce.

The Platform API is available to all Onna Enterprise Plan customers and accessible by users with a developer role.

Visit our new Developer hub to find API reference documentation, sample code, and tutorials.

Customize site name

Users can now customize the name of their sites. The name becomes visible by the site members and in the site list of the Site manager app to users who have access to it.

For more information, see Update site name.

Improved features

These are the improvements to existing features that you will see starting from this release.

Export normalized email addresses

Previously, when exporting email data collected from applications like Outlook or Gmail, the addresses in the From, To, CC, and BCC fields were exported in JSON format. They now follow email normalization best practices, which makes email threading possible and the fields readable by other eDiscovery applications when data is exported.

Export email send date as individual field

Emails don’t generate MD5 hashes, that’s why eDiscovery softwares rely on an email’s metadata for deduplication, such as the send date timestamp. We’re adding the ability to export the Date sent metadata, which was previously exported together with other metadata in one catch-all field and in JSON format, as an individual field that is readable by other eDiscovery applications when data is exported.

Deprecated features

These are the features that you will no longer see in our platform starting from this release.

Google connectors consolidation

We’re focusing all our efforts in improving the experience of the Google Workspace connector, which includes the possibility to collect from Gmail and Google Drive. For this reason, we’re deprecating our personal Gmail and Google Drive connector. All existing collections will continue working and creating new collections will still be possible with the Google Workspace connector.

Google is also sunsetting Google Hangouts, so we’re deprecating our connector too.

Fixed issues

These are the most relevant bugs and issues that we fixed with this release.

Search query disappears from search bar when searching workspaces

We fixed an issue that caused search terms to disappear from the search bar after users ran a search in their workspace. This also prevented users from saving their workspace-level search queries.

Preserving Slack data in place causes 401 error

We fixed an issue that caused a Something went wrong, try again error when creating an In-place preservation that included Slack data. The issue was caused by the app trying to use an old authentication token when a new one was available.

Inactive user role and permissions fields

We fixed an issue that caused users' Role and Special permissions fields to be greyed out when admins accessed the User management section, preventing them from updating the user permissions. The issue was caused by requests being processed in an inconsistent order when loading the page.

Error when collecting deleted private chats from Microsoft Teams

We fixed an issue that caused 404 errors when trying to collect from Microsoft Teams. The issue occurred when private chats that were being collected were deleted from Microsoft Teams.

Error when selecting Microsoft Teams chats with no ID

We fixed an issue that caused an error when creating a Microsoft Teams collection and selecting the chats to collect. The issue was caused by the connector not ignoring attachments to chat messages that lacked an ID.

Error when processing large Slack resources

We fixed an issue that caused large Slack resources not to process when their payload was too large. This was caused by the payload being logged in the collection report, which has a payload size limit for security reasons. The fix consists in detecting whether the report is too large and chunking it as much as possible.

Google Workspace collection settings are processed multiple times

We fixed an issue that caused Google Workspace resources to be processed multiple times during collection. This caused the collection not to complete because the connector wasn’t able to process other resources.

Slack conversation creation date changes

We fixed an issue that caused Slack conversations creation date to change and show the edit or delete date. This happened when edits or deletions to a conversation message happened on a different date from when the original message was sent.

Slack thread parent message excluded from export

We fixed an issue that caused a thread’s parent message in Slack conversations to be excluded from the export when users selected the Export conversations as single messages option. This also included the parent message’s native files when users selected the Include native files option together with the other.

Newly created users can’t set their password

We fixed an issue that prevented users from setting their passwords from the link provided in the invite email.

Error when creating In-place preservations with large number of custodians

We fixed an issue that caused a Something went wrong. Please try again later error to show when users were creating an In-place preservation that required to load a large number of custodians.

Creation date changes when deleting or editing messages in Slack conversations

We fixed an issue that caused the creation date of a conversation to change when custodians deleted or updated a message in a Slack conversation. When that happened, the creation date started to match the date of the edit or deletion.

Inability to delete avatar picture

We fixed an issue that, once users started using an avatar picture, prevented them from leaving it empty again. When they tried to save the avatar after deleting the picture, their settings weren’t saved.

Slack preservation file count shows 1 extra file

We fixed an issue with the Preservation feature and Slack that caused 1 extra file to be added to the total file count. The issue was caused by our platform incorrectly counting a system resource as a file.