Versions Compared

Key

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

Features and improvements






Core modules

API. Search for work orders using as many parameters as you want! We’re introducing the POST/odata/workorders/filter method, a better version of the GET/odata/workorders method. It allows applying an unlimited number of WO search filters.

Add-on modules

No features and improvements for add-on modules.



Bug fixes




Core modules

Asset Manager. There were troubles with the Regions filter on the Manage Assets page. You picked some regions and hit Apply, but nothing happened. The filter is up and running again.

Dashboard. After you submitted a work order to your FTM internal provider, the assignment confirmation message was not displayed to you, while the WO was successfully assigned to the corresponding internal tech. We've handled the issue so that you see who from the techs group is assigned to your service request.

Dashboard. Dashboard 2.0 displayed an incorrect count of work orders waiting for review if the Only Show My WO checkbox was selected. We've done away with this discrepancy. Note that the Only Show My WO checkbox is an add-on feature.

MLI. Due to an MLI ruleset issue on our side, the invoice escalation occasionally didn't work as expected. We've settled that matter. All invoices are now being escalated per your MLI levels and rules.

Provider Directory. Providers who recently joined your private network visited their Clients page, and it looked as if they completed some of the custom requirements that you never had. The correct compliance details were available to them on the client details page. We've tackled the issue.

Work Orders. When you tried to add a WO note with the Follow Up checkbox selected, the error message appeared, and the WO note couldn't be created. A tricky bug was finally squished, and this now works fine.

Add-on modules

Refrigerant Tracking Manager. There were cases when adding refrigerant usage did not trigger a leak record generation even though the amount of refrigerant used exceeded the threshold. We've fixed the problem and taken the necessary measures to prevent it in the future.