Separation without the anxiety
In the past there was the program and the data; now we have the application program, the business rules, and the data. This separation of rules allows the business analyst to make changes to the application logic without having to turn to the developers for help. It enables applications to change dynamically - without the delays and frustrations of waiting for release cycles.
Chrome River provides a powerful world-class rules engine as a core part of our application. Every time a user saves an item, it is checked for policy compliance against a rules set. Every time an item is submitted, the routing is determined by the rules engine. Organizations can change their rules, add new policies and change approval chains at any time.
As flexible as yoga
The rules engine has access to the application's core objects. The significance of this is that your business has the flexibility to create virtually any kind of business rule; you are not dependent on a fixed set of pre-built rule types. For example, you might have a compliance rule that prohibits future dated transactions. Then you decide to modify this rule to allow for certain expenses that have future dates (but not other types of expenses). You might again change the rule to say that this expense exception is only permitted in your North American offices or for individuals with certain titles or...Regardless of how your policies evolve, the Chrome River Rules Engine can evolve with you.