🛠 Enhancements
Assignments: Proposal Data Added
Assignments now include a single-click expander (like the Work Order expander) showing key Work Order and Proposal details in four columns:
Work Order Info: Store identifier, address, and description
Latest Note: Most recent readable note with author and date
Work Order Dates & Info: Next/last visit, hours on site, PO number, creation date
Latest Proposal: Vendor proposal details, submission date, status, and total cost
This update provides quick, consolidated access to essential Work Order and Proposal information without leaving the Assignment view.
Vendor Assignment
Vendor Assignment configuration now supports asset-based conditions, allowing different default vendors to be automatically assigned when specific assets are tagged on Work Order assignments.
Key Details:
New Asset column in Vendor Assignment configuration, with dropdown selection and grid view support.
Updated Vendor Default Assignment import to support asset mapping.
Works with reports, communications, and API integrations.
Limitation: If multiple assets map to different vendors, only the most specific match will be used — multiple vendors cannot be dispatched on the same assignment.
Work Order Custom Fields in Invoice & Proposal Definition Checks
You can now include Work Order custom fields in definition checks for Client Invoices and Proposals.
Key Benefits:
Enables invoices to verify that related SC Work Orders are in the correct state for integration without relying solely on Work Order status changes.
Supports mapping SC Work Order statuses to custom fields on Fexa Work Orders for more flexible integration workflows.
Reduces complexity in crafting workflows for external system (SC) data synchronization.
Use Case Examples:
Streamlines integration for AAFM by allowing invoice readiness checks based on Work Order custom fields.
Benefits other clients (e.g., Evergreen) by providing greater control over invoice integration triggers.
🐛 Bug Fixes
Improved Performance for object_assets API Endpoint
We’ve optimized the object_assets API to prevent timeouts when filtering or sorting. The relationship that previously caused large queries to return excessive records is now only included when directly filtered or sorted on, resulting in faster response times and more reliable report generation.
External Subcontractor Payment API Validation
Fixed an issue where the /api/ev1/subcontractor_invoice_payments endpoint would accept and persist payments for non-existent subcontractor invoices. The API now validates the invoice_id and rejects requests when the referenced invoice does not exist, preventing erroneous payment records.
Note Visibility Behavior Update
Fixed an issue where note visibility was not being correctly set for users without the change_note_visibility_options permission. The application now correctly prioritizes the default_note_visibility value from the user’s permission group, falling back to the site setting if no group value is set.
User Export Sorting Fix
Resolved an issue where the Users Export did not respect the sort order set in the Main Users List. Exports now follow the same sorting as displayed in the UI.
Fix for Incoming Work Order Parsing from SC
Resolved a bug in the parsing logic for incoming Work Orders from SC that incorrectly determined whether a WO was preventive maintenance. This error caused an uncaught TypeError (“no implicit conversion of nil into String”), which is now properly handled.
Required Field Validation After “Don’t Save”
Fixed an issue where selecting “Don’t Save” on the unsaved changes prompt allowed invoices (and other objects) to bypass required field validation, such as the invoice description. Now, when “Don’t Save” is selected:
All unsaved changes revert to their original values without a page refresh.
Required fields must still be completed and saved before the workflow can proceed.
Applies To: Vendors, Work Orders, Vendor Invoices & Proposals, Client Invoices & Proposals, Projects, Work Order Bundles, Client Invoice Bundles, and Vendor Invoice Bundles.
Custom Field Key Conflict Fix
Resolved an issue where custom fields with identical keys on invoices and invoice line items could prevent one of the fields from appearing in forms. The loading logic in CustomFields.js now properly distinguishes between fields, ensuring both are displayed regardless of load order.
Project Assignee Translation Fix
Fixed an issue where the Project Assignee field in the project creation modal was using the Work Order Assignee translation instead of its own. The field now correctly uses the project.assignee translation, ensuring language overrides apply as intended.
Purchase Order Asset Selection Fix
Resolved an issue that prevented users from selecting an asset when adding a line item to a Purchase Order. The error assetPartRecord is not defined no longer occurs, and assets can now be selected without blocking PO creation.
Facility User Permission Group Dropdown Fix
Fixed an issue where the Permission Group dropdown appeared blank when creating a new user from the Facility > Users tab. The dropdown now correctly displays all available permission groups for selection.