Chateau Release Notes – Fixes & Improvements
Dashboard
• Redesigned operations dashboard with new compliance and performance widgets. (Beta).
The Chateau home dashboard has been rebuilt with a customizable drag-and-drop layout. New widgets give you a live view of inspection burndown (M21/AVO/OGI/CT) with pacing and projections, tour coverage by period, deadline pressure across your open leaks, leak trends by location unit and component type with trailing 12-month history and average repair time, and a technician scorecard — click any technician to see a breakdown of their PPM distribution, leak find rate, and monitoring stats.
Widgets can be shown, hidden, and rearranged per user, and custom metric widgets can be added.
This is an early-access feature — if you are interested in trying it, please reach out to LDARtools Support.
Leaks
• Fixed indexed leak response time due dates (First Retest Due, Final Resolution) remaining blank
when a component's first repair attempt was logged in the same check-in as the inspection that
opened the leak.. The mobile check-in processes repair attempts before the corresponding
inspection, so the due-date recalculation ran before the leak record existed, found nothing to
calculate, and was never re-triggered. The fix ensures the recalculation runs again after the leak is
opened — across all three inspection types (M21, AVO, and OGI) — so due dates populate correctly
even when the first attempt arrives in the same batch.
Porches
• Fixed No Noon Drift porch generating false positives and No End-of-Day Drift porch never firing.
Both porches determine whether a drift record was found by reading a field that is blank on
calibration data synced from a physical analyzer via Chateau Mobile — so on affected databases, the
check always returned the wrong answer. No Noon Drift flagged analyzers as missing a noon drift
even when one had been recorded for the day, generating a continuous flood of false positives. No
End-of-Day Drift, using the same flawed check, returned zero rows and never surfaced genuine end-
of-day drift failures.
Tours & Scheduling
• Auto Tours — automatically build tours on a recurrence schedule. (Beta).
A new Auto Tours tab under Tours lets you save a component filter and a build schedule once, and Chateau builds tours for you automatically on that cadence — drawing from your saved component filter and the current
inspection schedule.
Weekly, bi-monthly, monthly, quarterly, semi-annual, annual, and one-time schedules are supported; tours can be grouped by Location Unit with an optional size cap. You receive email notifications when a build succeeds, fails, or finds no matching components — any Chateau user or email address can be added as a recipient. A new Tours Management role controls who can create and manage auto-build schedules.
This is an early-access feature — if you are interested in trying it, please reach out to LDARtools Support.
• Fixed Next M21 Why and due date persisting after a component is removed from an Evergreen
tour. When a component was removed from an Evergreen tour after its inspection window became
overdue, the Next M21 Why and due date that had been applied by the tour remained on the
component record instead of clearing from the grid.
Components
• Fixed components added on TUx profiles not receiving inspections when activated. Components
originally added with a starting profile of TUPurged or TUinService did not receive inspection
requirements when their profile was later changed to Active. An initialization record needed to mark
the activation date as the scheduling start point was not being created on the auto-approve
activation path.
• Fixed Multi-Edit OK button staying disabled when only Active Why is changed. In the New
Component Porch, selecting two or more components and changing only the Active Why reason —
without changing the Profile itself — left the OK button grayed out and prevented the edit from
being saved.
• Fixed Yes/No property columns displaying blank for some components in the grid. Several Boolean
component properties — including UTM (Unsafe To Monitor) — displayed blank in the Component
grid for a subset of components even when the correct value appeared on the individual component
record. A historical or backdated property record could cause the grid's cached display value to fall
out of sync with the component's current active record.
• Fixed Equipment Ref Doc column displaying blank in the Component grid. The Equipment Ref Doc
column (sourced from the Equipment's MOC Reference field) displayed blank for all components,
even when a value was stored on the record. A missing column alias in the grid mapping prevented
the field from appearing.
• Fixed DOR Status column displaying blank in the Component grid. The DOR Status column showed
blank for all components due to a case mismatch in how the column name was registered versus
how it was returned in the component data.
• Fixed Next AVO Due and Next M21 Due filters excluding components due on the last day of the
range. When filtering the Component grid by Next AVO Due or Next M21 Due with a date range,
components whose actual due date fell on the last day of the range were excluded. The filter was
comparing against a date one day later than the date displayed in the grid.
• Fixed Previous Profile filter returning an error in the Component grid. Filtering the Component grid
by Previous Profile returned a server error and no results. The filter option was available in the UI
but was missing an internal lookup mapping required to resolve the filter value.
• Fixed duplicate Component entry in the Settings Picklists category dropdown. The Settings →
Picklists page listed Component twice in the Category dropdown. One entry showed only the
PhysicalState picklist while the other showed the remaining Component picklists. All Component
picklists now appear together under a single entry.
• Fixed Chateau Mobile sync writing TUx profile records with a blank availability date. When a
technician changed a component to a TUPurged or TUinService profile through Chateau Mobile
check-in, the sync processing path bypassed the required-field validation that the Chateau web
interface enforces, writing a profile record with no availability date set. The missing date caused
those components to show inconsistencies in TUx availability reporting.
Resources
• Fixed duplicate cylinder entries created during Spanbox sync. When the same physical cylinder was
synced from a Spanbox device, a duplicate entry could be created if the device used a different
internal identifier than the original cylinder record. The sync now matches cylinders on their physical
attributes to prevent duplicates.
Reports
• Fixed page number in the TUx Summary report footer wrapping to a second line on large reports..
On TUx Summary reports exceeding 999 pages, the footer rendered as Page N of N on one line and
N on the next instead of Page N of N on a single line.
Rules
• New Minimum Days Between Inspections setting on rule frequency grids. A new Min. Days
Between column is now available on the M21, OGI, AVO, and Cooling Tower frequency grids in rule
settings. When configured, a component's next inspection window does not begin until the specified
number of days have passed since the previous inspection. Leave blank (the default) for no
minimum. This option was previously only configurable by contacting LDARtools Support; it can now
be set directly in rule settings.
API
• New read-only option for API access tokens. When generating an API access token in Majordomo,
database administrators can now mark it as **Read Only**. A read-only token can retrieve data
from any read endpoint but is blocked from creating, updating, or deleting records — making it safe
to share with external reporting tools, auditors, or third-party integrations. This option is visible to
all database administrators and is set at creation; it cannot be changed after the token is issued.
Settings
• Work Days & Holidays calendar now includes a Crew work schedule. The Business Days & Holidays
page has been expanded and renamed to **Work Days & Holidays**. The calendar now tracks two
separate schedules on the same page: the **Deadlines** schedule (the compliance business days
that drive leak-response due dates, unchanged from before) and a new **Crew** schedule (the
days your crew actually works, for pacing and workload projections). A monthly capacity preview
shows working days and available capacity at a glance. Editing the Deadlines schedule requires an
explicit unlock step to prevent accidental changes. Requires the Settings and Resource Management
role.
General
• Fixed selected theme resetting to the default on page refresh. Selecting a Chateau display theme
and refreshing the page reverted to the default Style42 theme. The Clean & Green(dark); theme
also did not persist at all. Theme selection now saves to your user profile and follows you across
devices and browsers.
• General bug fixes and stability improvements.
Chateau Mobile
Analyzers
• Fixed manual PPM entry carrying over to the next calibration cylinder. During a multi-cylinder drift
check or confirmation test, typing a manual PPM value for one cylinder caused that same value to
be silently recorded for the next cylinder if no new value was typed for it. Each cylinder now starts
with a blank entry, recording either the manually typed value or the live analyzer reading.
General
• Fixed erroneous update available prompt appearing on every launch. Android devices running the
current version of Chateau Mobile displayed an update to new version prompt on every launch,
even when the app was already up to date. The app now checks the actual Play Store version and
only prompts when a genuine update is available.
Comments
0 comments
Please sign in to leave a comment.