Business rules come in many styles. FlowWright has 2 methods of defining and using them within a process. To keep it simple one is internal to the process and the other is external to the process.
Business rules can be designed graphically using decision steps strung together within a process. Once a process executes, its very easy to view the execution, and the decisions made by the process using rules. This is considered internal to the process, where the business rules live within the process itself. And the rules are also graphically designed using workflow steps and connections within the workflow process. In the above graphic, a decision is evaluated and made based on a Purchase order amount, based on a true/false outcome the Purchase order is routed to Manager 1 or to Manager 2 for approval.
If you have complex rules and want to share these rules with many processes, then you can use decision tables in FlowWright. Decision tables let you define any number of inputs and outputs; and any number of expressions. These decision tables can be used within any process using the "Evaluate decision table" step. Based on the input values fed to the decision table, it is able to provide the outputs based on the defined rules. Decision tables are external to the process, but all the rules are in one place to maintain and share. Here's an example of a decision table:
Graphical rules can get messy with there are many of them, for example, rules around getting a mortgage can be very complex. In order to get approved for a mortgage, the inputs would include mortgage amount, interest rate, # of years that determines if the mortgage is approved or not. Decision tables are perfect for managing complex rules. Decision table also lets you define them and test them within the same environment. Decision rules also provide a step, so that these rules can be evaluated within a process.
FlowWright provides a high performance .net rules engine, use any expression that is simple to complex. All expressions use c# format, if you can type the expression in Microsoft Visual Studio, then FlowWright is able to evaluate and produce the result. On top of using rules within processes, rules can be also tested from out side processes. Sometimes its time consuming to test rules within a process, so use the Rules testing tools within FlowWright. Click the "Status" menu and select "Tools" sub-menu.
FlowWright's .net rules engine is designed for performance, even with complex rules, performance is just amazing. This is where software writes software on demand to evaluate complex rules, all of this done in memory with very high speeds. Performance is always a key in decision making, faster you can make decisions, computations, the more you can process. FlowWright's engines are also optimized to perform computations, where the robotic processes are able to optimize them selves based on how complex the rules are. This comes in handy when evaluation complex rules within decision tables. Most graphical rules are single expression level rules, but in the case of decision tables, the decision table could have many complex rules with many inputs. Specially with decision tables, performance matters.
Decision engine software has many meanings, but when it comes to workflow processes, process tend to make decisions based on process data or expressions. When it comes to Decision engine software, FlowWright includes all the capabilities in one package. There is no additional software to purchase or add, its all built into the core FlowWright software. Decision engines are also separate from the workflow engines, where as workflow engines use robotic workers to process the data, but the decision engine use in-memory computations and compilations to evaluate complex expressions. Data driven processes depend on expression evaluation to make decisions. In most cases, decision engines have to evaluate expressions at many levels of the process. With any process, control flow and data flow is totally handled by the expression/decision defined within the process.
With Robotic process automation in the front lines of workflow-bpm, most decision making and rules processing are performed by robotic workers. For example, a robotic process that collects data for sales figures each day might make some decisions to determine if its end of the month and compute end of the month sales reports also for distribution. There are many ways to use decisions, but decisions are a key to any workflow process. Just as you would make decision in real life, you have handed over the decision making process to a robotic worker to process, remember they can make decisions a lot faster than you can.
Most business rules management software doesn't provide many choices to process business rules, but FlowWright lets you decide how you want to implement business rules, the graphical way or the decision table way. Do it your way!
When it comes to Rules Engine Software, there are many choices on the market. But don't forget what you really need for processing business rules, Automated workflow processes. Let digital processes make decisions based on rules that you have defined, so that you can focus on your business.