28 posts tagged with "Added"

CommandExecution.operationId on the public GraphQL API can now be null until the command is sent. CommandStatusType includes QUEUED and QUEUED_CANCELLED.

Drawer callsites that clear their selected value on close (e.g. isOpen={Boolean(selectedRow)}) used to hand-roll a useRef/useState "last non-null value" snapshot just to keep the panel's content visible through the ~400ms exit slide — otherwise it blanked instantly. @trackunit/react-components and @trackunit/react-drawer now ship a shared primitive for this.

Your app can now request four new manifest scopes to check an account's connections and partnerships through the public GraphQL API: connection.view, connection.manage, partner.view, and partner.manage.

New Iris App workspaces now scaffold a databricks-unity-catalog skill under .agents/skills/, alongside the existing graphql, create-app, and other skills. It guides Claude, Cursor, and other coding agents through building a SERVERSIDE_API_EXTENSION that reads or writes customer-uploaded or app-owned tables in your IrisX Analytics Unity Catalog workspace — for data that Trackunit's GraphQL API can't serve.

Your extensions can now describe their own pages to Trackunit Manager's AI assistant. Add an aiNavigation field to a manifest — a list of in-app routes, each with a path, a title, and a description — and the assistant can take a user straight to the page inside your app that answers their question instead of dropping them on its root.

This works today for every extension type that has a page a user can land on: Fleet, Admin, App Settings, Asset Home, Site Home, Customer Home, and Asset Events Actions. The field is opt-in and purely additive — apps that don't declare it behave exactly as before.

See Extension Point Types — AI navigation for the full reference: the manifest shape, both Tanstack Router styles, and in-app paths for entity-scoped extensions.

You can now inspect serverside function logs for your IrisX Apps directly in the Developer Console.

Open an app that includes Serverside API Extensions, select the Logs tab, then filter by date range and verbosity, search by message or function name, follow live entries when the range includes now, and open any row for full details.

See Viewing serverside function logs for the full guide.

The Telematics Device API now lets you roll back a previously executed configuration job. Rollback creates new configuration jobs that restore each device to the configuration it had before the original job ran.

Devices that have had their configuration changed since the original job (manually, by another job, or by automation) are excluded from rollback so the rollback never silently overwrites a newer change. A rollback request can produce more than one rollback job because devices are grouped by the previous configuration they shared.

Today, rollback is supported for CAN profile, Modbus profile, and Operating Mode changes. Other configurations the original job touched are excluded from the rollback's desired state — additional configurations will be announced as they become available.

➕ POST: /v2/configuration-jobs/{id}/rollbacks

Rollback a configuration job

A new Sheet component is now available in @trackunit/react-components. It provides a bottom-sheet UI with snap points, gesture support, and container-scoped rendering — suitable for mobile and responsive layouts.

Released stable version v2 of Assets API.

The Assets API v2 builds on the foundation of v1 with expanded querying, improved asset lifecycle management, and enhanced flexibility. In addition to onboarding, offboarding, and updating asset specifications, v2 introduces advanced filtering and pagination, asset querying by multiple identifier types, asset hiding and unhiding, and dedicated support for asset notes. The API also streamlines telematics device attachment flow, providing a more consistent and scalable way to manage assets across accounts and fleets. For more information, see the updated endpoint documentation.

Below a list of all available endpoints:

➕ GET: /asset/v2/assets

Get assets

➕ GET: /asset/v2/assets/{assetId}

Get asset

➕ POST: /asset/v2/assets

Create assets

➕ PATCH: /asset/v2/assets

Update assets

➕ DELETE: /asset/v2/assets/{assetId}

Delete asset

➕ POST: /asset/v2/assets/query

Query assets by identifiers

➕ PATCH: /asset/v2/assets/hidden

Hide or unhide assets

➕ PATCH: /asset/v2/assets/note

Update asset note

➕ POST: /asset/v2/assets/notes/query

Fetch asset notes

➕ POST: /asset/v2/assets/{assetId}/telematics-devices

Attach telematics device

Released stable version v1 of Bluetooth tag configuration API. For more information, see the documentation and introduction of the endpoints.

Below is a list of all available REST endpoints:

KIN Challenge​

➕ POST: /v1/kin-challenge/sign

Sign KIN Challenge

Utilization Profiles​

➕ POST: /v1/utilization-profiles/search

Search Utilization Profiles

➕ GET: /v1/utilization-profiles/{profileId}

Get Utilization Profile

➕ PUT: /v1/utilization-profiles/{profileId}/acknowledge-desired/{deviceId}

Acknowledge Desired Utilization Profile

➕ PUT: /v1/utilization-profiles/{profileId}/acknowledge-reported/{deviceId}

Acknowledge Reported Utilization Profile