Dashworks Release Notes - 5.3.0

Dashworks Release Notes - Galaxy

Executive Summary

Dashworks 5.3.0 is a major release, which includes a complete overhaul of the capacity functionality. Capacity is used to manage project tasks, such as deployments, where there is finite capacity for different types of deployment, or at different times within a day. The concept of slots has been introduced, allowing end users and project administrators to choose a time or type of deployment that suits them on any given date.


The existing capacity functionality has evolved to be become much more flexible and functional:

Multiple slots per day can be defined.

5.3.0 1-1

The availability of capacity slots is shown on the date picker when choosing a slot for a task:

5.3.0 2-1

Objects (e.g. devices) can be logically grouped into capacity units to manage which slots are available to them.

5.3.0 3-1

Capacity can apply to any task, not just scheduling tasks.

5.3.0 4-1

Capacity can apply to any object, including applications.

5.3.0 5-1

Override dates can now apply to a date range, not just a single date.

5.3.0 6-1

Capacity slots are a way of separating capacity available within a single day into different types or times. For example, you may allow users to choose between a Morning or Afternoon slot on any given day. Alternatively, you may use slots to offer a choice of different types of deployment to users, such as bringing their laptop to an upgrade clinic, or receiving a desk visit. Each slot has it's own defined available capacity across a Monday to Sunday pattern.

Capacity units are a new concept which allow you to group objects (devices, users, applications or mailboxes) together in an entirely flexible way in order to manage capacity for them. Previously capacity could only be defined for combinations of Teams and Request Types. You choose which slots to make available to which capacity units.

Now that capacity can apply to application objects, this opens up workflow options for UAT testing and application deployments. UAT sign off for business users may be limited by the number of virtual machines available to supply to the business users for testing. Further more, access to the VM may be restricted to a specific time slot rather than a full day. Deployment of new and re-packaged applications onto new infrastructure may also be restricted by capacity available within the application management team, and this can now be reflected. 

The existing capacity definitions (including override dates) that tie to teams and request types will be retained through the upgrade process and you are still able to use this configuration in any existing or new projects.

What's Improved

  • DAS-12813: Data on Admin > Buckets can be refreshed via a button
  • DAS-13637: Advanced filter options for list of saved lists

What's Been Fixed

  • DAS-13538: Admin > Projects/Buckets/Teams datagrid filters are not retained after deleting a project/team/bucket
  • DAS-13664: Target Drive Free Space missing from Evergreen device details page
  • DAS-13683: Link to project object pages in Snr from Evergreen project details tab, redirect to an invalid page when opening in a new tab/window
  • DAS-13890: WinAuth Issue: Evergreen UI 401 Not Authorised

Known Issues

  • DAS-14144: 'Over capacity' reason is incorrectly displayed for 'Unlimited' capacity in the Capacity > Exceptions report
  • DAS-14101: Objects which have a date value for capacity enabled tasks but no slot are not included in the capacity exceptions report
  • DAS-14147: Page error occurs on the Deployment Calendar when changing the Date Mode to a date hook task date that does not exist in the project
  • DAS-14148: Page error occurs on the Deployment Calendar when changing the Date Mode to a date hook task that was previously deleted and created again


Subscribe here to receive the latest Dashworks Release Notes via email.