This section provides a few more technical details about workflow.
In CGI Advantage, approval assignments can be routed to an approval role or directly to a user. Each approval level can be assigned to only one role user or one user. Each approval level can have a maximum of five OR conditions, and each OR condition can have a maximum of five AND conditions.
Condition ordering is important. After an AND condition evaluates as false, no more AND conditions are checked because the whole sequence will evaluate as false. Likewise, after an OR condition evaluates as true, no more OR conditions are checked because the whole sequence will evaluate as true.
AND conditions may not contain fields from more than one component unless one of the component types is the transaction Header. For example, F1 is a field on a transaction Header. F2, F3, and F4 are fields on the Vendor tab, and F5 and F6 are fields on the Commodity tab. “F1 is ‘xx’ AND F2 is less than 100” represents a valid AND condition. “F2 is less than 100 AND F6 is not ‘yy’” does not represent a valid condition since F2 and F6 belong to different components and neither of the two tabs is the transaction Header.
Each approval level is assigned an ordinal number that specifies when the approval level assignment should be displayed in the assignee’s worklist. Approval levels with a lower ordinal number will be assigned earlier than levels with higher ordinal numbers. Approval levels with the same ordinal number will appear in the assignee's worklist at the same time.
Each approval level assignment must include a comment. This comment describes the purpose for this approval level and appears on the worklist entry for the approval assignment.
Each approval level assignment can also include the option of sending an e-mail message to the assignee, whether the assignee is a user or role. The e-mail message is sent to the e-mail address for the single user assignee or to all members belonging to the assigned approval role.
Users are assigned approval level authorities based on the Access Control settings for their security roles and the resource group of the transaction instance being approved. Assignees must have the appropriate approval level authority or the approval assignment should not be made. For further information on Access Control, please refer to the "Access Control" topic in the CGI Advantage Security Administration User Guide.
Same-transaction tab fields in AND conditions are evaluated together. For example, a transaction with a Commodity tab can have multiple lines. The component contains two fields of interest - Commodity Code and Unit Cost. A condition of Commodity Code equals PC AND Unit Cost is greater than 10,000.00 can be designed. Because these two fields are contained on the same tab and in an AND condition, processing looks for the first commodity line that meets this AND condition. Even if the next line does not satisfy the condition, the rule will evaluate to true. Though approval conditions may be satisfied at the line level, they are required at the transaction level.