Overview
This section gives a brief overview of Rules Engine as a tool and its relevant scenarios.
The business rules language is procedural or imperative in style. You can assume it as a machine state consisting of a control part representing the instructions to be executed and a data part consisting of the structure being manipulated by the instructions. Rules Engine has been designed for non-technical users.
For example, you can use Rules Engine in the CR Sales Opportunity module, where it can be used to determine whether an opportunity is appropriate for a customer or not and if so, what value or probability can be placed on that opportunity for the customer.
Another instance where a rule can be used is in Process Workflow (PW). Here, the rule determines the correct status of a PW activity or a process.
Previously, a routine was used. This routine was coded to make a complex calculation or decision.
The Rule Designer is designed for business users to write a rule specifying the logic required to make the correct decision or to find the right score.
This guide describes the process of business rules language and its usage through rule composition.
In this topic