Conditional Rules
Dynamically show, hide, enable, disable, or require fields and categories based on tag selections on the Entry form.
What Are Conditional Rules?
Conditional rules let you customize the Entry form based on what a user selects. For example, you can require a "Finish" category only when the Material is "Stainless Steel," or hide a "Welding Type" category when the Process is "CNC Machining."
Rules are evaluated in real time as users select and deselect tags. The form adapts instantly without needing to save or reload.
Open the rules editor from Settings Hub > Conditional Rules, the Entry page toolbar Rules button, or via the Command Palette (Ctrl+K).
Rule Structure
Each rule follows a four-part pattern:
When [Category] is [Tag] then [Action] on [Target]
Parts of a rule
| Part | Description |
|---|---|
| When (Category) | The trigger category that the rule watches |
| Is (Tag) | The specific tag value that activates the rule |
| Then (Action) | What happens when the condition is met: Hide, Show, Disable, Enable, or Require |
| On (Target) | The category or field affected by the action |
Rule Actions
| Action | Effect | Use Case |
|---|---|---|
| Hide | Removes the target from the Entry form entirely | Hide "Welding Type" when the process is CNC Machining |
| Show | Makes a previously hidden target visible | Show "Coating" category only when Material is Metal |
| Disable | Grays out the target so it cannot be edited | Disable "Machine" selection when the job is outsourced |
| Enable | Re-enables a previously disabled target | Enable "Operator" field only when a machine is selected |
| Require | Makes the target mandatory — entry cannot be saved without a value | Require "Finish" when Material is Stainless Steel |
Practical Examples
Example 1: Material-based finish requirement
When Material is Stainless Steel then Require on Finish
This ensures operators always specify a finish type (e.g., #4 Brushed, Mirror Polish, Bead Blast) when working with stainless steel. Without this rule, forgetting the finish can lead to costly rework.
Example 2: Hiding irrelevant categories
When Process is CNC Machining then Hide on Welding Type
CNC jobs do not involve welding, so hiding the Welding Type category keeps the form clean and prevents confusion.
Example 3: Conditional field visibility
When Priority is Rush then Require on Due Date
Rush orders must have a due date. Regular orders can optionally have one. This rule enforces the policy.
Always Required Rules
You can create a special rule that makes a category or field required regardless of any tag selection. This is useful for fields that should never be empty:
- Always require Priority — Every entry must have a priority level
- Always require Material — Every entry must specify a material
- Always require Customer Name — Every entry must have a customer assigned
In the rules editor, select ALWAYS: REQUIRED as the condition type to create an unconditional requirement.
Setting Up Rules
- Open the rules editor — From Settings Hub > Conditional Rules, the Entry page toolbar Rules button, or Ctrl+K → "Conditional Rules".
- Select the trigger category and tag — Choose the "When" and "Is" parts of the rule from the dropdowns.
- Choose the action — Select Hide, Show, Disable, Enable, or Require.
- Select the target — Choose which category or field the action applies to.
- Click Add — The rule appears in the list below.
- Save — Rules take effect immediately on the Entry form.
How Rules Are Evaluated
- Real-time — Rules fire immediately when tags are selected or deselected. No save or refresh needed.
- Multiple rules — If multiple rules affect the same target, the most restrictive action wins. For example, if one rule hides a category and another shows it, hide wins.
- Rule priority — Require > Hide > Disable > Show > Enable. More restrictive actions take precedence.
- No cascading — Rules do not chain. A rule that hides Category B does not trigger rules that watch Category B's tags.