🛠 Enhancements
Copy Work Order Functionality
We’ve introduced the ability to copy an existing Work Order to quickly create a new one with the same core details.
This enhancement is designed for situations where scope changes mid-job or when similar work orders need to be created with consistent descriptions, NTEs, and other baseline fields.
What’s New:
A Copy icon has been added to the Work Order Overview screen, next to the ReDispatch option.
Users with Work Order Create permissions can copy an existing work order.
When selected, a confirmation modal will appear informing the user that:
All core details (except dates) will be copied.
Assignments, visits, invoices, proposals, quotes, and other associated records will not be copied.
Dates will reset to the copy date.
ETAs will adjust based on the new date.
🐛 Bug Fixes
IVR ID Not Recognized for Check-In
Fixed an issue where technicians were unable to check in via IVR due to the system not recognizing valid IVR IDs.
The IVR prompt incorrectly stated the IVR ID was invalid and disconnected the call.
Issue was reported across multiple sites.
Identified a pattern where impacted IVR IDs began with a leading “0”.
Technicians were forced to use web or mobile as a temporary workaround.
IVR now properly recognizes valid IVR IDs, including those beginning with “0”.
Restores expected IVR check-in functionality for affected sites.
File Upload Failing on Invoices and Quotes
Fixed an issue where users with proper permissions were unable to upload files to Invoices and Quotes.
No error appeared in the UI after selecting a file and clicking upload.
The browser Network tab returned an authorization error, despite correct permissions.
File uploads to Work Orders were functioning as expected.
Issue was blocking work for impacted users.
Upload functionality has been restored for Invoices and Quotes.
Users with appropriate document and invoice/quote permissions can now successfully upload files.
Success behavior is now consistent across Work Orders, Invoices, and Quotes.
This resolves a backend authorization issue affecting multiple sites.
Document Upload Failing in Vendors, Clients, and Projects
Fixed an issue where users were unable to upload documents in the Vendors, Clients, and Projects modules.
After selecting a file and clicking OK, no action occurred in the UI.
No success or error message was displayed.
The Network response returned:
{"message":"You are not authorized to access this page."}Root cause was a backend authorization issue preventing file uploads.
Documents now upload successfully.
A success message is displayed upon upload.
Uploaded files properly appear in the Files list.
IVR Check-In/Check-Out Fails After Replaying Prompt
Fixed an issue where the IVR lost the assignment ID if a user pressed a key other than 1 or 2 during the check-in/check-out prompt.
Previously, if a user pressed another key (e.g., 0) to replay the prompt and then selected 1 or 2, the system failed to recognize the assignment ID.
This resulted in a Twilio error and prevented users from successfully checking in or checking out.
The IVR now properly retains the assignment ID when replaying the prompt.
Users can safely press another key to hear the prompt again without interrupting the check-in or check-out process.
Ensures a smoother and more reliable IVR experience across all clients.
Asset Custom Field Updates via Import Causing Duplicate Asset IDs in Reports
Fixed an issue where updating an Asset Custom Field via Asset V2 Import did not properly reflect on the Asset record.
Multiple successful imports for the same Asset ID could cause duplicate rows to appear in Asset reports.
Each duplicate row displayed previously imported Custom Field values.
Asset records now correctly reflect the most recently imported Custom Field value.
Reports now return one row per Asset ID with the accurate, current Custom Field value.
Ensures consistency between Imports, Asset records, and Reporting.
Store Manager Organization Correctly Aligns to Facility Client
We fixed an issue where Store Managers created from the Main User List were always assigned to the site owning client’s organization — even when the selected facility belonged to a different client.
What’s Fixed:
If a Store Manager is created and assigned to a facility tied to a different client, the user will now be associated with the facility’s client organization.
Work orders created by that user will reflect the correct client.
Note:
If multiple facilities across different clients are selected, the user will default to the site owning client.
Region and District Manager creation is not impacted.
Inactive Users No Longer Receive Store Manager Default Email Address Communications
We’ve resolved an issue where inactive users were still receiving communications when a rule was configured to send notifications to Store Managers' Default Addresses.
Issue:
If a communication rule included Store Managers' Default Addresses as a recipient, inactive users associated with that store could still receive email notifications.Expected Behavior (Now Implemented):
When a user is marked as inactive in Fexa, they will no longer receive communications triggered by communication rules — unless:Their email is explicitly added to a communication rule, or
They are included in a previous note thread.
What’s Changed:
Communication rule logic now validates user status before sending.
Inactive users tied to Store Manager Default Address relationships are excluded from future notifications.
No manual removal of contact emails is required.
This update ensures communication rules respect user activation status and prevents unintended notifications to deactivated users.