- Understanding the Approval Flow Control Ruleset
- Understanding the Approval Flow Control Ruleset
- You must have a solid working knowledge of Oracle SOA Suite, Oracle BPM Suite, and Oracle Business Rules before modifying the EFM business Approval Flow Control Ruleset. 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 Suite and Oracle Business Process Management Suite
- Oracle eForms Management uses the EFM Approval Flow Decision Table, in the Approval Flow Control Ruleset, to determine the approval percentage, alert notification, and approval reviews for each submitted eForm. This decision table includes conditions and actions as its rows and rule buckets as its columns. The rule buckets test the values of the conditions and set corresponding values for the actions. The rule buckets must account for all possible combinations of values of all conditions in the table. A value of otherwise means "all values not listed." A dash means "this value doesn't matter." Globals are variables used in the decision table to set pre-defined values for certain conditions.
- What are the EFM Globals?
- Globals are global variables used in the Approval Flow Control Ruleset conditions. These global variables enable you to modify the values to fit your organization.
- EFM ships with two globals. The following EFM Globals table identifies each global, its use in the conditions, and the default values.
- EFM Globals
- You can modify the values assigned to each global. You should not add or delete globals because this has a negative effect on the processing of eForm approval requests. To edit globals, see "How to View Globals in an Oracle Business Rules Dictionary at Run Time," in
- Oracle Fusion Middleware User's Guide for Oracle Business Rules
- What are the Decision Table Conditions, Actions, and Buckets?
- The EFM Approval Flow Decision Table ships with four conditions, four actions, and nine rule buckets, R1 through R9. Upon submission of an eForm approval request, the rules engine tests each condition. If a combination of condition values matches a rule bucket, the corresponding actions are taken. The EFM Approval Flow Decision Table provides the details for
- each condition, its rule buckets, and the actions to execute. Following the table is an example scenario explaining how an eForm approval request is processed based on a given condition and action.
- EFM Approval Flow Decision Table
- A user submits an IT Change Request Form eForm approval request. The approvers approve the request within one day, so no alert notifications are sent, and the request is automatically closed.
- You can modify the existing ruleset, condition, or actions. Take caution before modifying a condition or action, it can require source code changes. eForm approval request processing fails if the Approval Flow Control Ruleset is deleted. The
- drop-down lists and globals must be modified, if required, prior to modifying the ruleset, conditions, or actions.
- To modify the ruleset, conditions, or actions, see "Editing Rules in an Oracle Business Rules Dictionary at Run Time," in
- Oracle Fusion Middleware User's Guide for Oracle Business Rules