> ## Documentation Index
> Fetch the complete documentation index at: https://docs.kodelabs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# What's new in KODE 3.19

> October 2026 (v3.19) product updates across Building BI, FDD, integrations, AssetOps, and Document Management.

![What's new in 3.19 banner](https://mintcdn.com/kodelabs/B-pwNrO91ylawNjH/images/whats-new/whats-new-v319-banner.gif?s=5d5fa33511409c125374940afebb8e8b)

# October 13, 2026

## Highlights

[See full release](#full-release-notes)

KODE 3.19 introduces **parameters** in 

Building BI (Building BI is the analytics module for dashboards, charts, and portfolio insights.)

 

and **Event Triage Rules** in 

FDD (Fault Detection and Diagnostics (FDD) finds building issues from broader analysis, not just simple instantaneous alarms.)

. We've also shipped a ZenControl lighting connector, a Smart Meter Texas connector, spreadsheet schedule import in 

AssetOps (AssetOps is the KODE module for assets, schedules, and maintenance work.)

, and a faster connector setup flow.

## Parameters in Building BI

Name a value once on a 

data source (A data source is the dataset a Building BI chart reads, including its columns, metrics, and calculations.)

. Reference it as `@name` in calculated columns, calculated metrics, and virtual data source SQL.

Each dashboard stores its own values. Open `Parameters` beside `Filters` and change a target, rate, or baseline. The widgets that use it recalculate.

A viewer's change stays on that screen until refresh. The data source and other dashboards stay as saved.

Choose a display name, a type, and a default. You can add an allowed-values list, require the value, block dashboard overrides, or lock it for viewers.

Shared dashboards, mobile view, and PDF export show the saved values.

![Adding a Building BI parameter and referencing it in a calculated column](https://mintcdn.com/kodelabs/B-pwNrO91ylawNjH/images/whats-new/whats-new-v319-parameters.gif?s=93f4ba7d03a1f358917c6a38b134c691)

Add a parameter, then reference it as `@name` in a calculated column

[Learn more about parameters](https://docs.kodelabs.com/products/building-bi/data-sources.md#parameters)

## Event Triage Rules in FDD

**Event Triage Rules** decide what happens to a 

work order (A work order is a maintenance job in a connected work order system.)

 

after 

FDD (Fault Detection and Diagnostics (FDD) finds building issues from broader analysis, not just simple instantaneous alarms.)

 

raises an 

event (An event is a device-reported occurrence that building management reviews or resolves.)

. The rules follow the status your 

CMMS (A CMMS is the external system that tracks maintenance work orders.)

 

sends back, so the work order stays aligned with the alarm.

Five rules run on their own:

* **Bad closure** reopens a work order the CMMS closed while the alarm is still active.
* **Recurrence reopen** brings the original work order back when the same alarm returns.
* **Hold and release** holds lower-priority work until a high-priority event fires at the same building.
* **Carry forward** keeps the open work order when a new alarm hits the same device.
* **Self-resolving cancellation** cancels the work order after the alarm stays quiet.

You can also group events yourself. Select two or more active events at one building and send one work order.

Open the rules from `Settings`, then `Triage Rules`. A work order connector is required.

![Event Triage Rules settings with enable toggles, labels, and timing parameters](https://mintcdn.com/kodelabs/B-pwNrO91ylawNjH/images/whats-new/whats-new-v319-event-triage.png?fit=max\&auto=format\&n=B-pwNrO91ylawNjH\&q=85\&s=ff518cf24afd86f6308bc128818f9f32)

Turn each rule on, set the window, and choose which priorities release held work

[Learn more about Event Triage Rules](https://docs.kodelabs.com/products/fdd/settings.md#event-triage-rules)

## Full release notes

User-facing product updates in 3.19. Integration items include the September 29 patch on 3.18.

### Building BI — Dashboards and data sources

* **Parameters** — Declare a typed value on a data source and reference it as `@name` in calculated columns, calculated metrics, and virtual data source SQL. Dashboards store their own values. Viewers can run a private what-if that clears on refresh. Shared links, mobile view, and PDF export keep the saved values. See [Parameters](https://docs.kodelabs.com/products/building-bi/data-sources.md#parameters).

### FDD — Fault Detection and Diagnostics

* **Event Triage Rules** — Five rules keep work orders aligned with live alarms: bad closure, recurrence reopen, hold and release, carry forward, and self-resolving cancellation. You can also group two or more active events at one building into one work order. Configure them under `Settings` > `Triage Rules`. A work order connector is required. See [Event triage rules](https://docs.kodelabs.com/products/fdd/settings.md#event-triage-rules).

### Integrations (API)

* **ZenControl** — Lighting connector for ZenControl sites. REST polling plus Live API events for dim level, scene, colour temperature, override, and gateway connection. Writable points cover dim level, scene, colour temperature, and override. See [ZenControl](https://docs.kodelabs.com/products/integrations/lighting/zencontrol.md).
* **Smart Meter Texas** — Read-only REST connector for Texas electric meters. Discover meters by ESIID and meter number. Collect 15-minute consumption and generation interval reads, plus meter status, disconnect, phases, multiplier, and reverse-flow handling. See [Smart Meter Texas](https://docs.kodelabs.com/products/integrations/meters/smartMeterTexas.md).
* **Service Channel (Lowes) work orders** — The Create Work Order action sends the asset tag and FDD event details in `Description`, maps `AssetId` from the linked device, loads `ProblemType` and `AssetType` from Service Channel, and sets `ScheduledDate` from the priority turnaround. See [Service Channel (Lowes)](https://docs.kodelabs.com/products/integrations/work-orders/serviceChannelLowes.md#available-actions).
* **Connector setup** — `Validate Credentials` loads vendor fields in the background and shows progress. Errors name the cause, and you can retry. When a multi-select vendor field has no options, type comma-separated IDs. See [Managing connectors](https://docs.kodelabs.com/products/integrations/get-started/managing-connectors.md).
* **Discovery metadata** — Discovered devices include manufacturer, model, firmware version, OS version, MAC address, and IP address when the connector provides them. See [Discovery](https://docs.kodelabs.com/products/integrations/capabilities/discovery.md).
* **Connector details date column** — Non-sensor data tables show which date column the selected range applies to, such as `Created At (Local)` or `Collected At`. See [Managing connectors](https://docs.kodelabs.com/products/integrations/get-started/managing-connectors.md).
* **AssetOps work orders** — Collected work orders map `category.name` to `category` and `issueType.name` to `subCategory`. See [AssetOps connector](https://docs.kodelabs.com/products/integrations/work-orders/assetOps.md).
* **Lutron Athena** — Collection skips a device Lutron has removed and continues for the rest. The connector stays up. See [Lutron Athena](https://docs.kodelabs.com/products/integrations/lighting/lutronAthena.md).
* **Wattics** — Point history collection skips a device or point that Wattics has removed. The job continues for every remaining device, and the connector stays up. See [Wattics](https://docs.kodelabs.com/products/integrations/meters/wattics.md).
* **Kastle** — Access Log collection redacts credential holder name, email, and phone by default. Each character is replaced with `*`. Alarm collection is not redacted. See [Kastle](https://docs.kodelabs.com/products/integrations/access-control/kastle.md).
* **Service Channel** — `Store ID` and `Subscriber ID` are drop-downs when the store list loads. If the list is empty, both fields are text boxes. See [Service Channel](https://docs.kodelabs.com/products/integrations/work-orders/serviceChannel.md).

### AssetOps

* **Import schedules from a spreadsheet** — Upload a spreadsheet based on the schedule template to create schedules in bulk. KODE OS checks the data and reports success or the rows to fix. See [Import schedules](https://docs.kodelabs.com/products/assetops/schedules/schedules-overview.md#import-schedules-from-a-spreadsheet).
* **Dashboard date range** — The `Created date` range you pick on the AssetOps dashboard stays in place for your session. You can return to the default range at any time. See [Building dashboard](https://docs.kodelabs.com/products/assetops/building/dashboard.md).

### Document Management

* **Section field** — The CSI specification field under a division is labeled `Section` in document details, filters, upload, and bulk edit. See [CSI divisions](https://docs.kodelabs.com/products/kode-os/documents/overview.md#csi-divisions).

## Improvements and bug fixes

### AssetOps

* **Schedules** — The task template picker shows an `Asset Type` column, and `Select All` honors your search and any templates you cleared. Start dates must fall between 1970 and 2099, with inline validation. Calendar event titles fit inside their blocks, and schedule type validation runs when you select `Continue`.
* **Assets** — Asset dates display on the correct day in every building time zone. The asset list shows `Active` and `Out of service` assets. Bulk edit offers `Add New` for manufacturer, and the unit field on technical specifications is required. Opening a deleted asset returns you to your last location.
* **Dashboards and layout** — The maintenance forecast dashboard shows charts without a paginated table. Checkbox sizes, dashboard fonts, and asset name headers are consistent. Floor plan, system, and device graphics use the updated design.
* **Work orders** — On the portfolio work order form, the `Area` dropdown waits for a building selection.

### KODE OS

* **Text display** — Clamped text without spaces wraps cleanly across KODE OS, Launchpad, and Client Admin.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.