- Understanding the ID and Background Check Ruleset
- Understanding the ID and Background Check Ruleset
- You must have a solid working knowledge of Oracle SOA Suite, Oracle BPM Suite, and Oracle Business Rules before modifying any business rules. For information on these products, see:
- Oracle Fusion Middleware User's Guide for Oracle Business Rules
- Oracle Fusion Middleware Administrator's Guide for Oracle SOA and Oracle Business Process Management Suite
- Oracle Financial Services Loan Origination uses the ID and Background Check Decision Table, in the ID and Background Check Ruleset, to determine whether a background check is needed for a loan applicant. This decision table includes conditions and actions as its rows and rules as its columns. The rules test the values of the conditions and set corresponding values for the actions. The rules must account for all possible combinations of values of all conditions in the table.
- Upon submission of a loan application, the rules engine tests each condition. If a combination of condition values matches a rule, the corresponding actions are taken.
- The ID and Background Check Decision Table provides the details for each condition, its rules, and the actions to execute. Following the table is an example scenario explaining how a loan application is processed based on the given condition.
- ID and Background Check Decision Table
- An applicant applies for a Personal Loan of $500. An automatic background check is performed.
- You can modify the existing ruleset, conditions, or actions. Take caution before modifying a condition or action, it can require source code changes. Application processing fails if this ruleset is deleted.
- To modify the ruleset, conditions, or actions, see
- "Editing Rules in an Oracle Business Rules Dictionary at Run Time
- Oracle Fusion Middleware User's Guide for Oracle Business Rules.