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 Decision Table page opens the Decision Table Editor in creation mode at /fw/decision-tables/new. It shares the same component (DecisionTableEditorPage) used when editing an existing table; the route parameter id is absent (treated as new).

​
Overview

Creating a new decision table navigates to /fw/decision-tables/new. The editor presents a configuration form (name, hit policy, description, tags) and a rule grid for defining input conditions and output values. On first save, the record is created and the browser is redirected to the edit URL (/fw/decision-tables/:id/edit) so subsequent saves update the existing record.

​
Who it’s for

Requires fw.decision_tables.manage permission (FW_PERMISSIONS.DECISION_TABLES_MANAGE). Users without this permission see the form fields and grid in read-only mode; save and publish actions are hidden.

​
Before you start

  • You must have the fw.decision_tables.manage permission assigned to your role.
  • Choose a descriptive name (required; the editor validates that it is non-empty before saving).
  • Select the hit policy that matches your rule evaluation strategy before adding rows, as it affects how multiple matching rules are handled.

​
Steps

  1. Navigate to /fw/decision-tables and select “New Table,” or navigate directly to /fw/decision-tables/new.
  2. Enter a Name (required) and optional Description and Tags in the Configuration card.
  3. Select a Hit Policy from the dropdown.
  4. Add input and output columns to the rule grid using the DecisionTableGrid controls.
  5. Define rule rows by filling in condition values for each input column and result values for each output column.
  6. Select Save. On success the browser redirects to /fw/decision-tables/:id/edit and the table status is draft.
  7. To make the table available for use, select Publish and optionally add a change summary in the confirmation dialog.

​
Key concepts

  • Hit policy — Determines which rules are evaluated and how results are combined when multiple rows match. Options are visible in HIT_POLICY_LABELS in src/cores/fw/types/decision-tables.
  • Input/output columns — Structured column definitions parsed from input_columns and output_columns stored as JSON in the database.
  • Draft vs. published — A table starts in draft status. Only published tables are available for reference by automations and workflows.
  • Version — Each publish action increments the version number displayed in the editor header.

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/DecisionTableEditorPage.tsx
  • src/cores/fw/hooks/useDecisionTable.ts
  • src/cores/fw/hooks/useDecisionTableMutation.ts
  • src/cores/fw/types/decision-tables.ts