Business Rules Engine decisioning within automation
Key Takeaway
Build decision logic once in Business Rules Engine. Call it from Salesforce Flow and Omniscripts through action elements, so business users can change the rules without editing the workflows that call them.
Business Rules Engine holds decision logic as decision matrices, decision tables, and expression sets. A workflow, such as a flow or an Omniscript, collects the inputs and sends them to Business Rules Engine. Business Rules Engine returns the outcome. The workflow then uses the outcome or shows it to the user. In Agentforce Financial Services lending, Business Rules Engine drives decisions such as eligibility, pricing, disclosures and consents, required documents, and risk categories.
How Business Rules Engine fits into a process
Business Rules Engine has three core components: decision matrices, decision tables, and expression sets. Building the rules is only the first step. You then deploy the rules to users by calling them from a workflow tool inside a real business process.
Every integration follows the same loop:
- The workflow collects the inputs and passes them to Business Rules Engine.
- Business Rules Engine runs the rules and returns the outcome.
- The workflow displays the outputs to the end user.
Think of the workflow as the conversation with the user, and Business Rules Engine as the calculator the workflow consults.