Welcome to the main Dashworks Release Notes page. Details of the latest Dashworks Release are highlighted below.
If you would like to be notified by email when a new release is published, you can subscribe using the form on the right.
Enhancements to application management capabilities continue in Dashworks 5.4.5. All User Applications is a breakthrough in managing user to application associations in bulk, and the counterpart to All Device Applications. Both of these features continue to be developed, with new association types, filters and columns in the pipeline. The focus for automations and bulk update in this release has also been on applications with updates to Project Rationalisation and Compliance now available. Additional pieces of the Application Owner story are now in place with owners now being onboarded into projects. User permissions have now been applied to the Evergreen interface with the same rigour as they have always had in the legacy interface, giving administrators the confidence to open up access to the Evergreen interface whilst keeping control over the information can be edited.
Improvements to the reporting capabilities for applications continue, and All User Applications now shows relationships between Evergreen users and their applications in bulk. This works in a similar way to the existing All Device Applications functionality, showing relationships between users and applications in a list. This detailed view facilitates the in depth application analysis across multiple users that is necessary when planning change for specific teams or locations. Additional filters, columns and association types are planned for both All Device Applications and All User Applications over the coming releases, however the "saved list" filters means that all the existing filters on the user, device and application lists can be accessed in these association lists.
There are 2 new association types on All Device Applications: Entitled to Device Owner and Used by Device Owner. Previously, reporting on the relationships between devices and applications was straightforward as long as your data held direct app to device relationships, now you can perform this same analysis even if your data only contains application to user relationships (DAS-18092). This ensures that analysis of your application estate is unhindered by the type of data you have. There are also new columns and filters available for: Device Custom Fields, Application Custom Fields, Device Location.
There are 2 new ways in which you can bulk update applications: Project Rationalisation and Evergreen Compliance. Rationalisation is the categorisation of applications into Keep, Retire, Forward Path or Uncategorised. If Forward Path is selected then a target app to forward path to is also selected. Compliance uses the red/amber/green traffic light system and indicates whether an app has been approved for use in the organisation or presents a risk. Both of these were previously available to bulk update in the legacy interface, however now it is possible to leverage the powerful filtering capabilities of the Evergreen interface to choose which apps to bulk update.
Evergreen application owners are now onboarded into projects, and can be synchronised using the Resync button along with the application name. Application owners will be shown on the Scope Changes page when onboarding into a project, and there are new options in Scope Details to determine how and if application owners are onboarded. Readiness of an application and its owner do not cross-impact. You can also specify which applications a user owns in a project using the new Applications > Project Owned page on User Details. Properties of the Project Application Owner are also available as columns and filters on the Applications List. The next step with application owners is to introduce the ability to email them using application date tasks.
Both role and object security is now enforced on the Details pages for all functions that can materially change your data, such as relinking or updating a capacity unit. Role security affects the types of function that are available to a user, for example only members of the Project User Object Editor rold can offboard users from a project. Object security affects the specific objects that a user has access to. In order to make changes to an object, for example to their Capacity Unit, that object must be in a bucket that is owned by a team that the current user is a member of. Users with the Project Administrator role can update any object in a project, regardless of which teams they are in.
DAS-17783 Application list: Add additional filters to Device category
DAS-18360 Application, User & Device list: Application > Package Type, Inventory App ID
Dashworks 5.4.5 Released 3 February 2020
Dashworks 5.4.4 Released 2 December 2019
Dashworks 5.4.3 Released 7 November 2019
Dashworks 5.4.2 Released 27 September 2019
Dashworks 5.4.1 Released 2 September 2019
Dashworks 5.4.0 Released 5 August 2019
Dashworks 5.3.7 Released 28 June 2019
Dashworks 5.3.6 Released 7 June 2019
Dashworks 5.3.5 Released 17 May 2019
Dashworks 5.3.4 Released 25 April 2019
Dashworks 5.3.3 Released 4 Mar 2019
Dashworks 5.3.2 Released 7 Feb 2019
Dashworks 5.3.1 Released 4 Dec 2018
Dashworks 5.3.0 Released 6 Nov 2018
Dashworks 5.2.9 Released 28 Sept 2018
Dashworks 5.2.8 Released 5 Sept 2018
Dashworks 5.2.7 Released 2 Aug 2018