While you can get fairly technical when talking about Business Rules and how they can be implemented from a software and workflow perspective (technical overview coming soon with pictures!) I first want to spark a few thoughts with a few ways that business rules can be used. Do you have an idea for how they can be used? Sound off in the comments below, or connect with us on Twitter @DecisionsTweets.
BUSINESS RULES AS A PART OF A BUSINESS PROCESS
One of the most obvious and simple ways to use business rules is to incorporate them into a flow or business process. Business rules as part of a business process could be used as a way to organize approval flows based upon different data points within the flow. One example of this is a classic loan approval process.
The flow takes in loan applications and based upon a set of rules the loan applications are directed to the appropriate loan officer or other approver or decision maker. These rules could be based upon the loan amount, for example "if the loan is for more than $1000 then send to Manager X".
As we consider any process and operate within it for a period of time we usually find ways for the process to be improved. Many times a process can be improved by applying a rule for a specific situation. With a fully graphical workflow platform this change can be made quickly, and without writing any code!
BUSINESS RULES AS TRIGGERS
Business rules can also be used outside of a process as a trigger. Let's stick with the loan processing example. What if you wanted to keep the applicant informed about the status of their application? You could use the following rule in the case of applications being submitted after business hours. "If application is submitted after 5:00pm EST, then send email message X". With Decisions it is easy to send more than just emails, you could send a text message, or even initiate a voice call using a telephony service like Twilio to let the applicant know that you will get to the application as soon as you return to the office the next day.
