Release Notes - May 9, 2025

Overview

This document describes what’s new or improved with the May 9, 2025 Tango release, which was included in Core Release 3.7.43, Edge Application Release A10.8.1, and Edge Platform Release P3.10.1.1.

What's New or Improved?

• Predictive Analytics

• Transactions

• Projects

• Lease

• Maintenance

• Space

• Reserve

• Occupancy

• Energy & Sustainability

• Datamart

• Platform

Predictive Analytics

Reports - Users can now batch process demographic reports for all store locations. The restriction to 100 records has been removed. [TAC-3916]

Transactions

N/A

Projects

Project Document Collaboration - Added a notification procedure which can be configured to automatically notify a designated role by email when a document is uploaded via document collaboration in EDGE. The notification email will be sent to a designated contact role called “Vendor Document Notification Recipient.” [TAC-3375]

Project Vendor Invoicing (in Edge) - Updated to support and display the “Exported” Status in Edge for clients who have Invoices sent to an outbound integration before marking them Paid. [EA-458]

Purchase Orders - Created new optional validation for when Purchase Orders are associated to an SLA agreement. This will check PO amounts against the SLA contract amount to ensure the high-level agreements can be enforced across multiple projects. [TAC-3044]

Target Mobile - Added additional filter parameters to the Target search page for the Tango Workplace app. [TAC-3229]

Vendor Invoicing - Created a new mechanism to notify a designated project role (“Edge Invoice Notification Recipient”) via email when an invoice is received into the system from the Vendor invoicing portal. [TAC-3389]

Workplace - Added a detailed supplier record view to the mobile application. [TAC-2973]

Lease

GL Accruals - Added new export feature that improves performance through a batch process export/download option. [TAC-3797]

Lease Abstract (Standard Report) - Updated Lease Abstract standard report to sort the option section by Option Start Date then Option Type. [TAC-3803]

Recurring Costs - Added support for bi-monthly (every two months, 6 payments per year) and tri annually (every four months, 3 payments per year) recurring cost frequencies. [TAC-3336]

Maintenance

Work Order Invoicing - Vendor Line Item “Name” Field (Label = Item) is no longer editable during creation of the WO Invoice. New Items can still be added with any Item name given, but the default and existing items can no longer be edited. In addition, Invoice Detail Items can no longer be deleted.

A new Comment field is now available on the Invoice Detail items allowing the user to enter ad hoc details about the Item, if they so desire. Since the Item name is no longer editable, this gives the user a way to enter specific information if needed. [EA-516]

Work Order Invoicing - Updated to support and display the “Exported” Status in Edge for clients who have Invoices sent to an outbound integration before marking them Paid. [EA-458]

Space

Space Management - We have enhanced Visual Query for Buildings to show all Space attributes including additional attributes. Additionally, we have added the Building entity to Bulk Update using all the Space attributes including additional attributes. When configured, this allows for editing specific space attributes, including additional attributes, across multiple spaces at one time. [TAC-3413]

Reserve

Stability - Implementing measures to improve performance of the system as a whole. This initiative will be carried out over multiple release cycles. [AQ-75]

Occupancy

N/A

Energy & Sustainability

Historically, Building Balance (BB) accounts subtracted reference account data from aggregate building level data based on reference account billing month/year, irrespective of the reference account start date / end date. This was an acceptable methodology when it was unknown if the source aggregate building level data was pre-calendarized (1st of month to end of month) or simply aggregated to the billing period and entered into ENERGY STAR Portfolio Manager as 1st of month to end month. With enough evidence suggesting that utilities are indeed pre-calendarizing the aggregate data, we are updating our methodology to calendarize the reference account data before subtracting from the aggregate data. For example, if a reference account has a Jan 2025 billing period with a start date of 1/10/25 and end date of 2/9/25, for the Jan 2025 Building Balance account, the 1/10/25-2/9/25 data would be subtracted from the aggregate data. With the updated methodology, this data will now be calendarized with the prior month invoice data and 1/1/25-1/31/25 would be utilized. [WATX-1367]

When users with GRESB module access set an asset to “Whole Building = False”, emissions will be allocated per the table below (dependent on the utility commodity type and the asset and account GRESB configurations), regardless of the emissions allocations set at the account level within WatchWire. This allows users to set account level emissions for their GHG inventory / annual reporting, while also reporting to GRESB per GRESB specifications. [WATX-1114]

Sentence Filter Report will now display 4 decimal places on non-currency numeric fields (trailing zeros will be displayed). [WATX-1290]

AP Status Improvements - Removed “Ready for AP Processing” and added AP Status Message underneath the existing AP Status Field. [WATX-1398]

Consumption data (and derived emissions data) in the GRESB ALS is based on calendarized billing data (i.e. 1st of month to end of month vs. true billing period start/end dates). As such data availability was historically reflected as 1st of month to end of month. With this latest update, starting month data availability will be based on the starting month billing period start date and the ending month data availability will be based on the ending month billing period end date to more accurately reflect true number of days coverage. [WATX-1384]

Datamart

N/A

Platform

Documents - Enhanced the document workflow engine to auto lock documents from editing once approved. Documents can still be manually unlocked by someone with the correct permissions. This auto locking will only apply to those using the Documents Approval Work Flow. [TAC-3380]

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.