Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.encoreos.io/llms.txt

Use this file to discover all available pages before exploring further.

The Automation Details screen shows the full configuration and most recent execution trace for a single automation rule and is available at /fw/automations/:id.

​
Overview

This screen loads the automation rule matching the id URL parameter from useAutomationRules. For rules with a trigger type of event or date_relative, an inline trigger configuration panel (EventTriggerConfig or DateRelativeTriggerConfig) is shown and can be edited directly. The most recent execution is loaded via useRealtimeExecutions and displayed as an ExecutionTrace. Domain events are listed via useDomainEvents. Action steps are managed through AutomationActionsBuilder.

​
Who it’s for

No explicit permission gate on this route.

​
Before you start

  • Navigate here from the Automations list (/fw/automations) or from a direct deep link.
  • A valid automation ID must be present in the URL.

​
Steps

1

Open an automation

Navigate to /fw/automations/:id or click a rule name in the Automations list.
2

Review trigger configuration

For event or date_relative rules, the trigger config panel is displayed and editable inline.
3

Review action steps

The AutomationActionsBuilder section lists the configured action steps.
4

Inspect execution trace

The last execution is shown in the ExecutionTrace panel with status and step details.
5

Save trigger changes

Click save in the trigger config panel; changes are persisted via useEventTriggerConfig.

​
Key concepts

  • Trigger type — event (domain event fired) or date_relative (scheduled relative to a date field); other types do not show the inline config panel.
  • Execution trace — the step-by-step record of the most recent run of this automation.
  • Domain events — platform events that can trigger automations, loaded via useDomainEvents.

Forms & Workflow

Forms & Workflow core overview.

Governance & parity

Documentation coverage and governance.
This page documents shipped product behavior. It is not medical, legal, or billing advice. Verify against your organization’s policies and applicable regulations before using it for clinical, compliance, or billing decisions. Protected health information (PHI) shown in the product is governed by your tenant’s access controls and is never exposed in this documentation.
  • src/routes/fw.tsx
  • src/cores/fw/pages/AutomationDetail.tsx