🛠 Enhancements

CMMS

Customers whose identity provider sends the email under a different attribute name could fail to map correctly.

• What's Changed:

  • SSO now treats emailaddress, e-mail, E-mail, e-mailaddress, Email Address, and E-mail Address as the user's email.

FexaAI

Facility managers can now tell us whether an Answers Agent response was helpful, so the product team can see which answers work and fix the ones that don't.

• What's New:

  • Thumbs-up and thumbs-down controls appear on each Answers Agent response. They're always visible on the latest response and appear on hover for earlier ones.

  • Ratings are per response. You can change a rating you gave earlier.

  • A new ratings report, alongside the existing FexaAI reports, shows each rated question and answer in the context of the surrounding chat.

  • Rated data is retained for 90 days.

When a permission group enforced default priorities, the priority disappeared from the Work Order Agent chat. Users couldn't see it until after the work order was created.

• What's Changed:

  • A site-level setting controls whether users who can't set priority can still see it in chat.

  • When the setting is on and the default is enforced, the priority shows as read-only before submission. Users can't change it, even by asking the agent.

  • When the setting is on and the agent may set priority, users see both the default and the agent's recommendation. They choose one before the work order is created.

  • Priority also appears in the work order detail summary.

Create Work Order was available from the location work order grid but not from the location work order menu.

• What's Changed:

  • The menu now includes Create Work Order, matching the grid.

  • If FexaAI is configured for the location, the action opens the FexaAI creation flow. Otherwise it opens the standard creation modal.

  • Only users with work order creation permission see the action.

The Work Order Agent sometimes picked irrelevant categories when creating a work order.

• What's Changed:

  • Category selection now works down the category tree one level at a time, choosing the best match at each step.

  • If one category is a clear match, the agent uses it. If several fit, the agent shows the options so the user can confirm one. If none fit, the agent asks for more detail.

  • Categories can be flagged as default/fallback, using the same setting as other AI flags on categories.

🐛 Bug Fixes

Scheduled or FTP-delivered Excel reports could produce a workbook Excel flagged as corrupt. This happened when a free-text column, such as work order description, had a line starting with "=".

• What's Fixed:

  • Free-text values are now always written as plain text, so they can no longer be misread as formulas or links.

  • Numeric columns export exactly as before.

A Work Order Notes import with a work order ID that didn't exist yet still succeeded. The note then attached itself to whichever work order was later created with that ID.

• What's Fixed:

  • Rows that reference a non-existent work order are rejected and listed in the import failures file with "No work order with ID {ID} could be found."

  • Other rows in the same file still import.

  • Notes already stored this way are not changed.

An import could change an assignment's Service Provider, and the change carried through to existing and new proposals and invoices. On Vendor Invoice imports, the invoice details and the invoice grid could show different Service Providers.

• What's Fixed:

  • Imports can no longer change the Service Provider on an assignment.

  • A Vendor Invoice import row fails with a clear error if its Service Provider doesn't match the invoice.

  • The invoice grid and invoice details stay consistent.

• The SYNC TRAKREF button was hidden from vendor and subcontractor users. It showed for Super Admin and internal roles.

• Vendors with permission to update assignment status now see the button and can create a Trakref service event for each asset on a multi-asset work order.