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 Approval Routing Rules screen lets administrators create and manage conditional routing rules that direct requests to specific approval chains and is available at /fw/approval-routing.

​
Overview

This admin-only screen displays all approval routing rules loaded via useApprovalRoutingRules. Each rule card shows its entity type, associated approval chain (from useApprovalChains), and an active/inactive toggle. Rules can be created, edited, toggled, and deleted. Manage access is gated by fw.approval_routing.manage (canManage flag). Deletions require confirmation via an AlertDialog. The ApprovalRoutingRuleDialog component is used for both create and edit flows.

​
Who it’s for

Requires permission: fw.approval_routing.view (route guard). Manage actions additionally require fw.approval_routing.manage.

​
Before you start

  • Hold fw.approval_routing.view to access this screen.
  • Hold fw.approval_routing.manage to create, edit, toggle, or delete rules.
  • At least one approval chain must exist before creating routing rules.

​
Steps

1

Open Approval Routing Rules

Navigate to /fw/approval-routing.
2

Create a rule

Click New Rule (visible with fw.approval_routing.manage) to open ApprovalRoutingRuleDialog.
3

Edit a rule

Click the edit icon on a rule card to reopen the dialog with existing values.
4

Toggle a rule

Click the toggle icon to enable or disable a rule without deleting it.
5

Delete a rule

Click the trash icon and confirm in the alert dialog to permanently remove a rule.

​
Key concepts

  • Routing rule — a conditional policy that maps an entity type and matching criteria to an approval chain.
  • Hit policy — SME: confirm whether rules are evaluated first-match or all-match (not determinable from code).

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/ApprovalRoutingRulesPage.tsx
  • src/platform/permissions/constants.ts