All Collections
Release Notes
Release Notes for the Loc8 browser app
Release Notes - 14 March 2024
Release Notes - 14 March 2024
Updated over a week ago

Improvements

  • Maintenance schedule exports (csv, pdf and excel) now include the following additional fields

    • Create jobs

    • Jobs are due

    • Job type

    • Remove duplicate tasks

    • Avoid weekends and holidays

  • Attachment exports now include the following additional fields

    • Assets

      • Asset Loc8 ID

      • Asset ID

      • Asset Reference

      • Asset Name

      • Asset Type ID

      • Asset Type Name

    • Jobs

      • Job Loc8 ID

      • Job ID

      • Job Reference

      • Job Subject

      • Job Type ID

      • Job Type Name

    • General

      • Tag Name

      • Tag ID

      • Tags (comma separated list of all tags)

  • Improvements to performance and stability when performing intensive BI integration requests

  • Minor UI improvements

Bug fixes

  • An issue that occasionally caused quote and job line items to be added with 0 cost / charge values has been resolved

  • An issue that caused inspector fields to become editable when double-clicking has been resolved

  • An issue that caused the inline customer creation wizard (on site and asset wizards) to remain open after creation has been resolved

  • An issue that caused an error when renaming attachments has been resolved

  • An issue that caused an error when performing bulk status updates has been resolved

  • An issue that caused an error when adding attachment tags has been resolved

  • An issue that prevented name changes when editing workforce users has been resolved

  • An issue that prevented field updates when performing consecutive edits has been resolved

  • An issue that redirected users to the home page when removing job locations has been resolved

  • An issue that occasionally caused workspace search results to be partially hidden has been resolved

  • Several issues affecting asset imports have been resolved

    • An issue that caused an error when addresses were re-used across multiple assets

    • An issue that caused the asset number for every second imported asset to skip a digit

    • An issue that displayed old / legacy statuses

  • An issue that directed users to an old / legacy login page when their authentication session expired has been resolved

Did this answer your question?