June 2023 Discover Maintenance Release
Feature Updates
Updated charting components in the Discover dashboard
Discover offers several areas where information may be presented in a graphical format. In this release, the components that generate those charts have been updated. This update includes the home page dashboards, Classification summaries, standard and trend Analytics reports, and eDiscovery result charts
![](../__attachments/186417155/image-20230609-181102.png?inst-v=2a7f6216-cd78-4207-9e5e-2ee0ab03c660)
Support for custom SharePoint properties
Clients may add custom SharePoint properties that they wish to examine in their Discover Dashboard. The following example shows the Connector tab on the Discover Settings page. In the section for Custom Data Source Properties, we’ve added a custom SharePoint property called Document Type.
![](../__attachments/186417155/image-20230609-181329.png?inst-v=2a7f6216-cd78-4207-9e5e-2ee0ab03c660)
Once the properties have been added, they can be synced to the Discover Workflow Editor by logging in, then opening the Session tab and selecting the option to Refresh Customer Features. This step will need to be repeated every time you add new Custom Data Source Properties in the Discover dashboard.
![](../__attachments/186417155/image-20230609-182239.png?inst-v=2a7f6216-cd78-4207-9e5e-2ee0ab03c660)
When creating SharePoint workflows, there is now a new decision available at the SharePoint Object level to evaluate a Custom Property
![](../__attachments/186417155/image-20230609-183111.png?inst-v=2a7f6216-cd78-4207-9e5e-2ee0ab03c660)
This example shows evaluating SharePoint objects to determine if they contain a custom property named Document Type that contains the value Accounting. Based on the presence of this property appropriate action may be taken on the SharePoint object.
![](../__attachments/186417155/image-20230609-184423.png?inst-v=2a7f6216-cd78-4207-9e5e-2ee0ab03c660)
An MSI version of the Connector setup for Windows
MSI installers can be helpful when distributing the Connector software using a deployment technology such as Microsoft SCCM.
![](../__attachments/186417155/image-20230609-184652.png?inst-v=2a7f6216-cd78-4207-9e5e-2ee0ab03c660)
When using the MSI installer package, it is designed to register the Connector software in the Windows Installed Apps list where it will be potentially visible to a desktop user.
Issues Addressed
Along with the features described above, a number of issues were resolved as detailed in the following table:
Issue Number | Description |
791023 | Added a setting to clean up pending files on a Connector device |
83184 | Fixed an issue causing a 404 error when using shortcut links in a ‘move to SharePoint’ option |
82769 | When removing an agent, change email notice to be more accurate |
82989 | Fixed an issue preventing files without an extension from being included in an eDiscovery collection |
82988 | Corrected a problem with SharePoint agent that was causing a ‘file type include’ to pull in older versions of MS Office files (i.e. doc when only docx requested) |
84689 | Fixed an issue causing a 500 error when adding a user with an invalid user id |
83923 | Update Gimmal Gear logo in dashboard |
83658 | Preserve NTFS file permissions when moving a file |
82768 | Fixed the multiple choice, multiple selection, and select list options for eDiscovery custodian questionnaires |
83652 | Fixed the export report rows option on policy reports page |
78825 | Removed .eml as an export option for Google eDiscovery collections |
85210 | Fixed a problem where non-owned data targets were available when creating a policy unless the customer had eDiscovery |
85647 | Fixed eDiscovery caching of OneDrive content |
83639 | Properly return report values generated by a workflow (for example %path-total-size% and %path-size% tokens) when applying sub token formatting with decimals (i.e. %path-total-size.format(‘00.00’)%) |
83645 | Require a value in the description field for a new automation |
84741 | Cancelled Owner/Target searches were hanging the hub scheduler |
85689 | Problems with large full-text sampling files not being returned for an eDiscovery search |
85687 | XML manifest files were not being generated in the collection path when eDiscovery collections ran |