E Order of Precedence Rules for Close Manager
Note:
This feature is available only in 11.1.2.4.100 (patch 20307212). For information about new features and updating to release 11.1.2.4.100, see My Oracle Support https://support.oracle.comExecuting a rule might prevent a rule established later from being invoked. For example, if a customer assigns an auto submit rule to a task, and the auto submit succeeds, then any rule tied to the Submit function (such as prevent task submission) would never be invoked.
Table E-1 Order of Precedence Rules
Rules | Rule Type | Runs When | Precedence Notes |
---|---|---|---|
Auto Approve Task |
Template Rule Schedule Rule Task type Rule Task Rule |
Task status changes to Open with Approver. |
If any rule is successful, then Auto Approval occurs. |
Auto Submit Task |
Template Rule Schedule Rule Task type Rule Task Rule |
Task status changes from Pending to Open with Assignee. |
If any rule is successful, then Auto Submit occurs. |
Prevent Task Approval |
Template Rule Schedule Rule Task Type Rule Task Rule |
Approver clicks Approve. |
If any rule is successful, then approval fails. |
Prevent Task Submission |
Template Rule Schedule Rule Task Type Rule Task Rule |
Assignee clicks Submit. |
Rule triggered when the assignee clicks Submit. Can be evaluated in any order. If any rule succeeds, then the Submit function is prevented. |