Organize Business Rules into Separate Rulebooks by Purpose

Problem Overview

A Rulebook with fifty Business Rules is hard to navigate, harder to explain to non-technical stakeholders, and nearly impossible to hand over to a new team member without a lengthy walkthrough. When something breaks, you have to dig through all fifty rules to find the relevant one. When an audit requires you to show which rules apply to HR data versus financial data, there is no clean answer.

Rather than building one large Rulebook for everything, split your Business Rules into focused Rulebooks by department, data subject, or validation purpose. This makes maintenance faster, statistics cleaner, and the overall Knowledge Base easier to navigate.

Solution

Splitting rules into purpose-driven Rulebooks costs nothing in execution performance - HEDDA.IO processes all applicable Rulebooks during a Run regardless - but it pays dividends in maintainability and reporting clarity.

There is no single correct way to divide Rulebooks, but the following patterns work well in practice:

• By department or data domain: 'HR - Employee Validation', 'Finance - Invoice Cleansing', 'Logistics - Address Standardization'. Each department owns and maintains its own Rulebook.
• By processing stage: 'Stage 1 - Structural Checks', 'Stage 2 - Reference Enrichment', 'Stage 3 - Business Logic Validation'. Rules that must run before others go in earlier-stage Rulebooks.
• By criticality: 'Critical - Blocking Rules', 'Advisory - Warning Rules'. Separating rules that invalidate records from rules that only flag potential issues makes it easier to interpret results.

Configuration

1. Open the Knowledge Base and switch to Edit Version mode
2. Navigate to the Rulebooks tab
3. Click Add Rulebook at the top of the Browsing Panel.
4. Enter a descriptive Name and a clear Description explaining what this Rulebook is responsible for.
5. Click Save. HEDDA.IO automatically adds a default first Business Rule to the canvas.
6. Begin building out the rule sequence on the canvas by editing the default rule and adding subsequent ones.

When you save a new Rulebook, the Edit Business Rule drawer opens immediately for the default rule. Use this moment to name and configure the first rule rather than closing the drawer and reopening it.

Connecting Rules Within a Rulebook

Inside a Rulebook, Business Rules are connected on a canvas. Each rule has two exit handles: a green checkmark (rule was valid) and an orange warning (rule was invalid). Clicking one of these handles on an existing rule and dragging to a new position creates a new rule connected under that outcome.

This means you can build branching flows: if Rule A passes, check Rule B; if Rule A fails, check Rule C instead. The Advanced Flow Editor in the top-right corner of the canvas gives you full control over connections, including cycles and complex graphs, and provides a Format button to auto-arrange nodes using the Network Simplex Algorithm.

Each Rulebook has exactly one root Business Rule - the starting node. All other rules must be connected back to the flow. If a node is disconnected (an orphan), HEDDA.IO will flag it in the Advanced Flow Editor with a red indicator.

Outcome

After executions have run, open any Execution in the Run Info Panel and navigate to the Business Rules tab. The Rulebook dropdown at the top of that view lets you filter statistics by individual Rulebook. This is where the organizational investment pays off - instead of scrolling through all rules, you can instantly see the pass/fail profile of one specific department's rules in isolation.

If you have any further questions, please feel free to Contact Us.

You can also refer to the HEDDA.IO End User Documentation.