Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This release includes some great improvements and fixes to the Crisisworks FPN module in preparation for the new Fire season.

Key Improvements

  • Have added an option to chose A Yes or No option now appears in the FPN register to choose whether there's a property has been identified. This allows you to add a Fire Prevention Notice without an associated asset Asset if needed.
  • Moved Select From Map option to under the map for the Crisisworks App
  • Added For the Vic Council schema, a new notes field has been added for when MFPO is selected
  • Added A new Workflow status has been added called "Proceed to Prosecution". Infringement Number and Infringement Sent Date fields appear for this new status
  • Added the Asset Contact's externalId and the Asset's geo geometry data to the FPN CSV export
  • Modified Asset Contacts import results table to display the propnum and crefno fields in the success message. This allows for easy identification that it has added the correct Asset to the FPN.
  • When Generating Merge Documents or Exporting to CSV Mail Merge, added a check to not update the Next Action Date if it's already set to a later date.
  • For Export CSV Mail Merge - we are now updating the Next Action Date regardless of the state. Previously it was only updating for Hazard Exists
  • Updated the Asset view screen to display additional codes for the asset such as propnum, crefno etc. This appears in a new table called Asset Extra Information
  • Updated the Asset Datagrid to display the code configured for your site (ie propnum)
  • Added two new tokens to the FPN Merge Letter:
    • {$noticeNumber} - this token is useful for when there are multiple letters generated for the one property. If there is more than one owner for the property and multiple letters are generated the noticeNumber will add include the registerId and prepend it with add an "_1", or "_2:" to the end of it to ensure the notice numbers are unique. For example, if there are 3 letters generated for the FPN Id 12345, the notice numbers will be 12345_1, 12345_2, 12345_3.  You can add this token to your HTML template and replace the current  {$item.id} next to the Notice Number heading. This notice number will also be part of the filename of the letter. If there is only one letter generated for the property, the notice number will simply be 12345.
    • {$item.Asset.friendlyCode} - since the latest Vicmap update your Asset Codes in Crisisworks are is using the prop_pfi of the property.  If you wish to display the propnum (or code that's configured for your site) next to the Property No on the right hand side of your letter, then change the {$asset.Code} to {$item.Asset.friendlyCode}.
  • Improved the quality of the letterhead in the Merge letters.