Problem Overview
A single Knowledge Base may contain Rulebooks for multiple departments, multiple data sources, or multiple processing scenarios. Without Tags, every Run processes every Rulebook - which applies irrelevant rules, produces misleading statistics, and slows down executions unnecessarily. The alternative of maintaining a separate Knowledge Base per use case creates duplication of Domains, Members, and shared rules that must be kept in sync manually.
Solution
Tags create a targeted relationship between Runs and Rulebooks. The matching logic works as follows:
- A Run with Tag 'Finance' processes against all Rulebooks tagged 'Finance', plus all untagged Rulebooks
- A Run with no Tag processes against every Rulebook in the Knowledge Base, regardless of their Tags
- A Rulebook tagged 'HR' is skipped by any Run that carries a different Tag or no Tag at all.
Untagged Rulebooks act as universal rules - they always apply. This makes them the right place for foundational structural checks that should run for every data source, while tagged Rulebooks contain the context-specific logic.
Configuration
- Switch to Edit Version mode then navigate to the Tags tab in the Knowledge Base
- Click Add Tag, enter a Name and Description (e.g., 'Finance', 'HR', 'Month-End'), and save
- Go to the Rulebooks tab. Edit each Rulebook that should carry this Tag and assign it from the Tag dropdown in the edit form
- Go to the Runs tab. Edit the Run that should only apply tagged Rulebooks and assign the same Tag.
Tip: Build a set of core untagged Rulebooks for structural checks that apply to all data, then use Tags to layer department-specific or source-specific validation on top. This keeps shared logic in one place and avoids duplication.
Selecting a Tag in the Tags tab opens an overview panel listing all Rulebooks and Runs associated with it, along with an Unlink button to remove the Tag from a specific Rulebook or Run without deleting the Tag itself. After executions run, the Business Rule statistics panel's Rulebook filter shows only the Rulebooks that were applied for that execution - providing a clean view of exactly which rules were in scope.
If you have any further questions, please feel free to Contact Us.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article