Flow Studio
Forms Capability Overview
Presenting Atlas Forms to users as workflow steps — the UserFormNode, HIL suspension, form rendering in the WorkDesk inbox, and reading submitted data downstream.
What the Forms Capability Provides
The Forms capability integrates the Atlas Forms platform with workflow execution. When a workflow reaches a UserFormNode:
- Execution suspends (HIL mechanism)
- A task is created in the assigned actor's WorkDesk inbox
- The inbox renders the Atlas Form, pre-populated with workflow data
- The user fills and submits the form
- The submitted data flows back into the workflow as the node's output
- Execution resumes from the appropriate port
Forms vs. Approval HIL
| Feature | Forms Capability | Approval HIL |
|---|---|---|
| UI | Full Atlas Form (any fields) | Simple Approve/Reject decision |
| Data input | Many fields, structured data | Optional comment only |
| Use case | Data collection, registration, surveys | Binary decisions, escalations |
| Output | All form field values | decision + comment |
Data Flow
[UserFormNode]
│ Suspends; creates inbox task
│ Pre-populates form with inputMap values
│
User submits form
│ POST /api/executions/{id}/resume
│ Body: { responseData: { fieldKey: value, ... } }
│
[UserFormNode resumes]
│ responseData merged into nodeOutputs[nodeId]
│ Routes to submitPort
▼
[DownstreamNode] reads $output.formNode.fieldKey
Prerequisites: Read Guide21_HILOverview and Guide22_HILSuspensionResume before this guide to understand the HIL mechanism that Forms is built on.