March 06, 2018 / by jburks / In release-notes /

Release Note — v7.2.0

A comprehensive list of various enhancements and bug fixes are mentioned below:

  • Data can now be filtered as per seconds in $Duration field.

  • Users can now filter data based on custom time intervals using $DateTimeField and $SystemTstamp.

  • timeslice feature is now available for field $SystemTstamp using $DateTimeField.

  • Pivot data can now be sent in the email itself while raising a module via template.

  • All error logs are now consolidated within a single log file. Although, separate log files are also available for individual components/services. These files can be found within /dnif/<Deployment-key>/logs/ directory.

  • Memory Cache information for DS can now be accessed by executing a fetch query on metrics store.

  • Within a Dashboard, users can now add widgets from a different Scope.

  • Improper redirection was observed while saving entities (Modules, Templates, Reports and Workbooks). This is now fixed.

  • Current time for selected time zone is now visible within INBOX page.

  • The INBOX page now supports hierarchical comments for an incident.

  • Once an incident is created, there is a provision for users to assign an incident to themselves via the Take Ownership option available in the INBOX popup page.

  • Users can now create Modules from INBOX page itself.

  • Users can now easily copy the slug name of a package upon selecting the copy slug button while viewing package information.

  • Alert emails will now be devoid of special characters and UNICODE characters.

  • Author details are now visible for every component (Module, Widget, Dashboard, Template, Report) created on DNIF Cloud.

  • Rating feature for package is now fixed. Previously, users were unable to provide 5 star rating to a package.

  • There was an issue in the way resultset was displayed for the directive _field, which is now fixed.

  • In some cases, the email address of the user to be notified was not visible properly when a module was raised.

  • When a public repository was synced, the original author information of the entities was updated with the user details who performed the Sync operation.