Action Rule Sequencing
You can sequence, or order, action rules. Sequencing action rules establishes the order in which action rules are evaluated as data is collected.
One Rule Per Sequence
When action rules are mutually exclusive you can define a single action rule for each sequence number. Each action rule can be associated with one or more actions. In this scenario, if the action rule for the first sequence number is not true, then the action rule at the next sequence number is evaluated, until an action rule at some sequence is evaluated as true. When an action rule is evaluated as true, evaluation stops and the action or actions associated with the action rule are invoked.
For example, consider the action rules associated with the Oven Temperature collection element:
- Seq 10 Action Rule: When Oven Temperature is outside the upper and lower specification limits (190 to 210 degrees F), Send an electronic mail notification and Place the job on hold.
- Seq 20 Action Rule: When Oven Temperature is outside the user-defined specification limits (195 to 205 degrees F), Display a message to the operator.
If an Oven Temperature value of 185 is collected, the action rule at sequence 10 is true and the actions that are specified for that rule -- Sending an electronic mail notification and Placing the job on hold -- are invoked. The action rule at sequence 20 is not evaluated even though the 185 value is outside the range specified.
If an Oven Temperature value of 192 is collected, the action rule at sequence 20 is the first rule to be evaluated and found to be true a warning message notifying the operator is displayed.
Multiple Rules per Sequence Number
When action rules are not mutually exclusive, you can define multiple action rules for each sequence number. In this scenario, all action rules associated with the same sequence number are evaluated. Even if the first action rule is evaluated as true, the subsequent action rules with the same sequence are evaluated.
For example, consider the action rules associated with the Defect Code collection element:
- Seq 10/1st Action Rule: When Defect Code is greater than 3, Send an electronic mail notification to the manager of the QA Department.
- Seq 10/2nd Action Rule: When Defect Code equals 9 (most severe defect), Place the job on hold and Display a message to the operator.
If a Defect Code value 4 is collected, the 1st action rule at sequence 10 is true and the action specified for that rule -- Send an electronic mail notification -- is invoked. The 2nd action rule at sequence 10 is also evaluated, but is found to be not true and no action is taken. If a Defect Code value of 9 is collected, the 1st action rule at sequence 10 is evaluated as true and the action specified for the rule -- Send an electronic mail notification -- is invoked. The 2nd action rule at sequence 10 is also evaluated as true and the actions specified for the rule -- Place the job on hold and Display a message to the operator -- are invoked.
See Also
Defining Collection Element Actions
Defining Collection Element Alert Actions
Defining Collection Plan Element Actions
Defining Collection Plan Element Alert Actions
