Problem
Business rules often start simple, but quickly become hard to manage once multiple conditions, exceptions, and dependencies are involved. In the budgeting software at UNEOS, for example, transactions had to be assigned to the correct budget based on different attributes such as amount, account, text, or other transaction data.
The challenge was to give users enough flexibility to describe complex logic without forcing them to think like developers or work with opaque technical rule syntax. This is a common problem far beyond budgeting, wherever systems need to route, classify, filter, or automate based on a set of conditions.
Solution
The Conditions Editor translates complex rule logic into a visual, no-code interface built around simple conditions and nested groups. Users can combine AND/OR logic freely, making advanced rules possible while keeping the structure readable and easy to adjust. The pattern scales from simple filters to complex automation and classification workflows.
Interaction
The interaction model follows a simple, sentence-like structure: Variable → Operator → Value, making each condition easy to understand at a glance. All / Any controls translate AND/OR logic into familiar language, while nested groups reuse the exact same pattern, so complexity grows without introducing new interaction concepts. This makes even advanced rules feel predictable and surprisingly lightweight to build.