2 February 2018

Today we are rolling out Crisisworks 4.12, which contains a range of performance improvements and new features. This will be progressively rolled out to all users over the next few days.

New features

Use templates to create training injects 

Now you can set up a series of template items (e.g. cases, requests, messages) that can be injected during training simulations. This is a great way to prepare a streamlined exercise, as well as re-use content across your exercises.

Read our practice note for more details. 

Automatic on-duty management

Crisisworks can now automatically place your on-call personnel on duty in their positions, whenever you add a position to an event.

To access this feature, check the checkbox labelled Automatically place on-call users on duty when creating or editing an event. 

Greater visibility on who received your published messages

Information items are a great way to capture and share intelligence such as situation reports, incident action plans, announcements and other messages during in incident 

They contain a publishing feature that will send a formatted email and/or SMS message to all specified recipients.

Now with Crisisworks 4.12, when publishing an item you can view the audit log to see the complete list of recipients, the delivery method used and the status of that delivery. This provides increased visibility and comfort that a message was delivered. 

Performance improvements

We've worked hard on this release to improve the performance of Crisisworks with two key areas:

1. Whenever events are added or positions added, Crisisworks now processes this changes much faster than before
2. Users go on or off duty faster than previously

Measured performance improvement varies site to site, but we've seen a 500% improvement in some cases.

Other Improvements

• The Situation Report template within the Information record has been updated based on feedback from a user group, to contain more useful fields. 
• Added a new Briefing Handover template within the Information record 
• User profile notification settings are now more easy to understand
• When reading logs, actions performed by Anonymous User have been renamed to System to avoid confusion — these are changes made by the system itself.
• Added the ability to duplicate an event via the event datagrid
• Improved asset importing speed and handled more edge cases (thanks to Corangamite for their feedback)
• When creating a new event from an event template where that event template contains item templates, those items were previously ignored. Now those item template are copied into the new event. If you didn't understand that last sentence then don't worry, neither do I — our recommendation is to use global events for training injects rather than template events.
• Fixed crash when a faulty record cascade rule was defined (Cardinia FPN)
• Improved the audit log for changes affecting multiple items
• Fixed audit log displaying image thumbnails in the log when they were deleted
• Fixed the Infrastructure Assessment reports to show cost estimate and actual values for only the selected event
• Fixed the Roster Reports which was crashing for a small number of users
• Fixed some multiple edge cases where some items were not copied when creating a new event from a template event.
• Some MEROs reported they could not view other people's logs.
• Additional search filter options have been added across various registers to improve content visibility

As always, thank you for being a Crisisworks user, and please let us know how we're doing by dropping us an email to our service desk or via Twitter.