Importance of business rules management in interoperability
What is the value of enabling users to manage business rules in service interoperability processes? One of the aspects to consider while making systems interoperable is how to manage the change in business rules in a way that doesn't affect the quality of the process. Traditional interoperability frameworks encourage embedding business rules into code only accessible to developers. Although this approach has its advantages, it reduces the ability of the enterprise to react to sudden changes in processes, which many times are necessary to keep a competitive advantage.
So the question becomes how to abstract decision management from processes in a way that allows for maximum flexibility for change while maintaining a high degree of security, scalability, usability, and all the -ities.
If an enterprise has processes that are subject to frequent changes of business rules, and these processes are core to the services and the product it sells, then there should be a consideration on using Business Rules engines that will allow for the decentralization of the management of such rules without affecting the already built processes. These engines usually support user management capabilities by design, which allows the creations of users, groups, roles. Business processes can invoke business rule engines on the fly without needing to be recompiled or go through the release lifecycle whatsoever, accelerating the reaction time to changes. Business users have controlled access to rules that drive these processes and this access is no less secure than embedding the rules into code, however with the advantage that rules can be modified, monitored, and approved for production within moments.
Are your interoperability flows taking advantage of business rule engines?
Data Governance Professional
4 年I fantastic read. Very interesting indeed.