Elements of Business Rule Management: Rule Repository
Rules not only need to be created but also need to be managed. The management of business rules answers questions like these:
- When was it changed?
- Who changed it?
- Why was it changed?
- What did it look like at any point of its history?
- What state is the rule in?
- Can I checkout and test the next version of the rule?
The Decisions platform includes an integrated rule repository where business rules can be:
- Checked out
- Managed by release state (production, hotfix, development, qa)
- Reverted to prior versions
The rule repository is critical as it forms the ‘database’ of rules, in all versions. Without a comprehensive repository its impossible to track the progression of rules or look back at the what the logic/processes were at any given stage.
Want to try the Decisions Business Rule Engine? Click here.
- How financial institutions can not just keep up with Joneses but outpace them
- What is Intelligent Process Automation (IPA) and why does it matter?
- Through earthquakes, unplanned outages, and grid failures: Keep your applications running
- Low-code vs. no-code: Which one do you need?
- What Exactly is a Business Rules Engine?
- How Can You Automate Quotes with a Business Rules Engine for Insurance?
- Use Automation and Custom Business Rules to Create Intelligent Asset Management
- Three Ways to Drive Process Automation for Insurance with a Business Rules Engine
- Where and How to Use Scoring Rules to Make Better Decisions in Process Automation
- Edge Cases Don’t Fit Your Workflow? Customize with a Business Rules Engine.