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 worklist entry /fw/workflows does not correspond to a route in src/routes/fw.tsx. There is no standalone “Workflows” list page registered. Workflow definitions are managed through automation rules accessed at /fw/automations and edited via the Workflow Editor at /fw/automations/:id/workflow.

​
Overview

Based on the shipped codebase, there is no dedicated /fw/workflows route registered in the FW router. Workflow graphs are associated with automation rules: each automation rule can have a visual workflow definition edited at /fw/automations/:id/workflow. To create a new workflow, a user first creates an automation rule on the Automations page (/fw/automations) and then navigates to its Workflow Editor. The route /fw/workflows/:workflowId/analytics does exist and is documented separately at Workflow Analytics.

​
Who it’s for

No explicit permission gate exists on this route because it is not registered. Access to the related Automations page and Workflow Editor is unguarded at the router level; data-layer permissions apply.

​
Before you start

This page documents a route that was not found in the shipped router configuration. SME confirmation is required before this content should be considered accurate.

​
Steps

SME: These steps are inferred. Confirm the correct workflow-creation path before publishing.
  1. Navigate to /fw/automations.
  2. Select “New Automation” to open the rule builder dialog.
  3. After saving the automation rule, open the rule and navigate to its Workflow Editor via the link or button to /fw/automations/:id/workflow.
  4. Build the workflow graph in the visual editor and save.

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/pages/WorkflowEditor.tsx