Workflow Inputs

Workflows can take inputs from the application that hosts the workflow. There are two types of inputs:

Do not confuse workflow inputs with user inputs. User inputs are gathered from the user by the running workflow using forms or prompts. Workflow inputs are provided to the workflow by the application that runs the workflow.

Configure a Host Application to Pass Inputs to a Workflow

Some host applications support different methods of hosting workflows. The way you configure the inputs depends on how the workflow is hosted and what type of inputs the workflow takes:

The table below lists the most common methods of hosting workflows and the types of inputs they support.

Common methods of hosting workflows that take inputs

Host Application

Hosting Method

Supports
Design-Time Inputs

Supports
Run-Time Inputs

Hosting Method
Run-Time Capability

Geocortex Web

I Want To menu

 

Toolbar

 

Feature Actions menu

Passes the currently selected feature.

Context menu

Passes the map location (point geometry) clicked by the user.

Geocortex Mobile

I Want To menu

 

Feature Actions menu

Passes the currently selected feature.

Geocortex Viewer for HTML5 *

I Want To menu

 

Toolbar

 

Feature Actions menu

Passes the currently selected feature via the {{context}} token.

Map Context menu

Passes the map location (point geometry) clicked by the user via the {{context}} token.

Hyperlink

Passes different types of data via replacement tokens, especially field tokens and object tokens.

Web AppBuilder for ArcGIS

Widget

 

*  The Geocortex Viewer for HTML5 has additional context menus that can be used to run workflows. For information, see Types of Context Menu in the Geocortex Viewer for HTML5 administrator help.

See also...

Host and Run Workflows in Geocortex Web

Host and Run Workflows in Geocortex Mobile

Host and Run Workflows in the Geocortex Viewer for HTML5

Host Workflows in Web AppBuilder for ArcGIS

Use a Workflow's Inputs in the Workflow

To use a workflow's inputs in the workflow:

  1. Add a Get Workflow Inputs activity to the workflow to get the inputs that are passed into the workflow.

    You will use the activity's inputs output—$getWorkflowInputs1.inputs—to access the inputs. The inputs output has a property for each input that was passed into the workflow.

  2. Access the inputs.

    The name that you use to access an input depends on the type of input:

© 2019 Latitude Geographics Group Ltd. All Rights Reserved.

Documentation Version 5.11