Release Notes - October 10, 2025

Overview

This document describes what’s new or improved with the October 10, 2025 Tango release, which was included in Core Release 3.7.48, Edge Application Release A10.8.6, and Edge Platform Release P3.10.6.

What's New or Improved?

• Predictive Analytics

• Transactions

• Projects

• Lease

• Maintenance

• Space

• Reserve

• Occupancy

• Energy & Sustainability

• Datamart

• Platform

Predictive Analytics

N/A

Transactions

Transaction Description - Added a rich text field on a new tab, Transaction Description, allowing capture of formatted details describing the transaction details. [TAC-4667]

Transaction Workflow - Enhanced Transaction workflow to allow for locking or unlocking an in process or approved transaction based on the read-only flag of the transaction status. [TAC-4480]

Projects

Projects - With the correct user role, you can now choose to terminate an in process budget approval workflow directly from the submitted budget with the click of a button. [TAC-4341]

Projects - With the correct user role, you can now choose to terminate an in process change order workflow directly from the submitted change order with the click of a button. [TAC-4345]

Projects - With the correct user role, you can now choose to terminate an in process budget change order workflow directly from the submitted budget change order with the click of a button. [TAC-4347]

Projects RFI - On the RFI subtab of the Communications tab, added a column to display the document reference input. [TAC-4686]

Lease

Clauses - Added Abstraction Method field to capture approach used to populate clause information (Manual Abstraction, AI Abstraction, AI Abstraction with Modifications). [TAC-4227]

Lease Description - Added a rich text field on a new Basic Info subtab, Lease Description, allowing capture of formatted details describing the lease. [TAC-4669]

Payment/Billing Search - Enhanced Export to produce .XLSX format (formerly .CSV) [TAC-4649]

Recurring Costs - Enhanced the Update feature to populate the Due Date on the one-time payment created through a retroactive rent change. [TAC-4131]

Sales Import (API) - Added ability to support monthly (in addition to annual) caps on exclusions. [TAC-4651]

Standard Integration (AR) - Added support to include late fees in accounts receivable inbound integration inclusive of late fee amount and late fee date. [TAC-4427]

Maintenance

Facility Manager Home Page - New Tile/Report for “Unassigned Service Requests” which will show any Service Request that is not currently assigned to a Facility Manager. A SR could potentially be unassigned if a Request is submitted by a Requestor for a Location that has no FMs assigned/associated to it (such as a brand new Location), no Default FM selected, and Smart FM Assignment not enabled. [EA-740]

Scheduled Maintenance - When Scheduled Maintenance Work Orders are generated, the Asset data on the Scheduled Maintenance Plan/SM Location will be updated from the current data in the Core Asset Detail record. This will ensure the Asset data on the SM Work Order is up to date when it is created. Note: At this time the “Create WOs Per Asset” option does not include the Asset data refresh at this time, but this will be available in the upcoming release. [EA-689]

Scheduled Maintenance - Asset Status and Status Type (Active vs InActive) is now displayed on the Scheduled Maintenance Plan (in the Assets section on the Locations) and on the SM Work Order. Asset Status & Type will also be displayed on various Scheduled Maintenance Work Order notifications in the Assets table. Note: Only “Active” Assets can be selected on to a Scheduled Maintenance Plan, but if the Status changes to and InActive Status in Core then this will also show up in Edge. [EA-690]

Service Request - For Requests created in Edge, the duplicate check will now also validate the Floor and Space if populated.

• If the Request is at the Building/Location level, a duplicate SR would also need to be at Building/Location level with no Floor or Space selected.
• If a Request is at the Floor level (meaning Building/Location + Floor), then a duplicate SR would also need to be at the same Building/Location + Floor level, without a Space.
• If a Request is at the Space level (meaning Building/Location + Floor + Space), then a duplicate SR would also need to be at the same Building/Location + Floor + Space level.
• Note: All levels of the duplicate check validate against other open Service Requests with the same Issue Type, Impacted Are and Problem Code (Same “Matrix” options selected). [EA-708]

Service Request - For Requests created in Core, the duplicate check will now also validate the Floor and Space if populated.

• If the Request is at the Building/Location level, a duplicate SR would also need to be at Building/Location level with no Floor or Space selected.
• If a Request is at the Floor level (meaning Building/Location + Floor), then a duplicate SR would also need to be at the same Building/Location + Floor level, without a Space.
• If a Request is at the Space level (meaning Building/Location + Floor + Space), then a duplicate SR would also need to be at the same Building/Location + Floor + Space level.
• DNote: All levels of the duplicate check validate against other open Service Requests with the same Issue Type, Impacted Are and Problem Code (Same “Matrix” options selected). [TAC-4395]

Space

MAC - Enhanced the update of the locker location to use the locker that best matches the person’s From Location. [TAC-3188]

Space Management - We enhanced the Calculate Closest Building functionality to allow clients to clear the closest building for inactive buildings from the People records for a given set of buildings. [TAC-4267]

Space Management - Enhanced the printing of Flexible areas to give a sort by option when Display HR Names in Flex Area is chosen. [TAC-3214]

Space Management - Enhanced the drawing viewer to add the Area Type in front of the Area Name when assigning a space to an area.  This will group all the areas with the same type together and make it easier to search for an area type when using the multiple space edit. [TAC-3115]

Space Management - Enhanced the Floor Plan viewer search functionality, to see all results or results by People, Spaces and Assets. [TAC-3092]

Space Management - Fixed an issue to automatically update a building’s lease expiration date when it changes on the lease and the building’s measurement type is ‘Lease-Building Calculated’ [TAC-2326]

Space to Reserve - Enhanced the person sync functionality to include the Preferred Name.  The Preferred Name field in Reserve is mapped to the OTHER_NAME filed in Space. [TAC-4058]

Reserve

Web Application - An asset's “Requires Check In/Check Out” policy can now be changed when active reservations exist for a given asset. The check in setting at the time of reservation creation will be enforced. In some cases the reservation's status and history will reflect the current policy on the asset rather than the policy that was in place when the reservation was created. If the asset’s check in policy is changed between the reservation start time and end time, then in some kiosk applications the user may not be able to check out of or end the reservation. In those cases the user may check out of or end the reservation within the web application or mobile apps; or they can let the reservation expire automatically at the end time. [AQCORE-1148]

Web Application - Added a property which controls display of the Google Map in the Reserve Web Application for an organization. By default, property google.map.show is enabled. To disable it for your organization, create a support ticket. When disabled, the Google Map is hidden in the Search By List page, Asset Details page, and Manage Reservation page. The Google Map remains visible in the Manage a Location Details page and the Location Details page regardless of the property setting. [AQCORE-509]

Web Application - When the MS Teams checkbox option is enabled, the checkbox is no longer shown for workspace reservations, only for collaboration spaces. [AQCORE-1877]

Web Application - Added reservation comments to the pop-up displayed when hovering over a reservation on the floor plan or calendar grid. [AQCORE-1809]

Data Management Utility - When a location is outside of the United States, the fields for State/Province and Zip/Postal Code are no longer required. [AQDMU-44]

Data Management Utility - The DMU now supports conditions when the language tag for an asset type (or similar element in Reserve) has been modified from the default value. [AQDMU-48]

Crestron Room Kiosk - Reduced height of input window for improved compatibility with on-screen keyboard. [AQDS-334]

Crestron Room Kiosk - Added two new images that can be used as the image for the associated room, which is the background on the home screen. [AQDS-329]

Occupancy

Badge events are now ingested and stored as building-level aggregations. This update introduces a dedicated API for badge data and retroactive updates to aggregations when new events occur. [OCCDEV-10855]

Occupancy data warehouse stores assigned geo level entry per building, enabling the usage of country and property level filters in the OBIEE dashboard. [OCCDEV-10917]

Occupancy data warehouse stores assigned building per person from Core, enabling the calculation of headcount metrics per building and team. [OCCDEV-10927]

User-level anonymization for stored occupancy events is configurable via a on/off toggle, enabling the collection of individual user metrics where contractually permitted. [OCCDEV-10907]

Energy & Sustainability

Historically, if an account is linked to ENERGY STAR Portfolio Manager (ESPM) and is pulling data from ESPM into WatchWire (WW), then certain updates in ESPM would automatically sync to WW and overwrite data, while others would create a new invoice and need to be manually reviewed.  If the start and end dates (e.g. 5/10/25 to 6/9/25) in ESPM remained the same, but any of the other fields (usage, cost, demand, etc.) changed, then that new data would automatically overwrite what’s in WW.  However, if either the start or end date changed (e.g. from 6/9/25 to 6/10/25), WW would assume it’s a new invoice (not a correction) and there would be a duplicate invoice in WW that would need to be reviewed.  Moving forward, in these situations we will be automatically updating the changed start or end date, rather than creating a new invoice, so as to prevent duplicate invoice creation. [WATX-2057]

Emissions allocations can now be allocated with decimal precision (e.g. 93.7% Scope 2 and 6.3% Scope 3) vs. whole integers (e.g.94% scope 2 vs. 6% scope 3). [WATX-1900]

The Sentence Filter report now includes a column that identifies the billing period frequency ((Monthly, Bi-Monthly, Quarterly, Bi-Annual, Annually, Irregular) so users can review to confirm billing gaps are expected. [WATX-2124]

Historically, we set and track the Data Provider at the account level. We added another label at the Invoice Details level - in the header section - that shows the Data Provider at the statement level, since it could be different in some cases. Those cases are typically when invoices are first onboarded (historical import) manually, and any manual data entry. [WATX-2012]

Datamart

Added new column: PAYMENT_TIMING to the tables D_LEASE_ACCT_SCHEDULES, F_LEASE_ACCT_SCHEDULES, and F_LEASE_FINANCIALS [TAC-4501]

Added below new columns to the table: DM_PROPERTIES [TAC-4355]

• SEC_ATTR1
• SEC_ATTR2
• STORE_SIZE
• UOM
• C_EXT_ATTR11
• C_EXT_ATTR12
• ADDRESS2
• OPEN_DATE
• CLOSE_DATE

Added new column UNIT_WID to the below tables: [TASD-110604]

• F_LEASE_COST_PROJECTIONS
• F_LEASE_FINANCIALS_ATTR
• F_LEASE_PAYMENTS
• DM_LEASE_PAYMENTS
• F_LEASE_COST_ALLOCATIONS

Added below new tables: [TASD-110604]

• D_LEASE_OPTION_ATTR
• F_UNIT_OPTION_ATTR
• D_LEASE_WRKSHT_SUMMARY
• D_LEASE_WRKSHT_DETAIL
• F_UNIT_WRKSHT_SUMMARY_DETAIL

Platform

N/A

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.