Skip to main content
Version: 1.2.0

Release Notes

Fixed Issues – 1.2.0​

  • DSE-651 - Managing or exempting groups for an audit policy was not working as expected.

Known Issues​

  • DSE-514 - Selecting the Schedule tab on a disabled trigger causes the Save button to enable.
  • DSE-643 - Editing a FlashBlade device does not populate the Managed By field.
  • DSE-655 - The Threat Detections page can display User as unknown/unknown if a lookup fails in Active Directory.
  • DSE-733 - Saving a trigger with an invalid schedule results in both a saved message and an error message, but the configuration still saves.
  • DSE-737 - Database maintenance does not retain data correctly for triggers defined with in-between dates.
  • DSE-742 - The Threat Detections detail page shows the share name as part of the path. It should not.
  • DSE-765 - Resetting a trigger after changing from a one-time schedule to a recurring schedule with an invalid value resets back to a one-time schedule but leaves the recurring error displayed.
  • DSE-915 - Multiple audit policies managing the same folder can trigger Threat Detections multiple times.
  • DSE-956 - Changing the name or description of an existing trigger does not enable the Save button, but the trigger still saves.
  • DSE-976 - Switching between schedule tabs for two custom triggers causes the Save button to enable. A prompt appears to save changes when leaving the page, even though you made no changes.