- Primeros pasos
- Actividades
- Diseñar flujos de trabajo de larga duración
- Comenzar trabajo y obtener referencia
- Esperar trabajo y continuar
- Agregar elemento de la cola y obtener referencia
- Esperar elemento de la cola y continuar
- Esperar la tarea de formulario y continuar
- Reanudar después del retraso
- Asignar tareas
- Crear Tarea Externa
- Esperar la Tarea Externa y continuar
- Complete Task
- Forward Task
- Get Form Tasks
- Get Task Data
- Obtener tareas de la aplicación
- Agregar comentario de tarea
- Actualizar etiquetas de la tarea
- Crear tarea de aplicación
- Esperar tarea de aplicación y reanudar
- Configurar el temporizador de tareas
- Acciones
- Autopilot en Action Center: vista previa
- Procesos
- Notificaciones
- Auditoría
Quick Form tasks, inline human-in-the-loop forms for Maestro, Case Management, Flow, and Agents, with no separate app to build.
Quick Form tasks let you define a human-in-the-loop (HITL) review step directly inside your process. No app to build, no separate deployment, no additional cost or units. The form schema lives in the process itself, and the form appears in Action Center for the assigned reviewer when the task runs.
Quick Form tasks work across all UiPath process surfaces: Maestro BPMN, Case Management, Flow, and Agents.
Form editor
The form schema is opened differently depending on where you build it:
- In Maestro BPMN and Case Management, the schema is a file in the process. A Customize schema button in the task node's properties panel opens it in a dedicated schema editor within the canvas workspace. Once a schema exists, the button reads Edit schema.
- In Flow, the schema editor is inline in the node's properties panel, with no file and no separate launch step.
Both editors offer two modes:
- Live editor: visual drag-and-drop form builder with an immediate layout preview.
- JSON editor: direct schema editing for advanced use cases.
Campos
Fields define what the reviewer sees and what data flows in and out of the task. Each field has:
-
Label: the display name shown to the reviewer.
-
Type: controls validation and input rendering. Supported types, grouped by kind:
- Text and boolean: String, Boolean
- Numeric: Integer, Decimal
- Date and time: Date, Date and time
- Choice: Single select, Multi-select
- Structural: Array, File
Single select and Multi-select need a configured list of choices, each with a stable id, the value that gets submitted, and the label shown to the reviewer.
-
Direction: determines how data flows between the process and the reviewer (see Field directions).
-
Binding: for Input and InOut fields, maps the field to a workflow variable or expression for pre-population. Accepts any workflow expression, not just variable references.
Multi-column layout
Fields can be arranged side by side in a multi-column grid. Each row supports up to three columns, and field order within the grid can be changed by dragging fields into place.
Conditional rules
Fields support conditional display and validation rules. A field can be shown or hidden, or made required, based on the value of another field in the same form. The field's settings panel holds these rule settings.
Resultados
Each Quick Form task has one or more outcomes: labeled actions the reviewer can take, such as Approve, Reject, or Submit. Each outcome maps to a sequence flow in the process. After the reviewer selects an outcome and submits, the process routes to the corresponding branch.
Field directions
| Dirección | Pre-populated | Editable by reviewer | Written back to process |
|---|---|---|---|
| Entrada | Yes, from a bound workflow variable or expression | No, read-only | No |
| Salida | No (starts empty) | Sí | Sí |
| EntradaSalida | Yes, from a bound variable or expression | Sí | Yes, final value replaces the original |
Input surfaces context for the reviewer. Output collects a decision or value the reviewer provides. InOut shows a pre-filled value that the reviewer can correct or confirm.
Accessing output values
After the reviewer submits the task, output and InOut field values are available downstream at:
vars.<nodeId>.output.<fieldName>
vars.<nodeId>.output.<fieldName>
For example, if the node ID is quickForm1 and the field ID is approvalNote, the value is at vars.quickForm1.output.approvalNote.
Inline debug
Quick Form tasks support inline debug. You can test the full task experience directly from the canvas during a debug session, without deploying the process or creating an Action Center task.
When a debug session reaches a Quick Form node, the task form opens inline in the properties panel, supporting:
- Filling in output and InOut fields as the reviewer would.
- Selecting an outcome to continue the process on the corresponding branch.
- Output values flowing into downstream variables in real time in the variables panel.
No Action Center task is created during inline debug. The submission is simulated locally, so you can validate field bindings, outcome routing, and variable mappings before publishing.
Inline debug in Agents
When an Agent escalates to a Quick Form task during debug, the same inline form appears. You can respond to the escalation and observe how the agent continues after the human step completes.
No app required
Quick Form tasks do not require an Action App, UiPath App Studio, or any additional deployment step. The schema is packaged and versioned with the process, at no additional licensing cost and with no dependency on the Apps service.
If you need a fully custom interface, such as a branded layout, complex UI logic, or a form shared across multiple processes, use an Action App instead.