User actionStable

Dynamic form

Presents a form whose specification is produced during execution, without creating a temporary `platform.form` resource.

Presented context

Dynamic form

User Journey

User response

Vue d’ensemble

Presents a form whose specification is produced during execution, without creating a temporary platform.form resource.

Exemple

An Agent identifies missing information and produces a common.form_spec limited to clarifications actually needed for the case.

Key point A user action suspends the instance until the interaction is resolved. The User Journey presents the action; the node remains the orchestration contract determining its inputs and outputs.

Parameters 6

form_specRequisform spec

common.form_spec specification produced during execution. It describes form fields without creating a persisted Form resource.

allowed_file_purposesOptionnelstring[]

Designer-controlled list of storage purposes that a file field in a dynamic form may request.

titleRequisstring

Main title presented to the participant for this action in the User Journey.

descriptionOptionnelstring

Optional supporting text shown under the title to explain what is expected from the participant.

allow_replay_from_hereOptionnelboolean

Allows a participant to restart a replay from this interaction when the process enables that capability. Disable it when repeating the action would be dangerous or misleading.

replay_boundaryOptionnelboolean

Marks this interaction as a replay point of no return to bound earlier steps that can be replayed or reused.

Outputs 1

valuesform submission

common.form_submission map containing only responses validated against the presented form snapshot.

Behavior

The specification is validated and then frozen in the user action. Submission is validated against this snapshot and only the common.form_submission map is returned.

Limits and responsibilities

The node does not re-emit the specification: map form_spec separately if a downstream node needs to know the questions.
File fields are limited to storage purposes explicitly allowed by the designer.
A dynamic specification cannot freely define its own classification policy; protections derive from field types.