Platform rebrand: The platform has been rebranded Gimmal Discover.
AI/NLP for PII: Gimmal is introducing a static Natural Language Processing (NLP) model for PII that is designed to identify name and/or address information.
Microsoft 365 Legal Hold Support: Ability to enable or disable the ability to set Microsoft 365 litigation holds for Exchange and retention labels for OneDrive and SharePoint.
Connector and Agent assembly version numbers are now displayed on the Discover dashboard. Assembly numbers often are incremented when a patch is released for a Discover component.
The data-target grid now displays the date that a search was created and the date it was last updated.
The automatic update behavior for Connectors will default to obtaining the installation files from Discover’s Content Delivery Network (CDN).
Additional notification options have been added for clients using data owner retention
For clients using Discover’s automation feature, there is now an option to add or remove data owners/targets to existing policies.
New colored icons on the policy list page that use different shapes to indicate statuses for schedules (On/Off) or policy enabled/disabled.
Administrators may now optionally cancel targets currently processing (or pending) at the agent when a policy time out occurs.
Multiple data targets may now be selected when canceling a policy on the Policy Execution page (previously each target had to be canceled separately).
There is now support for generating summary reports when using the workflow Allow Partial option. Setting the Allow Partial option in a workflow is highly recommend as it will provide more efficient processing.
Data Governance automation has been extended with new tokens to update a policy by adding or removing owners.
There is now support for capturing all instances of a keyword when examining content. (Previously, Discover Agents stopped after locating the first occurrence of a keyword match.)
A new search continuity option is now available when creating an eDiscovery search. This setting determines how keyword matching will be performed by allowing three options:
Simple will stop searching after the first occurrence of any keyword is found
Complete will search for every occurrence of the keyword terms
Exhaustive will search for every occurrence of the keyword terms including honoring any proximity settings in the search syntax (i.e. Gimmal NEAR(5) Software).
Along with the new keyword options, there is also a new snippet option that determines if snippets will be returned for the first keyword hit only or for all keyword hits.
When creating a new eDiscovery collection, there is now an option to save workstation collections to a local folder first. This is very helpful in the event the network collection location is not accessible by the workstation (i.e. VPN access not available). When this option is configured, collected files will be stored locally until the network location becomes available.
A new option added to the “move message” action enhances support for partial matching on folder names by allowing that check to include all subfolders.
Multiple enhancements have been made to the Box Agent.
Discover now supports modern authentication (sometimes referred to as oAuth) for Microsoft 365 PowerShell calls. PowerShell is typically used to obtain information such as a list of mailboxes or retention policies.
Credential testers are now available in the Connector Status application for all supported cloud data sources. These testers are a useful way to validate that the entered credentials can successfully access the target content repositories.
Updates to the CDN download process used when new Connector/Agent versions become available now handle machines with older versions of the Microsoft .NET framework.
Notification emails now accurately indicate when Agents are installed or removed.
Resolved an issue with the incorrect identification of inactive targets.
Resolved an issue with Data Target and Owner searches being over-written when they are created manually from a template.
Fixed issue which caused the message subject to not be included in the fast search criteria for Exchange EWS messages.
Several fixes were introduced to address performance in the hub, policy sharing views, and other miscellaneous user interface elements.