[OFFICIAL]

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 16 Next »

  • Blog:
    Crisisworks 4.22.17 Hotfix Release

    This release contains minor improvements and fixes:

  • Blog:
    Crisisworks 4.22.15 Hotfix Release

    This release contains minor improvements and fixes:

  • Blog:
    Crisisworks 4.22.8

    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.

  • Blog:
    Crisisworks 4.20.5

    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.

  • Blog:
    Crisisworks 4.20 release

    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!

  • Blog:
    Crisisworks 4.19 release

    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:

  • Blog:
    Crisisworks 4.17 Released

    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.

  • Blog:
    Crisisworks Release 4.16

    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.

  • Blog:
    Crisisworks 4.15 released

    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.

  • Blog:
    Crisisworks 4.14

    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.

  • Blog:
    Crisisworks 4.13.8 - 4.13.9 released

    April 16 2018


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

    •  The additional Resource Assignment Counters Services Required registers.
  • Blog:
    Crisisworks 4.13.7 released

    April 6 2018

  • Blog:
    Crisisworks 4.13.0 Released

    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

  • Blog:
    Crisisworks 4.12.3 Released


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

    Roster Updates

  • Blog:
    Crisisworks 4.12 released

    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

 

  • No labels