The following list gives an overview of how production objects (and all of the objects they can contain) work. You should have a good understanding of this sequence of events before you start defining your own system’s production objects.
For each production object:
Run any production object prefilter against the entire input transaction.
Parse input byte stream into field objects and perform field object qualification. If errors are found, stop processing the current transaction.
Perform production object qualification.
If data does not pass qualification, stop processing the current transaction.
For each rule object, starting with first in the list and proceeding sequentially:
Process each qualification object.
If data does not pass, go to the next rule.
For each rule component object (sequentially from first in list):
Process each qualification object.
If data does not pass, go to next rule component.
Move field, literal, nested group, or datalink to a temporary work area.
For each rule component prefilter (sequentially from first in list):
Run the specified filter on the information in the temp work area.
Move result to rule object’s output transaction.
For each rule component post filter (sequentially from first in list):
Run the specified filter against the rule object’s output transaction.
For each rule post-filter (sequentially from first in list):
Run the specified filter against the rule object’s output message area.
Combine the result onto the production object’s output message area.
After the last rule object runs, run any production object post-filters against the entire transaction.
The following section provides examples of sequential processing through rule and rule component objects, examples of the path processing takes when a qualification object fails, and detailed examples and descriptions of processing through a production object and its various objects.
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
