Crisisworks 4.0.114 released

This release contains a number of improvements to application stability and functionality and has been released to all customers.

Added a retry loop to item saving in the event of a deadlock detected at the database server
Fixed: EMLOs cannot resolve
Fixed: a number of unrelated edge cases causing "500" errors when saving items
Improved: request workflow now better supports users with no ability to assign (e.g. EMLOs, limited users) by automatically unassigning the request if its status is set to 'Requested' or 'Resolved''. The standard workflow for EMLOs assigned to a case allows them to select 'Requested' if they wish to hand back the task to the coordinators.
Improved: request workflow now supports 'On Hold', which is an assigned state that the EMLOs can select for multi-part deployments (e.g. road blocks) where a part of the deployment involves keeping the case open with no work being done.
Notifications no longer send messages for registers that do not need them -e.g. FPNs, Recovery.
Corrected the Environmental Health Assessment form fields (order was incorrect)
Added Environmental Health Assessment to the list of available registers in the app and web
Tested for Internet Explorer Edge compatibility (passed)
Fixed: missing Open Information layer on maps
Removed broken global event counters until a fix is applied to them
Various internal improvements
Fixed: Duplicated welcome message for new users
Fix: crash when accessing resources datagrid
Vulnerable Persons Registers registration, user management and link now working