Workflow Inputs
Overview
The Workflow Inputs node provides access to the input parameters defined for the currently active workflow.
Workflow Inputs represent the data supplied when a workflow begins execution. They are automatically generated from the workflow's configured Input Parameters and are available through the Process Data Explorer.
Workflow Inputs are read-only and can be referenced throughout the workflow to configure activities, build expressions, evaluate conditions, and pass data to other workflows.
Creating Workflow Inputs
Workflow Inputs are not created directly within the Process Data Explorer.
Instead, they are automatically generated from the Input Parameters configured for the current workflow.
To define or modify Workflow Inputs, use the Workflow Parameters dialog.
For more information, see Workflow Parameters.
Availability
The Workflow Inputs node appears automatically when the active workflow defines one or more Input Parameters.
If the workflow does not define any Input Parameters, the Workflow Inputs node is not displayed.
Each workflow maintains its own set of Workflow Inputs.
When switching between workflows in the Agent Designer, the Workflow Inputs node updates to display the Input Parameters defined for the selected workflow.
Using Workflow Inputs
Workflow Inputs can be referenced anywhere the Process Data Explorer is available.
Typical uses include:
- Configuring activity inputs.
- Building expressions.
- Evaluating conditions.
- Populating Model Data.
- Calling Sub Workflows.
- Calling external services.
Workflow Inputs are read-only within the workflow.
To modify a value during workflow execution, copy it into Model Data and perform subsequent processing on the Model Data field.
Runtime Behavior
Workflow Inputs receive their values when the workflow begins execution.
The source of those values depends on how the workflow is invoked.
- For the Main Workflow, values are supplied by the caller when the agent starts.
- For a Sub Workflow, values are supplied by the Call Sub Workflow activity.
The values remain available throughout the execution of that workflow.
Workflow Inputs and Model Data
Although both are available through the Process Data Explorer, they serve different purposes.
| Data | Purpose |
|---|---|
| Workflow Inputs | Data supplied when the workflow starts. |
| Model Data | Business data and workflow state managed during workflow execution. |
Workflow Inputs should be treated as the workflow's incoming contract.
Model Data should be used for values that need to be modified, transformed, or reused throughout the workflow.
Best Practices
- Define only the inputs required by the workflow.
- Use descriptive names and descriptions for Input Parameters.
- Treat Workflow Inputs as read-only.
- Copy values into Model Data when business processing requires updates.
- Keep Workflow Parameters focused on the workflow interface rather than internal workflow state.