🛠 Enhancements

CMMS

Bulk vendor-invoice imports can now associate an asset with each line item at import time, instead of tagging every line by hand after the fact.

• What's New:

  • The Vendor Invoice V2 import template includes a new optional Asset field

  • Assets link automatically to the correct invoice line item on import

  • Asset matching respects the line item's facility to avoid mismatches; unmatched assets surface a clear per-row error, and rows without an asset still import

Saved Vendor and Purchase Order lists can now power dashboard widgets, so procurement and accounting teams can surface records needing action directly on their dashboards.

• What's New:

  • "Vendor" and "Purchase Order" are now selectable shared-list types for dashboard widgets

  • List widgets display the full set of vendor or purchase order records

  • Count widgets show an accurate total, including "0" when empty

Large data imports could stall partway through or strain the system on big files. Imports are now more resilient and more memory-efficient from the first row to the last.

• What's Changed:

  • A single problem row no longer aborts the whole import — it's recorded as a failed row in the downloadable failures file, and the import runs to completion

  • Large import files stream and parse row-by-row (CSV/TSV and XLSX), avoiding the memory exhaustion that could kill an import before it started

  • Import progress saves in batches and skips redundant workflow re-checks, so large imports finish faster; imported records still land in their correct starting state

The "default hidden types" capability — previously only on the Work Order grid — now extends to the Assignments, Vendor Invoice, Client Invoice, and Proposal grids, so no-longer-actionable records don't load on every grid open.

• What's Changed:

  • Four new settings let admins hide chosen workflow types by default on those grids

  • Hidden records are excluded server-side for faster loads, and stay reachable via filters and reporting

On multi-currency work orders, the Budget NTE and Summary NTE widgets now also show the amount in the work order's own native currency, so it's clear which currency a figure is in.

• What's Changed:

  • Adds a second, native-currency value (with its symbol/code) only when more than one currency is involved

  • The existing value and its math are unchanged; single-currency work orders look exactly as before

  • Applies across Desktop and PWA (mobile and tablet)

FexaAI

The safeguard that keeps Store Managers from overriding work order priority in the agent now applies to Region Managers too, so their work orders use the configured site default.

• What's Changed:

  • Region Manager is now handled like Store Manager for priority — the agent won't set it directly and the role can't set it manually

  • A new permission-group toggle controls whether AI can set priority

Users creating a work order through the Work Order Agent can now see and set the Responsible Party in the conversation, instead of waiting until after the work order is created.

• What's New:

  • Responsible Party appears during the chat review step when a match can be resolved

  • The field is optional and only editable by users with permission to edit Responsible Party

  • The value set during chat carries through to the finished work order

🐛 Bug Fixes

Assets tagged to a parent (non-leaf) category were being left out of the asset list on the work order creation form and the main work order view. They now appear correctly on both.

• What's Fixed: The asset lookup now includes parent categories on both the standard creation form and the post-creation work order view

Asking the Answers Agent for "open work orders" could return work orders that aren't actually open, such as Call Avoided and Cancelled – Archived.

• What's Fixed: "Open" now excludes avoided, archived, expired, and inactive statuses, so only genuinely open work orders are returned

The Work Order Agent could match the wrong store — or fail to find one — when a store number was entered without its leading zero, because it matched on the internal store ID rather than the store identifier.

• What's Fixed:

  • The agent now matches stores from partial store numbers, so users no longer need to include leading zeros (e.g. 7012 resolves to 07012)

  • Store mapping now uses the store identifier and name, and the store dropdown displays the identifier value

Attachment photos showed as broken-image icons on survey-response print/PDF documents, because a malformed image link was rejected by some sites' security layer.

• What's Fixed: Attachment photos now load reliably in survey-response PDFs; no template or data changes required

In large facilities, the work order asset picker was capped at the first 500 assets alphabetically and typeahead search didn't work, so many assets simply couldn't be selected.

• What's Fixed:

  • Removed the 500-asset cap and added pagination so all in-scope assets are reachable

  • Typeahead search now filters across the full asset set, within the correct facility/category scope

  • Already-selected assets still show as selected regardless of position

Store managers saw inactive/retired priority options when creating a work order, even though administrators didn't.

• What's Fixed: Inactive priorities are now hidden from the urgency dropdown for Store Managers on new work orders; historical inactive priorities still show on existing work orders

Users with permission to change note visibility couldn't see the visibility control (hamburger icon) on a vendor's Notes tab, even though it worked on work order notes.

• What's Fixed: The note visibility control now appears on vendor profile notes for authorized users, matching work order note behavior

Invoices and proposals hidden from a user in the grid could still be opened directly via their URL, bypassing visibility rules.

• What's Fixed: Subcontractor and client invoices and quotes now enforce hidden-record rules on direct-link access, returning the standard "record not found" response just like work orders do