Leaks

Alerts for open DORs. 

You can now be emailed about open Delays of Repair the same way you are about leaks. The Leak Alerts sub-tab is now called Alerts, and Add New asks whether the alert is about Leaks or DORs. A DOR alert is set up exactly like a leak alert — choose which components it covers, choose who receives the email, and choose when it sends. An alert’s type is set when you create it and cannot be changed afterward, because its saved query filters on fields specific to that type.

Alerts can now send weekly or monthly, not just daily. 

Alerts used to have a single Frequency setting, and every option except Immediately Upon Check-In sent daily. That is now two settings: Content rule, which decides what goes in the email, and How often, which decides when it sends — Daily, Weekly on a day you choose, or Monthly on a day you choose or the last day of the month. Your existing alerts keep sending daily exactly as they do now, and a new DOR alert starts on Weekly / Monday until you change it. Alerts set to warn you within 2, 3, or 4 days of a due date stay daily, so the warning still reaches you before the deadline.

Alert emails now show what closed, not just what is still open. 

Every alert email has two sections: what is currently open, and what closed since the last email. On a weekly or monthly schedule, this means work your team finished during the period is still reported instead of dropping out of the email entirely.

Tours and Scheduling

Auto Tours can be grouped by any component property. 

Auto Tours could only be split up by Location Unit. You can now split tours by multiple component properties, applied in the order you list them. Each tour then covers a single value of every property you chose: grouping by Area and then LUnit gives you tours that each cover one Area and, within that Area, one LUnit — so Area North / LUnit 5 and Area North / LUnit 6 build as separate tours.

Auto Tour names can include component property values. 

The Tour Name field already accepted variables such as the build name, the date, and the LUnit; it now accepts any component property. Naming a tour after a property you grouped by gives you that tour’s single value. Naming it after a property you did not group by lists up to three values alphabetically and then "+N more" — so a tour spanning six LUnits reads "LUnit 1, LUnit 2, LUnit 3 +3 more". The Tour Name Example beneath the field fills in real values from your data so you can see the result before saving, and a finished name is capped at 100 characters.

Auto Tour notification emails now name the database. 

The database name is added to the beginning of every Auto Tour build notification subject line, so recipients who receive these emails from more than one database can tell them apart.

Reports

New Comp Type filter on Component Count by Regulation. 

The report can now be restricted to one or more component types instead of returning the whole facility and filtering afterward. All types are selected by default.

API

New public endpoint for scheduled inspection requests. 

Partner integrations can now query scheduled inspection requests — due date, inspection type, and inspection reason — through GET /v1/InspectionRequests/Scheduled, without the request first having to be added to a tour. Query metadata is available at GET /v1/InspectionRequests/q.

Chateau

Components

Fixed closed DORs still showing as open on the Component Grid. 

After a DOR was closed, the Component Grid still showed DOR Status = Yes and the On DOR indicator stayed lit on the tag header, so the tag kept coming back when the grid was filtered for DOR Status = Yes — even though the Leak Grid and the component’s Leaks tab correctly showed the DOR as closed. Closing, opening, and reopening a DOR now update the Component Grid right away.

Fixed the Tag# field stacking vertically on narrow screens. 

On Component Details, the Tag# value in the tag box rendered one character per line when the browser window was narrowed. It now stays on one horizontal line at every width.

Inspections

Fixed Edit clearing values on inspections opened from the M21 Variance porch. 

Using View Inspection on the M21 Variance porch and then clicking Edit behaved as though you were creating a new inspection for the tag — Technician, Analyzer, M21 Why, and Detector Type blanked out, and every other field reset to its default.

Tours and Scheduling

Fixed check-ins left in Processing. 

When Chateau hit an error while processing a check-in, it stayed on Processing on the Chateau Mobile Sync Status screen with no sign that anything had gone wrong. It is now marked Failed Processing, so it can be reprocessed from that screen.

Fixed "Next OGI Reason" and "Next Cooling Tower Reason" field labels. 

In the Add Fields to Query picker — used by Auto Tours, the Components List, and everywhere else you add fields to a query — the OGI and Cooling Tower fields were labeled "Reason" while AVO and M21 correctly said "Why." They now read Next OGI Why and Next Cooling Tower Why.

Rules

Fixed Site Type showing as "Property removed" in Assign Rules. 

Rules that matched on Site Type showed that condition greyed out and labelled "SiteType — Property removed," and it could no longer be edited — although the saved rule was still filtering on Site Type behind the scenes.

Fixed components closed as misidentified being left in the monthly (M1) phase. 

Opening a leak drops a component back to M1, and closing it with Leak Close Why = Component MisIdentified left it there — so a component that had already worked its way up to the quarterly phase had to earn it back over roughly two months, even though the leak was never real. The component now returns to the phase it held before that leak opened, on MMQ, AMM and SMM alike, and the Component Grid reflects it right away.

Reports

Fixed tags missing from the Deactivated Component report when they were deactivated at the start of the period. 

A tag deactivated effective the first day of the reporting period — midnight local time, the time set for a backdated MOC edit — did not appear on the report. A tag’s regulation coverage ends the moment it leaves service, so a deactivation effective at the very start of the period read as though the tag was no longer covered by the regulation being reported on.

Fixed missing DOR information on the Full Data Leak History report. 

DOR Auth By, Est Rep Date, and DOR Status stayed blank unless the report’s end date fell after the DOR’s Date Approved — so running the report for the month the leak was found, or for the same day the DOR was approved, returned no DOR data. The DOR columns now follow the leak. The OGI version of the report is fixed by the same change.

Majordomo

Fixed database administrators being blocked from removing a user’s assignment. 

On a security group’s Assignments tab, Remove Assignment and Edit stayed greyed out with the tooltip "Only administrators of this can remove assignments," even for an administrator of the database in that row. The rows on that tab are databases, but Chateau was checking whether you administer the security group rather than the database itself. It now checks the database in the row, and when a removal is not permitted the message names the database you need access to.

OGI

Fixed large OGI video uploads getting stuck on "uploading." 

A video was sent as one single upload that the connection closed after about a minute, so large files never finished — and a video whose data did arrive but failed to attach still reported Upload Complete. Videos are now sent in smaller pieces, and a failed attach is reported as a failure. This applies to both the OGI Import screen and the Sensitivity Checks grid.

General

Fixed screens sitting on "Loading" after a brief connection drop. 

When the connection to Chateau dropped and came back, a grid could stay on Loading indefinitely and only recover by reloading the browser.

General bug fixes and stability improvements.

Chateau Mobile

Inspections

Fixed the Add New button appearing on the Emission Point list when it was turned off. 

Chateau Mobile has a setting that controls whether technicians can create new emission points while entering leak details. The + Add New button appeared at the bottom of the Select Emission Point list whether or not that setting was turned on, and tapping it did nothing. It now appears only when the setting is on, and turning the setting on or off takes effect the next time a technician opens the list.

Sync

Fixed check-in reporting a failure when the work had already reached Chateau. 

A check-in uploads everything on the handheld, not just that day’s work, so on a large site Chateau Mobile could stop waiting before Chateau had finished receiving it — while Chateau went on to save the day’s work regardless. Check-in now confirms the result with Chateau before reporting it, so a successful upload is no longer reported as a failure that leaves the device on Checked Out.

Clearer messages while checking in. 

The confirmation step now reports each attempt instead of going quiet while it waits, and cancelling a check-in yourself is reported as a cancellation rather than an unexpected service error.

Fixed check-in failing for analyzers with all-numeric serial numbers. 

Chateau could not read an analyzer serial number that was made up only of digits, with no letters. Because Chateau will not accept an analyzer record whose serial number it cannot read — it would have no way of telling which instrument the reading came from — it rejected the technician’s whole upload rather than the single record.

General

General bug fixes and stability improvements.