UNS OpenHubDocumentation

Automations

Detect events and record values with Automations

Choose a Trigger to detect a condition or a Capture to record selected values, explicitly enable it, inspect runtime confirmation, and open the recorded event or closed session in Explore.

Applies to
Current compatible Runtime · documentation reviewed 18 October 2026; component requirements are stated below
Guide version
1.1

Worked example

Example: record furnace values while heating

A Capture records selected temperature/status values during an agreed state window. A Trigger can separately report a threshold or comparison event; creating either definition is not proof that its runtime is armed.

Trigger Detect an event

High/low threshold, event, comparison, string and composite rule families.

Capture Record values

Stateful windows with interval, on-change, summary or single-shot behavior where configured.

Runtime UNS API Global

The Controller authors definitions and audit; the separate service evaluates and records them.

Procedure

Follow the task in order

  1. 1
    Check the data and dependencyUse Controller 2.2.4 with compatible API Global 4.1.17. Verify source paths, value shapes, timing and permissions, then check Services health for the Triggers/Captures runtime. Authoring may remain available while evaluation is unavailable.
  2. 2
    Choose the goalOpen Automations. Use Detect an event for a Trigger or Record values for a Capture. Choose actual permitted sources from the namespace instead of entering guessed topic paths.
  3. 3
    Review a disabled definition firstSet the rule or recording window, selected values, output identity and useful description. Inspect summary and validation before saving. Cancel leaves no new definition. A valid output must not conflict with another owner.
  4. 4
    Enable deliberately and wait for confirmationUse the explicit enable/arm control. Check runtime state rather than only the saved enabled flag. Awaiting data, Unknown or a dependency error must not be read as Armed. Inspect recent fires or sessions to confirm the behavior on real input.
  5. 5
    Inspect the recorded evidenceFor a Trigger inspect the fire and its captured context. For a Capture inspect the session status, bounds and emitted row counts. Emitted audit counts do not by themselves prove archive acknowledgements; allow storage to catch up and verify actual history.
  6. 6
    Explore one closed sessionUse Explore from a closed session. Its session identifier and time bounds restrict the query as well as the authorized output topic. Changing the time window does not remove that session filter. An empty session can accurately return no rows; an open/invalid session requires a suitable supported selection rather than a broader fallback. To find the session list, open Edit capture → Recent sessions. In Controller/UI 2.2.10, Auto columns focus on time and measurements; All or Custom can reveal technical fields.
  7. 7
    Handle concurrent edits and interrupted readsIf another operator saved a newer revision, compare your draft with the saved definition and explicitly retain the draft or load the current version. Re-read runtime/audit after a restart. Authorization loss or uncertain runtime state requires investigation, not an assumption that the previous enabled rule still runs.
  8. 8
    Disable and verifyDisable a rule or capture deliberately and confirm the runtime state. Inspect whether an in-progress session has closed. Retain evidence needed for audit; deleting a definition is a separate operation.

Expected result

What you should have

A saved and explicitly enabled definition with observable runtime state, plus event/session evidence that can lead directly to a restricted historical analysis.

Boundaries

Important boundaries

  • These are focused UNS rules and recordings, not an arbitrary scheduler, email/webhook workflow system or safety controller.
  • A full independent first-time-user acceptance review remains separate from the existing functional checks.
  • Topic permissions, output ownership, runtime readiness and archival availability remain separate gates.

This versioned public guide is maintained with the UNS OpenHub website and linked directly from the controller where the task applies.