Skip to main content

Reference/Glossary

Key terms used throughout the IrisX App SDK documentation.

IrisX App​

An installable unit that customers can find and install from the Trackunit Marketplace. An app is a container — it bundles one or more Extensions, defines marketplace metadata (name, description, screenshots), and controls the installation policy.

Extension​

The unit of functionality inside an app. An extension targets a specific Extension Point in Trackunit Manager and contains the React code and business logic the end user interacts with. One app can contain multiple extensions.

Extension Point​

A named slot in Trackunit Manager where an extension can render UI or execute logic. Examples: Asset Home, Fleet, Widget, Report, App Settings, Administration, Customer Home, Asset Events Actions, App Lifecycle.

Workspace​

An NX monorepo that holds all your IrisX Apps and Extensions. The recommended approach is one workspace per developer or organisation, containing all apps and shared libraries.

Manifest (iris-app-manifest.ts)​

The single configuration file for an IrisX App, written in TypeScript. See the App Manifest reference for every field.

moduleFederationName​

The unique identifier used to load your app at runtime. See moduleFederationName.

specVersion​

The version of the manifest schema, set by the SDK tooling. See specVersion.

Scope​

A permission your app requests in its manifest in order to call Trackunit APIs. See scopes.

Custom Field​

An app-defined data attribute that can be attached to Trackunit entities (Asset, Account, Group, Site). Custom fields are defined in the app manifest and owned by the app that defines them.

App Token​

A short-lived credential issued to your app, scoped to the installing customer's account. See IrisX app tokens and API access.

cspHeader​

The Content Security Policy your app declares in its manifest, controlling which external origins it may contact. See cspHeader.

permissionsPolicy​

The browser features and shared resources your app's iframe may use. See permissionsPolicy.

TU_TOKEN​

An API token used to authenticate the submitApp CLI command in CI/CD pipelines instead of interactive browser login.