Condition workflow steps are logic steps used for complex workflow processing, such as allowing the workflow to proceed only after each workflow step is completed. The condition workflow steps are as follows:
AND. Met only after all workflow steps leading to it reach the specified required status. Figure 3-5. AND example shows an AND condition workflow step.
OR. Met if at least one of the workflow steps leading to it reaches the required status specified for it. Figure 3-6. OR example shows an OR condition workflow step.
SYNC. Successful only if all the package lines of that package reach the status required for the workflow step immediately preceding that SYNC step.
Consider the business process illustrated in Figure 3-7. SYNC example. According to the flow chart, after QA Testing Group 1 succeeds for all package lines, SYNC succeeds, and then the next step, Migrate to Prod, becomes eligible.
FIRST LINE and LAST LINE. Only the first line to reach the condition workflow step takes the True transition. All subsequent lines take the False transition.
For LAST LINE, only the last active line to reach the condition workflow step takes the True transition. All previous lines take the False transition.
The business process illustrated in Figure 3-8. FIRST LINE and LAST LINE example could be part of a Web site maintenance life cycle. As part of this life cycle, three HTML files are processed on three respective package lines in a single package. The Web site updates are large enough to warrant shutting down the Web server during change migration.
By including a FIRST LINE step, only the first line causes the server to shut down. The server remains down while the rest of the changes are migrated to production. By including a LAST LINE workflow step, the server remains down until the last active line reaches the condition step. The last active line takes the True transition, the Web server starts up, and then the maintenance is complete.