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.
If an email bounces for any reason, the publishing log now indicates that this is the reason for the failure.
If no messages are sent because no recipients match the publishing criteria, the publishing log now indicates this.
When an item is published, the actual sending of messages is done in a background queue process. Previously the item was only reverted to its non-publish state once this process completed. This meant that if the item was updated again during the processing window, another publishing process could inadvertently be triggered. The publishing process has been changed so that now items are reverted to their non-publish state as soon as the publishing process has been triggered. This means that the items can be updated again immediately without the possibility of accidental publishing.
This release contains minor improvements and fixes:
- Fixed issues with bulk functionality when choosing Select All on datagrid
- Vic Map importer changes to update matching Assets instead of deleting all assets - this is to support the new Asset Contacts so that they can remain linked.
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!
This recovery form has been redesigned with extensive consultation and feedback from our customers to make it easier to use and less complex, while still retaining all the same fields and functionality of the previous module. It does this by intelligently hiding unneeded parts of the form based on answers to prior questions, and by hiding the complexity by default.
This makes adding new recovery cases much easier, especially for new or unfamiliar users.
Behind the scenes, the module has the same fields and is fully compatible with prior season data, as well as EMV data sharing.
Additionally, for obtaining consent to share, the form now no longer defaults to no, but instead defaults to a new option of “not asked”. The system reminds users when viewing the record if consent has not been asked, and highlights records where consent has been asked but not granted.
Also, all the data grids for the recovery system have been overhauled to make them easier to use both on the web application and the mobile application, including improved navigation between the numerous records that make up recovery.
We hope you enjoy it, and we’d love your feedback on this.
Other improvements
Crisisworks 4.20 also adds the following additional improvements:
Fixed a problem with bulk management sometimes selecting different items. We know this was a big problem for some FPN mail merge users, and we apologise for this one.
Introducing a rollback facility to allow items to be rolled back to a prior state, which works by reversing the effects made on a single audit action. If you need to make use of this, contact our Service Desk.
Improved Vicmap asset import to now support NCPR coded property codes, and to support updating properties in a way that preserves asset contact links, if they’ve also been imported.
Fixed a problem with the form for web and mobile that would sometimes not display the embedded map
Fixed a problem with the web datagrid map sometimes not loading on first page load.
This release has been made after extensive collaboration with key customers, and we hope you enjoy this release.
As always, if you encounter any issues with this release then please let us know.