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 New Automation flow opens within the Automations list page (/fw/automations). There is no separate standalone route for /fw/automations/new; the creation experience is surfaced as an in-page dialog launched from the “New Automation” button on the Automations list.

​
Overview

The Automations page allows administrators to configure workflow automation rules. New rules are created through an inline rule builder dialog. The route /fw/automations has no explicit RequirePermission guard in the router — access control is applied at the component and data layer. Note: There is no dedicated /fw/automations/new route. The creation experience launches from the “New Automation” button on /fw/automations.

​
Who it’s for

No explicit permission gate on this route. The “New Automation” button and AutomationRuleBuilder dialog are rendered for all users who can reach the Automations page. Permission enforcement on create/save actions is handled within the rule builder component.

​
Before you start

  • An organization must be selected. If no organization is active, the page shows a message and the new-rule flow is unavailable.
  • Confirm whether the execution worker is enabled. If the worker is disabled or unconfigured, a warning banner appears on the Automations page indicating that queue-based triggers (including portal and external form submissions) will not execute until the worker is enabled. Navigate to /fw/settings to configure it.

​
Steps

  1. Navigate to /fw/automations.
  2. Select “New Automation” in the page header. The AutomationRuleBuilder dialog opens.
  3. Configure the rule name, trigger type, and actions within the builder.
  4. Save the rule. On success the dialog closes and the new rule appears in the Rules tab.
  5. To edit the rule’s visual workflow, open the rule and navigate to the Workflow Editor at /fw/automations/:id/workflow.

​
Key concepts

  • Execution worker — A background worker that processes queue-based automation triggers. The fwSettings.fw_execution_worker_enabled flag controls whether it is active.
  • Trigger type — Determines when the rule fires (e.g., form_submitted and other event-based or date-relative triggers visible in useAutomationRules).
  • AutomationRuleBuilder — The in-page dialog component responsible for rule creation and editing; opened via setBuilderOpen(true).

Forms & Workflow

Forms & Workflow core overview.

Governance & parity

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/Automations.tsx
  • src/cores/fw/hooks/useAutomationRules.ts
  • src/cores/fw/hooks/useFWModuleSettings.ts