Release Notes - 23 June 2021

Read the list of new features, improvements and issues resolved in this release

Updated over a week ago

New features

The job importer has been extended with several new features

  • Jobs can now be updated using the importer

  • Custom fields can now be imported with new / updated jobs

  • Tasks can now be imported with new / updated jobs

  • The job importer now supports configurable template generation

Feature improvements and changes

Dashboard history pods have been improved in several important ways

  • New history period options have been introduced, including 'This week', 'This month', 'This year' and 'This financial year'

  • A value is now displayed for every day in a configured history period, from the point at which the pod is first added to the dashboard. Previously there might have been gaps in the data if the workspace view from which the pod is derived was not loaded

    • Please note that this change will only affect data collection from the time at which your Loc8 system is updated and existing pods with gaps will not be back-filled

  • Only one value is now displayed per day in a configured history period, which means that the distribution of data across the horizontal / x axis of the chart is consistent and even. For example, if a pod is configured with a history period of 'One week', there will never be more than 7 data points

  • Where there is no data in a history pod (i.e. future days in a pod configured to display data for 'This month'), the gap will be indicated with a dashed grey line

A quick-actions launch panel is now displayed when first logging in to Loc8

Other minor improvements include

  • Searched values in most settings spaces are now persisted when opening and closing an inspector

  • Job ID's now display an orange dot if there are any warnings present against the job

  • The 'Location address' is now an available column in the asset workspace

  • The 'Last updated' field on assets is now updated when an asset is moved

  • The 'Creator' field on jobs generated by a preventative maintenance schedule is now populated with the creator of the schedule itself

  • The 'Update job priority' automation rule action now includes an 'Update start / due by dates' option that will update the job start and due dates based on any SLAs configured against the selected job priority

  • It is no longer possible to delete a customer's primary site via the bulk editor

  • Invoice payment information is now displayed on the invoice HTML web view

Bug fixes

  • Assets that are manually associated to regions now correctly inherit additional region associations from asset / site ancestors

  • Some user workflows that led to inaccurate workspace view counts have been resolved

  • An issue has been resolved that caused workspace list views to appears as if they are bouncing whilst scrolling

  • An issue that caused an error to display when bulk updating job due dates has been resolved

  • An issue has been resolved that prevented the update of code / reference fields against workforce members

  • An infrequent error that was displayed when creating a quote has been resolved

  • An issue has been resolved that prevented some problems from being associated correctly to regions

  • An issue has been resolved that caused PDF generation to fail when a job had no address

  • An error that occasionally displayed when adding a location to a schedule has been resolved

  • An issue has been resolved that prevented the removal of deleted users from preventative maintenance schedules

  • An issue has been resolved that caused inactive maintenance schedule locations to disappear from view when interacting with a long list of locations

  • An issue has been resolved that caused the asset importer to fail when duplicate contacts were present

  • An issue has been resolved that prevented the correct display of the automation rule condition 'Task type'

  • An issue that caused an error to display when when editing multiple regions sequently has been resolved

  • An issue has been resolved that caused regions without boundaries to appear in the 'Regions with boundaries' list when inspecting a site

  • Several minor dashboard layout, label and UI bugs have been fixed

  • Several system-wide performance and stability improvements has been implemented

Did this answer your question?