Step templates are preconfigured steps that perform different types of actions when a job is run, such as opening a map, running a geoprocessing tool, asking a question, and so on. Each step template contains a default name and values for step properties, options, and styling. When a step template is added to a workflow diagram, it becomes a unique step in the workflow and its default values can be customized as necessary.
The following table lists the step templates included in ArcGIS Workflow Manager:
Step template | Description |
---|---|
Add attachments to a job. | |
Add comments to a job. | |
Choose the user or group to whom a subsequent step is assigned. | |
Remove the location defined in the job. | |
Create jobs, automatically generate dependencies, and establish parent-child relationships between jobs. | |
Define the geographic extent of a job's location. | |
Create a step with no advanced logic to serve as a placeholder for separate tasks that need to be completed outside of Workflow Manager—for example, fieldwork for GPS data collection, requests pending approval from a manager, or documentation. | |
Open one or more project items in an ArcGIS Pro project, such as maps or tasks. If a mapping item is chosen, data layers are pointed to the appropriate branch versions for the job. | |
Open web pages and web apps in an integrated Workflow Manager environment for a seamless experience. | |
Add a decision point to a workflow and define a question to determine the next step in the workflow. | |
Run geoprocessing tools, ModelBuilder models, and Python scripts that have been published as geoprocessing services. | |
Run geoprocessing tools, Python scripts, or ModelBuilder models in ArcGIS Pro. | |
Send an email notification to one or more recipients. | |
Send requests to REST endpoints to get data or post updates. | |
An optional step that can be used to indicate where a workflow diagram starts and ends. | |
Collect, view, and edit ArcGIS Survey123 surveys. | |
Allow the user running the job to create, show, and edit table records in a job's one-to-many properties table. | |
Allow the user running a job to update the job's extended properties. |