The workflow diagram is the most important part of a job. It represents the process that a job will follow from start to finish. A workflow can be short, containing only a few steps for a linear task, or it can contain many steps that document a process that takes several days or months to complete and involves many participants that complete steps in the ArcGIS Workflow Manager web app, mobile apps, desktop applications, or on a server.
The connected steps in a workflow diagram are more than just a simple flowchart and contain automated logic that performs specific actions when a step is run. When a step in the workflow diagram finishes, it can either proceed to the next step and automatically start it or stay active until someone finishes it. When steps are added to the workflow canvas, they can be placed and connected using paths to form different configurations of the workflow. The workflow patterns described in the following sections can be used on their own or in combination to form large workflows.
A sequential pattern is used for linear workflows where steps are placed one after another and is the simplest form of a workflow. This pattern should be used when there is only one path for how the workflow can proceed and where steps are completed in the order in which they appear in the workflow.
A looping pattern is used for workflows that need to return to a step that has already been run based on the result of a decision point or condition in the workflow.
For example, a quality assurance person manually reviews edits that are made to a route. After the review, they are asked if the results are acceptable. If they choose yes, the workflow proceeds to the next step in the process, but if they choose no, it follows the path back to the Route Edits step. The path that returns to the Route Edits step can be configured to assign it back to the person or group that last ran the step.
A branching pattern is used to create a decision point in the workflow with multiple possible paths. It results in the workflow proceeding down a single path based on the result of a step in the workflow.
For example, when a person answers a question in the workflow, their response results in only one path becoming active. The logic for how to guide the workflow is based on the conditions configured for each path. The decision point can be manual, but it can also be automated. The Run GP Service step can also serve as a decision point in a workflow by using the return value of the step to guide the workflow.
A parallel pattern is similar to a branching pattern, except that it results in multiple steps becoming active after the previous step. This pattern is used when responsibilities of a job span across multiple parties so that they can all work simultaneously.
For example, when data is collected, an email is sent to notify stakeholders that the data is ready for review. The review is assigned to three people who each review a piece of the collection independently. The parallel workflow allows for the distribution of steps to people, groups, or automated processes simultaneously, and the people running their assigned steps may not be aware of the other active steps. Parallel workflows can also be configured using path logic so that only two of the three paths are activated depending on a condition.