This release contains minor improvements and fixes:

This release contains minor improvements and fixes:

With this release, customers can now bulk import Recovery Tasks (also known as “Services Required” from within the recovery portal).

The import process allows the tasks to be linked to a case by its ID, select the category by matching on the category’s name, and auto-assigning to resources by matching on the resource’s full name.

This is a 'hot-fix' release to enhance the publishing system:

• Improvements to the publishing log output:

  • The Crisisworks email platform has a maximum message size limit of approximately 5MB; if an email fails to send because this limit has been exceeded, the publishing log now indicates that this is the reason for the failure.

As we approach summertime, we are pleased to be releasing the 2018 edition of the EM Recovery module, along with our regular release pace with improvements and fixes.

Recovery 2018

Good news, everyone!

October 25, 2018

It’s spring-time in Melbourne, and to celebrate we have the first of a number of exciting releases over the next three months.

Crisisworks 4.19 has the following improvements:

August 8 2018

Global Contact Directory

With this release, we are pleased to introduce a new Global Contact Directory feature, which optionally maintains a synchronised contact item for each Crisisworks user and organisation.

June 12 2018

This release contains the first stage of work towards the Crisisworks Single Sign-in, Crisisworks ID Project.

The end goal of the project is to allow users to use a single account to login to multiple Crisisworks sites (once access is granted) including VPR.

On Friday May 25, Datalink released Crisisworks 4.15 to all customers. This release brings a number of improvements, along with an important major feature.

EMV Recovery Portal Reporting

This release brings a beta integration to EMV for post-impact Recovery Portal Reporting, with lead customers Corangamite and Moyne using the service to electronically prepare and submit recovery statistics to EMV.

Datalink is pleased to release Crisisworks 4.14, containing a series of new functionality and enhancements — this release is the “notifications and reporting” release.

Notifications

Crisisworks now has improved email and SMS notifications.

April 16 2018

This release includes some minor usability improvements to the Recovery module:

•  The additional Resource Assignment Counters Services Required registers.

April 6 2018

February 26 2018

We are pleased to announce the release of Crisisworks 4.13, which simplifies the use of resources and improves performance.

Global resources

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

Roster Updates

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

21 December 2017 — 22 December 2017

This festive release contains a number of improvements to improve application functionality, and is being released to all customers in a staged manner.

Improvements

20 November 2017

With this release, we have resolved the issue with Datagrid searching when using lookup fields.

17 November 2017

This series of maintenance releases contain the following improvements and has been released progressively according to our staged release cycle. 

4.11.13  

November 14, 2017

This series of maintenance releases contain the following improvements and has been released progressively according to our staged release cycle. 

4.11.7

October 30, 2017

This series of maintenance releases contain the following improvements and has been released progressively according to our staged release cycle. 

4.11.5

August 16 2017

4.9.11

• Support added for Windows m4a audio format

This series of releases contains a number of minor improvements.

4.9.7

• Fixed issues with the event selector

Following our 4.9.5 release, some users reported getting a more restricted level of access than they should immediately after logging in. The issue was easily worked around by having the affected user change their duty status (e.g. go off and back on duty), however it was annoying and we apologise to those affected.

May 4 2017

This release includes:

• Fixed: User export displays '0' as the user id

Today the first public release of Crisisworks 4.6 landed for all customers (4.6.4).

This release paves the way to offer some advanced new functionality to customers via new modules, including a new rostering capability, new capabilities for integration (including weather monitoring with BOM), and templating and notification improvements. Speak to us to learn more about these optional features.

On 8th March a hotfix was released to address some minor issues of the finance module in Crisisworks.

• Fixed: counter issues for Finance Reconciliations.
• Improved: removed unnecessary counters that were being displayed for Finance Reconciliations

Over the past week a series of smaller hotfixes were released to address some minor issues and improve the quality of Crisisworks.

• Improved: SMS formatting was improved for messages
• Improved: The REST API was improved for user queries to return more data for integrations

Crisisworks 4.5.0 continues the trend of accelerating feature releases, and contains a range of exciting features and improvements.

Summary of new features

• Publishing (e.g. announcements) has been improved and standardised across all information registers

19 Jan 2017

This release contains improvements to the recovery case and infrastructure assessment forms

• Improved: "Assigned Service Provider" field in recovery cases and infrastructure assessments is now a type-ahead select field, to make selecting service resources amongst long lists easier.

This release contains improvements to application stability and has been released to all customers.

• Fixed: Mecc Lookups now displaying only active lookup records
• Improved: Weed Co-ordinators can now access Weed Analytics

18 Jan 2017

This is a minor configuration update

• Added some additional resource categories for councils

This release contains improvements to application stability and has been released to all customers.

• Fixed: Weed percentage cover field remembering data on edit

• Improved: Asset road data import for Hindmarsh
• Fixed: Mecc_Lookup fields are now full text searchable

• Improved:  weed import parsing now supports wkt format as geoMode
• Improved:  weed imports now support MultiPoint format
• New: Corangamite weed data import
  
  

• Fixed: Vanilla Bootstrap error when being run for non-council sites. Added missing security policy that was needed.

• Fixed: organisations being set to inactive when bootstrap is run
• Fixed: FPN security issue with contractors not being able to see items assigned to their organisation.

This release contains improvements to application stability and has been released to all customers.

• Improved: Weeds module. Changed all select boxes to now be Lookup fields.

• Fixed:  Baw Baw FPN issue with adding new sub-contractor tasks.

This release contains improvements to application stability and has been released to all customers.

• Improved: when creating new events, implemented a 'Please Wait ..' message on the Finish button to prevent users from clicking this button more than once.
• Improved: for the FPN module, have added Hazard Cleared as next state allowed from Hazard Exists

This release contains improvements to application stability and has been released to all customers.

• Fixed: VPR error message appearing for some users.  This was regarding parent:init() not being called in VPRController.

29 November, 2016

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

• Fixed: Register Item Bulk Edit functionality.

16 November 2016

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

• Improved: Projector Mode on datagrids now updates without full page refreshes, and retains custom user filters and counter selections.

8 November, 2016

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

• Improved: assets are now displayed on mobile maps with colour to indicate whether they are in-use or not

4 November 2016

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

• Fixed: Added "code" to asset API to fix error on mobile app

2 November 2016

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

Many remaining customers on Crisisworks 4.1 will be migrated to this version.

Over October, a series of limited releases for Crisisworks 4.3 has begun. Only opt-in customers received these updates, with the remainder staying on the 4.1.x series software.

The following summarises the releases over this time.

4.3.1

Rolling out over October and November 2016

Datalink has listened to your feedback from the 4.0.x and 4.1.x releases, as well as carefully monitoring the use and performance of the platform over the 2014 and 2015 fire and flood seasons, and Crisisworks 4.3 is the response to this feedback, incorporating thousands of person-hours of engineering with simulations, evaluations, trials and feedback evaluations to make this our best update ever. 

This series of releases contains a number of minor improvements to application stability and functionality, and have been released to all customers.

• Minor label change to Weeds Register Form based on request

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

4.1.45

August 22 2016

The following minor map changes were rolled out for all users.

• Datagrid maps now show item geometries in colours as determined by the rendering strategy for the individual register — most built-in registers are coloured based on their status, however custom registers may include colouring based on other attributes.