July 2022 release notes – Onna Help Center

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 July 2022.

New features

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

Site manager app

The Site manager app gives you a way of host your project or client as separate sites, which keeps their data and users separate from others. It’s a more efficient way to manage your organization and helps complying with regulatory obligations and ensures confidentiality by letting each user access only information that’s meant for them.

Some examples of how you can use Site manager:

For your organization, when you need to access multiple sites within your ecosystem. For example, you can organize sites by business unit, location, or store data from a merger in a separate site.
As a services provider or consulting firm, when you want to set up on-demand collections for your clients.

The Site manager app is not active by default and requires a separate license. Contact your Customer Success representative or write to success@onna.com if you want to enable the Site manager app for your organization.

For more information on the Site manager app, visit our Help Center.

Usage metrics app

The Usage metrics app gives you precise insights on the usage and the data processing for each site. With that, you can keep track of how much your team is using Onna and estimate costs for billing purposes.

You can analyze metrics for the entire platform or for specific apps, such as eDiscovery. This will give you a more refined understanding of where usage is most focused.

For more information on the Usage metrics app, visit our Help Center.

Trailing wildcard (`*`) support in basic search

You can now use the asterisk symbol (*) when doing a basic search. When you place it at the end of a search term, it acts as a trailing wildcard operator. Now, if you search for bird*, you find words that start with bird, such as bird, birds, birding, birdman and so on.

Trailing wildcard used to search for an exact match. For example, docum* would only return results with the exact term docum. With this release that behavior also changes. You can use double quotation marks (“) to surround terms that you want an exact match for.

Improved features

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

Link Slack users who left a channel to those conversations

To collect a user’s data from a channel, our Slack Enterprise connector required them to be a member of the channel when the collection was created. If they left the channel before the collection was created, their identity wasn’t linked to the channel, which caused data not to be included in the collection. As a result, none of such data would be returned by searched or included in exports.

We improved the logic to evaluate whether a user was ever a member of the channel (public or private). As a result, data from users who leave a channel is now collected even when they leave before you create a collection in Onna.

Improved resource copy progress feedback

When copying resources, the message where the copy progress is shown was closing automatically after a few seconds. This didn’t allow users to understand whether their copy was still ongoing and what its progress was. We updated the behavior of the toast, so that it won’t be closing automatically anymore. This will allow users to have a clear idea of the copy progress and close the message manually when they no longer need that information.

OCR and large files performance improvements

The processing of large files and text recognition on PDF files was negatively impacting the performance of the processing pipeline. To change that, we made a few improvements to the components that played a part in the processing:

We assigned a dedicated set of resources to OCR processing on PDF files to ensure they don’t slow down other resources' processing
We updated the OCR processing engine to a version with significant performance improvements
We optimized the processing of child resources

Fixed issues

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

No feedback about addresses not found in Google Workspaces

We fixed an issue that caused users creating a Google Workspace collection not to be notified when users associated to a given email address were not found in Google Workspace. That happened when the address wasn’t all lowercase, which is the format that Google API expects such data in. Now, we ensure all email addresses are processed as lowercase to prevent the issue from happening.

Empty channel list when creating Slack collection

We fixed an issue that caused the list of channels to be empty when users created a Slack Enterprise collection and set it to not load multi-workspace channels.

Dropbox collections stop when user no longer exists

We fixed an issue that caused Dropbox Enterprise collections to stop with an error when the collection of a user who no longer exists was attempted. Now, when that happens, we log a 404 error, which allows the collection to continue.

No feedback on Dropbox collections failing because of removed member

When users create a Dropbox collection and a user, who was originally a member of a shared folder, is removed from it, the collection fails as Onna tries to collect new data. We fixed an issue that caused this error not to show in the audit log, which prevented users from realizing and taking corrective actions.

Exporting folders from search bar causes empty exports

We fixed an issue that caused exports of collections from folder-based applications like Dropbox or Box to contain no data when users created them after navigating to the folder they wanted to export.

Document family relationship not visible in folder exports

To determine relationships about documents that are members of the same family, our platform uses a value called GroupID. We fixed an issue that caused collections from folder-based applications like Dropbox to have an incorrect mapping of that value to each resource. This resulted in the inability to see the relationship between members of the same document family when exporting such data by selecting the option Include document family.

We fixed an issue that caused empty search queries to be saved when users selected the option Save & share search query in the search bar.