Workflow Design Basics

Workflows are configured collections of subprocesses, activities, reference data, and functional resources that are used to complete the defined process from start to finish.

Under the Workflow model, using the Workflow Editor, you configure all aspects of a workflow's processes and specifications that are used during production.

Workflow logic may be internal and invisible to operators; however, most of the logic requires interaction through a user interface. Workflows that are visible to operators are called tasks, and when they are running, they can be viewed in the Task List or Task Management display, depending upon the permissions available to a user.

A workflow may also be composed of subprocesses. These subprocesses may only be internal and invisible to operators; however, they must be valid (that is, contain no errors) and enabled (active) for a workflow to run. But, like workflow, they may require user interaction. If they are visible to operators, they are called task steps. Task steps can include their own documentation and forms, which appears to users in the Task List display.

Tasks and task steps can be routed to different workstations based on equipment or user requirements. For example, a task might contain an Insert Flange task step. When executed, this task step is routed to the console of the flange insertion worker. This task step presents him with a diagram of the flange install and a form to submit when he is finished. Sequences of task steps can be used to guide users through complex operations. Operators can input data into forms, that can then be used by the rest of the workflow or stored for reporting purposes.