Release Notes - August 3-7, 2026

Overview  

This document describes what’s new or improved with the August 3-7 Tango releases, included in Core Release 3.7.64, Edge Application Release A10.8.22, and Edge Platform Release P3.10.12.

• Monday August 3: Energy & Sustainability
• Thursday August 6: Edge
• Friday August 7: Core, Reserve
• Continuous deployment for Occupancy

What's New or Improved?

• Predictive Analytics
• Transactions
• Projects
• Lease
• Maintenance
• Space
• Reserve
• Occupancy
• Energy & Sustainability
• Datamart 
• Platform

Predictive Analytics

N/A

Transactions

N/A

Projects

Bidding - Validations added to the Bid Response Cost Items to no longer allow negative Quantities or Unit Costs. [EA-1059]

Lease

N/A

Maintenance

Service Request - Scheduled Dispatch Date (part of the Dispatch Timing functionality) will now default the Appointment Date value. [EA-1072]

Service Request - Call Center users can now schedule Service Requests for future dispatch.

A new Dispatch Timing dropdown field is available on the Dispatch step of the Service Request with values:

• Immediate (default)
• Scheduled

When Scheduled is selected, users can define a future Dispatch Date/Time for the Service Request.

This enhancement provides greater flexibility for coordinating work with operational schedules and maintenance team availability. [EA-1001]

Work Order Reports - Asset Instance # field added to the "All Work Orders" report. [EA-1068]

Space

N/A

Reserve

N/A

Occupancy

N/A

Energy & Sustainability

Within the Settings configuration, toggling the “Use Custom Emission Rates” kicks off a full, client-wide invoice-emissions recalculation that runs across four services and takes ~1–2 hours. Historically, the toggle remains freely editable (even if flipped by a different user within the portfolio) so a user can flip it repeatedly and pile up overlapping recalculations, and there is no feedback about when the work is done. 

Now, an email is sent to the end-user that adjusts this toggle when the process starts and another when it ends. If a user toggles it on, it is now not editable for anyone else within the client org until the calculations are complete. If a user turns it off, it is now not editable for anyone else within the client org until the calculations are complete. [WATX-3318]

The “Sentence Filter” report currently shows estimated data in a way that looks the same as actual data. There’s now a column in the “Pivot Table” tab ONLY, to show which statements are estimated that indicate “TRUE” or “FALSE”. [WATX-3211]

There’s currently a “Data Provider” field in the Invoice Details modal within the “Invoice Management” module. This field has been added to the “Invoice Data Report”. [WATX-2675]

Within the “Sustainability” module, “Nuclear” now appears as an option within the REC resource types. [WATX-952]

The “search” bar on top of platform was limited to accounts, properties, and nodes. Now we additionally include results for real time meters. [WATX-3357]

When Arcadia (fka Urjanet) sends data, we now automatically fail any consumption data provided with energy unit = “undefined” (when it’s not clear on the utility invoice). This requires a human review. [WATX-2879]

Within the “Invoice Data Estimation” tool, users can now filter the account hierarchy by commodity in order to apply estimations specific to commodities vs. only nodes/locations. [WATX-2716]

End users now have the ability to bulk import ICAP/PLC tags within the “Imports” section, rather than filing a ticket for Tango analysts to upload on their behalf. [WATX-2052]

The “Onboarding” form now has an optional “Sewer Cost” column so users can upload sewer specific charges to the portal. [WATX-1340]

Datamart

N/A

Platform

Standard AR Inbound API - Added support for updating the payment status to VOID using only the Lease Payment ID / Invoice Header ID and Status fields. This enhancement is required to support scenarios where an invoice is issued to the wrong supplier. [TAC-6242]

Standard AR Inbound API - Added support for updating the payment status to VOID using only the Lease Receivable ID and Status fields. This enhancement is required to support scenarios where a billing is issued to the wrong tenant. [TAC-6243]

Known Issues

    When applicable, this section provides information on any known issues that will be corrected in the future. 

Additional bug fixes and performance enhancements were completed.