Skip to main content
Release Notes - 30 January 2024
Updated over a week ago

New features

  • Files / attachments now support tagging to aid in categorisation, sorting and filtering

    • Tags can be created and added to entity-level files / attachments on the Files tab of any given entity inspector. I.e. Tag a file on an asset, job or quote

    • Tags can be managed and deleted in the Tag settings area

    • In future Tags will be extended to support entity level tagging (i.e. Tag an asset, job or quote directly)

    • Note that tagging is currently only supported on the browser application


Improvements

  • Files / attachments can now be renamed from the Files tab of any given entity inspector

  • Changes to entity custom fields now reliably update the Last updated date/time value of entities across the platform

  • Improvements to workspace level access restrictions

  • Improvements to customer / contact association via API endpoints

  • Improvements to the performance of loading assignee and contact lists

  • Improvements to the performance of attachment thumbnail generation

  • Improvements to document template PDF print formatting

  • Improvements to authentication service performance and stability

  • Improvements to general platform performance and stability

  • Minor UI and layout fixes

Bug fixes

  • An issue that caused the incorrect loading of asset location modal properties has been resolved

  • An issue that caused the incorrect display of customer primary and billing contact fields has been resolved

  • An issue that caused an error when updating Job and Appointment automation rules has been resolved

  • An issue that was occasionally preventing correct region filtering has been resolved

  • An issue that was occasionally preventing region to workforce updates has been resolved

  • An issue that redirected users to the incorrect login screen after password reset has been resolved

  • An issue that was preventing the use of document templating on new accounts has been resolved

  • An issue that was preventing reliable activation of new accounts has been resolved

Did this answer your question?