Skip to main content

Dashworks Release Notes 5.6.8

This release contains a number of key improvements including being able to log in with an Azure Single Sign On, detailed device histories and forward pathing when tracking computers through the hardware lifecycle, department coverage target percentages when setting ring scoping for a project, and the configuration of conditional components that can be used in the Self Service portal.

Highlights​

Single Sign On​

screenshot

Users can now log into Dashworks using their Microsoft 365 account as Azure Single Sign On (SSO) is supported. This reduces the need for users to manage different logins to different systems and gives administrators control to enforce password strength and multi factor authentication in line with their existing corporate policies.

Device Forward Pathing​

screenshot

As part of any hardware lifecycle process, devices must be replaced when they reach the end of their warranty or lease. Mapping a device to its replacement is now possible in Dashworks. This means that decisions and actions around suitable replacements, device disposal and recycling devices after users leave can all be managed within Dashworks. You can see the full history of how devices have been replaced in the past. Managing devices from manufacturer to end of life gives a complete solution for hardware lifecycle management.

Hardware Lifecycle displays the history, current status, and future ‘path’ of a device. For example, a computer could be on order, in stock, in use, due to be replaced or upgraded, or retired from use. Additionally, Lifecycle Status enables you to view and manage the relationships between devices, enabling you to track which device was replaced with which, any Next Replacement devices, and, where appropriate, a planned ‘forward path’. You can also use Lifecycle filters to track device lifecycles.

Task Conditional Logic​

screenshot

Self Service now has the flexibility to present different components to the end user based on their interaction with previous components. For example if a user indicates they do not own a device then further questions about that device will not be shown. This allows self service to be much more customisable to cover different scenarios. Conditional logic is based on underlying tasks in a project. For each task available, you can choose which other components are revealed.

Department Coverage​

screenshot

When determining which devices to include in the pilot for any project, one of the goals is to ensure that those devices represent a diverse cross-section of your enterprise. Dashworks now includes the option to ensure that devices are selected from either all or some of the lines of business across your organisation, using configurable options. You can specify coverage targets as a percentage for any department you choose, at any level of your departmental hierarchy. A simple red and green system shows whether coverage targets have been achieved in any particular ring within your project.

What's New​

  • Hardware Inventory Import is a Data Import that replicates Distribution Hierarchies > Generic Import from Senior. You can now define hardware inventory imports in Evergreen > Admin.

  • You can now create, edit, and perform an automated bulk resync of buckets, capacity units and/or rings for objects between Evergreen and a project.

  • Users can now request list exports, and can receive an expiring download link by email.

  • Error messages for broken components are now displayed to end users in the correct language.

  • Names of Archived objects are displayed in Evergreen Self Service.

  • Evergreen Details > Tasks > Task Emails: Email Due or Sent shows the time in addition to the date.

What's Changed​

  • Task Names and Task Value Names in Self Service are now displayed in the Self Service default language and not the project default language if the relevant translation does not exist.

  • Self Service: “Allow user to change capacity unit” mode can only be select for one component for each project within a single self service.

  • Legacy UI login and splash screens redirect to the Evergreen login page for authentication.

  • Evergreen Details: The Purchase Info page has been moved to the Lifecycle section in the menu.

  • Custom fields: Allow update via API check box has been hidden, as it is not yet implemented.

Known Issues​

  • Return URL functionality is not handled for SSO authorization. SSO users accessing Dashworks via specific URL will not be returned to the original URL after they have logged in. This will affect. SSO users accessing self service in the legacy UI, if anonymous logins are not enabled.

  • In certain circumstances, when logging in without SSO configured, an AD user is created without the ability to assign roles.

  • New users with the same username as a previously deleted user do not work as expected.

  • A blank email is sent from a project if no task date has been set, and the email template contains at least one placeholder.

  • A 500 error displays in the console if an LDAP user logs in with, for example, ‘domain/’ as a prefix to their login.

  • There is no proper message shown when a private list is used for public dashboard widget

Notices​

All end of support notices are publicly available here:

Dashworks 5.7.6​

info

Dashworks 5.7.6 is due to be released in early August 2022.

Dashworks ended support for Internet Explorer (IE) and Edge in Internet Explorer Mode in version 5.6.1 (Apr 2021). While unsupported, the application has continued to be usable in IE. However, Dashworks 5.7.6 will introduce breaking changes that will result in Dashworks becoming unusable in Internet Explorer from this version onwards. IE 11 is no longer supported by Microsoft on most versions of Windows 10 from 15 Jun 2022.

Dashworks 5.7.6 will not support Microsoft SQL Server 2016