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
- Versioned
- Managed by release state (production, hotfix, development, qa)
- Reverted to prior versions
- etc
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.
By Carl Hewitt
By Carl Hewitt
In addition to being the founder of Decisions and other prior workflow ventures, Carl has been an innovator in object oriented programming for business since the 90′s.
Rumor has it he was raised by marketeers.
Latest Articles
- What Does No-Code Software Really Mean for End Users?
- Is Your Company’s Workflow Software Not Cutting It? Here’s What You Need to Know
- The Advantages of Using a Rules Engine for Managing Insurance Forms, Rate and Commission Calculations
- 6 Tips for Mastering Data Management
- Building Brownfield Applications
- Understanding External Truth Tables: Applications for Your Business
- How Manufacturers Streamline Business Processes with Workflow Automation
- The Benefits of Using an External UI
- Data Mapping Tools to Consider When Selecting a Decision Management System
- What Multi-Tenancy Environments Can Do for Your Business
