Skip to main content
Version: Current

Process Data Drawer

Overview​

The Process Data Drawer is the central location in the designer for viewing, defining, and managing all data used by a process. It provides structured access to data models, runtime context, system metadata, shared variables, and activity outputs, enabling consistent and type-safe data flow throughout the workflow.

Designers use this drawer primarily at design time to bind inputs, build expressions, and define data structures. During execution, the workflow engine populates these data models with runtime values based on process execution and user interactions.

Process Data Drawer

Data Categories​

The Process Data Drawer organizes data into the following categories, each serving a distinct purpose:

  1. Model Data   Define and manage process-specific data structures used to store intermediate values, computed results, and business context throughout the workflow.

  2. Form Data   Access data captured from all forms associated with the process. This is a consolidated, read-only view of user inputs collected during execution.

  3. System Data   Use predefined system variables that provide execution context, such as process details, activity metadata, task information, and participant attributes.

  4. Enterprise Variables   Access shared, tenant-scoped configuration values and secrets managed centrally in the Control Room. Enterprise Variables support global and user-level scopes, as well as optional encryption.

  5. Activity Outputs   Reuse output data produced by upstream activities in the workflow. These outputs enable direct data flow between activities without explicit mapping.

How to Use the Process Data Drawer​

You can use data from any category in the drawer to:

  • Populate activity inputs
  • Build Liquid expressions
  • Configure conditions and filters
  • Drive decisions and branching logic

The designer enforces type compatibility and prevents invalid bindings, ensuring reliable and predictable workflow execution.

Best Practices​

  • Use Model Data for values that must persist across multiple activities
  • Use Activity Outputs for step-to-step data flow
  • Use Enterprise Variables for shared configuration and credentials
  • Use System Data for contextual and audit-related information
  • Avoid duplicating data across categories unless necessary

The Process Data Drawer acts as the backbone of data modeling and data flow within a workflow, enabling clean, maintainable, and scalable process design.