Skip to main content
Sign in

Release Notes 11.24.2025

  • Updated

🛠 Enhancements

Automatic Logout and Clear Messaging After Session Timeout

  • We’ve improved how session timeouts are handled to reduce confusion and enhance security.

What’s New

  • When your session times out and the countdown reaches zero:

    • You are automatically logged out

    • You are redirected to the login screen

    • A banner appears at the top of the page stating:
      “You have been logged out due to inactivity.”

  • The banner remains visible until you log back in.

Why This Matters

  • This update provides a clearer, more secure experience by ensuring you always know when your session has expired, and can immediately log back in without uncertainty. 

🐛 Bug Fixes

Correct Date Formatting in Exported Work Order Spreadsheets

  • We’ve resolved an issue where the Client ETA, Follow Up Date, and Next Visit fields appeared as decimal values when exporting Work Order lists to a spreadsheet. These fields will now display in the correct date/time format, consistent with other fields such as Created and Completed.

  • This update ensures exported reports are clearer, easier to read, and ready for immediate use in your workflows.

API Fix: is_default_for_classification Field No Longer Accepted in Products POST Requests

  • We’ve corrected an issue in the Products POST API where the is_default_for_classification field could be included and modified in the request body. This field is intended to be response-only and should not be user-modifiable.

What’s Changed:

  • The is_default_for_classification field will now only appear in API responses.

  • Any attempt to include or update this field in a POST request will result in an error, as expected.

  • API documentation has been updated to reflect this behavior.

  • API consumers will be notified of this change to ensure smooth adoption.

  • This update ensures consistent, secure handling of classification defaults across all product records.

API Fix: Correct Property Name in Subcontractor Invoice Payments POST API

  • We’ve resolved an issue in the Subcontractor Invoice Payments POST API where the sample request in our documentation used an incorrect property name. The sample previously referenced subcontractor_invoice_payments, which caused requests to fail with the error:

    • "param is missing or the value is empty: payments"

What’s Changed:

  • The correct property name for the request body is now clearly documented as payments.

  • Using payments in the POST request results in a successful response.

  • The API documentation has been updated to reflect the correct request structure so developers can integrate without errors.

  • This update ensures accuracy in the API documentation and prevents unnecessary troubleshooting for integrators.

CSV Support Restored for Asset V2 Import

  • We’ve resolved an issue that caused CSV files to behave inconsistently in the Asset V2 Import tool. Users reported that CSV imports appeared to stall, showed incorrect progress, or failed to display accurate success/failure counts, even though some assets were being created in the background.

What’s Fixed

  • CSV files now import correctly and stay fully within the V2 import flow.

  • Progress indicators and status updates display accurately.

  • Success and failure counts now appear correctly in the Imports grid.

  • Failure reports can be downloaded reliably.

  • CSV and XLSX files now behave consistently.

  • This update ensures a smoother and more predictable asset import experience for all clients using CSV files.