Skip to main content
Version: Current

Process Data Explorer

Overview​

The Process Data Explorer is the central location for viewing and managing all data available to the currently active workflow.

It provides structured access to workflow inputs, process data, form data, system metadata, enterprise variables, activity outputs, and other contextual data, enabling a consistent and type-safe data binding experience throughout the Agent Designer.

Open the Process Data Explorer from More (⋮) → Process Data in the Designer Command Bar.

Using the Process Data Explorer​

The Process Data Explorer is primarily used at design time when configuring workflows.

You can drag data directly from the explorer into supported designer elements, including:

  • Workflow activity properties
  • Workflow parameter mappings
  • Form components
  • Email templates
  • Expressions
  • Conditions
  • Filters

The same Process Data hierarchy is available throughout the Agent Designer wherever data binding is supported, providing a consistent design experience.

tip

Wherever a designer supports data binding, the same Process Data hierarchy is available, allowing you to browse and bind workflow data in a familiar way.

Available Data​

The Process Data Explorer displays data that is available to the currently active workflow.

Some nodes are always available, while others appear only when the corresponding resources or execution context exist.

Always Available​

The following nodes are always available.

NodeDescription
Model DataDefine and manage workflow-specific data structures used during execution.
System DataAccess runtime information about the current workflow, activity, task, and execution environment.
Enterprise VariablesAccess tenant-wide configuration values and shared variables managed in AI Command Center.

Contextual Nodes​

The following nodes appear only when applicable.

NodeAvailable When
Workflow InputsThe active workflow defines one or more Input Parameters.
Form DataThe active workflow contains one or more forms.
Activity OutputsOne or more upstream activities expose output values.
Error HandlerThe current activity is configured inside a Custom Error Handler.

Workflow Inputs​

The Workflow Inputs node contains all Input Parameters defined for the currently active workflow.

These values represent the data supplied when the workflow begins execution and can be referenced throughout the workflow.

Each workflow maintains its own Workflow Inputs.

For more information, see Workflow Inputs.

Model Data​

The Model Data node contains workflow-specific variables and business data used during execution.

Model Data is typically used to store:

  • Intermediate results
  • Business objects
  • Collections
  • Computed values
  • State shared between activities

For more information, see Model Data.

Form Data​

The Form Data node displays data captured by forms belonging to the active workflow.

This node becomes available only when the workflow contains one or more forms.

Form Data can be used throughout the workflow after values have been collected from users.

For more information, see Form Data.

System Data​

The System Data node provides access to runtime metadata supplied by the platform.

Typical information includes:

  • Workflow information
  • Activity information
  • Task details
  • User context
  • Execution metadata

For more information, see System Data.

Enterprise Variables​

The Enterprise Variables node provides access to shared values managed centrally in AI Command Center.

Enterprise Variables are commonly used for:

  • Application settings
  • Configuration values
  • Shared constants
  • Secrets

For more information, see Enterprise Variables.

Activity Outputs​

The Activity Outputs node displays output values produced by previously executed activities.

These outputs can be bound directly to downstream activities without requiring intermediate variables.

The node automatically updates as activities are added to the workflow.

For more information, see Activity Outputs.

Error Handler​

The Error Handler node becomes available when configuring activities within a Custom Error Handler.

It exposes information about the error that caused the exception, allowing workflows to inspect and respond to failures.

Typical information includes:

  • Source activity
  • Exception details
  • Error context
  • Activity inputs

For more information, see Error Handler Data.

Best Practices​

  • Use Workflow Inputs to access data supplied when a workflow starts.
  • Use Model Data to store information required throughout workflow execution.
  • Use Activity Outputs for short-lived data produced by upstream activities.
  • Use Enterprise Variables for shared configuration values.
  • Use System Data to access runtime metadata.
  • Use Form Data for values captured from user interactions.
  • Use Error Handler data only within Custom Error Handlers.
  • Workflow Parameters
  • Model Data
  • Form Data
  • System Data
  • Enterprise Variables
  • Activity Outputs
  • Custom Error Handlers