Data Dynamics Enterprise

This version of the Data Dynamics Enterprise product provides several new features, improves usability, and extends several capabilities. Many of these improvements were made in direct response to suggestions from our customers.

--Improves handling of 0 KB Microsoft Office files during NTFS tag Collection [74457]-- Prior to this hotfix, if you created and ran a Metadata Scan policy in Data Dynamics Enterprise that included 0 KB Microsoft Office files, such as .docx, .xlsx, or .pptx files, and where the CollectNTFSTags option was enabled, the policy would potentially fail. These 0 KB files appear to be Office documents but contain no data or internal structure, which makes them invalid files. Because these files do not contain the expected content of a normal Office document, Data Dynamics Enterprise may not be able to retrieve NTFS tag information from the files. As a result, these files could fail during metadata processing, and Data Dynamics Enterprise would return a misleading error message. With this hotfix, Data Dynamics Enterprise now properly recognizes invalid 0 KB Office files and provides a correct error message to let the user know that NTFS tag collection is not supported for files of this type.

--Improves Data Dynamics Enterprise displaying full names for users where available in Active Directory [57714]-- In previous versions of Data Dynamics Enterprise, the user interface displayed only Active Directory usernames for users when listed in tables or other views. This version enhances the visibility of individual users within the Data Dynamics Enterprise user interface, displaying full names for users in Data Dynamics Enterprise where name information is available in the connected Active Directory installation.

--Allows sorting and filtering in all areas of Data Dynamics Enterprise user interface [70205]-- In addition to the improvement above, Data Dynamics Enterprise 2.0.3.1 now allows users to sort or filter their data in all areas of the product, regardless of the view. This functionality includes standardized icons to make sorting and filtering easier to understand and use across the Data Dynamics Enterprise user interface.

--Resolves issue where the Dashboard does not automatically update when users complete assigned Risk Mitigation Tasks [64245]-- Previously in Data Dynamics Enterprise, when a Data Owner user completed a Risk Mitigation Task in the Dashboard, the Risk Mitigation Task area did not automatically update to show that the risk had been mitigated. This could potentially cause confusion with Data Owners, making those users think that their assigned tasks had not been completed. With this version, Data Dynamics Enterprise now automatically updates the Risk Mitigation Task area of the Dashboard once a user completes an assigned task and also updates the associated risk displayed in other areas of the Dashboard, where applicable.

--Resolves issue where the Risk Mitigation Task area of the Data Dynamics Enterprise Dashboard may display an incorrect count for Overdue tasks [73607]-- Data Dynamics Enterprise 2.0.3.1 resolves an issue where, if you assign one or more actions to Data Owner users using a workflow, when you go to the Data Dynamics Enterprise Dashboard after those actions are due, the Overdue count in the Risk Mitigation Task area may incorrectly display a count of 0. With this version, Data Dynamics Enterprise now correctly displays the number of overdue actions for the Overdue count in the Risk Mitigation Task area of the Dashboard.

--Resolves issue where Metadata Scans may remain in In Progress for an extended period of time [72746]-- Data Dynamics Enterprise 2.0.3.1 resolves an issue where, if you create and run a Metadata Scan policy, the scan may appear to have completed successfully in the Policy Execution History, while the scan itself remains in an In Progress state. This occurs because of the way in which Data Dynamics Enterprise handles invalid date/timestamps on scanned files. When the Universal Data Engine encounters a file with an invalid timestamp, it scans the file and sends the file metadata to Elasticsearch, in an effort to gather all the data possible. However, Elasticsearch may not be able to index the file metadata because of the invalid timestamp, which can cause the data engine to incorrectly see the scan as still running. With this release, Data Dynamics Enterprise now correctly returns an error for files with invalid timestamps and allows Metadata Scan policies to complete successfully.

--Resolves issue where owner field is empty in scanned AWS metadata [72913]-- This version of Data Dynamics Enterprise resolves an issue where, if you create and run a Metadata Scan policy on an Amazon Web Services (AWS) data store, the object metadata may display no information for the object owner field. This occurs because Amazon removed the Owner.DisplayName field from its APIs, and Data Dynamics Enterprise used that field to populate the owner field in Elasticsearch. With this release, Data Dynamics Enterprise now uses the Canonical ID provided by the AWS SDK to populate the owner field.