OFFICIAL

Crisisworks 4.28 Released

Created by Scott Davey
Last updated: Apr 09, 2020
2 min read

February 19 — February 21

We are pleased to announce the release of Crisisworks 4.28, which continues our series of incremental upgrades to support the 2020 bushfire recovery.

Key highlights of this release

  • We’ve improved performance

  • We’ve re-written the merge facility so that it now supports undoing a merge

  • We’ve added initial support for setting up scheduled reports

  • Some reports now support being able to update their contained items upon completion — this allows reports to be set up to send delegated tasks to agencies each morning and transition the containing task’s status.

  • The EMV Recovery Portal integration has been dusted off and verified ready for use.

New and improved

  • New: Imports can now support attaching files from CSV links

  • Improved: More file types are supported as attachments, including CSV and EML

  • Improved: performance of the Recovery Task with Case report

  • Improved: allow opening of closed (duplicate) items

  • Improved: “Activity” panels are now expanded by default, now that performance is improved

  • Improved: Redirecting *.mecccentral.com → *.crisisworks.com

  • Improved: Audit log entries now strip any HTML from comments

  • Improved: Asset searching for addresses with postcodes or address ranges work

  • Improved: When signing in, the system will do better at remembering your last duty and last selected event

  • Improved: The data grid no longer refreshes when new data arrives; instead, you will be notified and have control over refreshing it.

  • Improved: Added a confirmation alert before merging items

  • Improved: some counter tweaks have been made to registers based on analysing usage

  • Improved: Offers gets an export report

Fixed

  • Fixed: Offline app email validation preventing cases from being saved

  • Fixed: Removed “Saved Searches” admin menu item (this will re-appear in future when the feature is released)

  • Fixed: Safari users were sometimes running out of memory causing infinite spinners; this has been detected and fixed.

  • Fixed: IE users had some errors

  • Fixed: Some users had troubles scheduling reports where the report got stuck in the “pending” state.

Faster

Performance improvements include much better handling of large-scale activations through horizontal platform scaling, and through heavy optimisations of counters, audit logging and background tasks.

  • Load balancing now better-handles switching between readers and writers in the database cluster to leverage scaling the number of readers under load

  • Event convex hull calculations are tuned to handle large polygons and large events

  • The activity feed API is pre-calculated to avoid slow-downs

  • Counter calculations detect and respond to high load events where they have been delayed running, and avoid building outdated counters

  • Bulk actions no longer trigger counter re-calculations for each item added or imported

  • Many internal performance fine-tuning experiments have been rolled out to all sites