Custom form
Presents a reusable platform Form chosen at design time and validates responses against its persisted schema.
Presented context
Custom form
User Journey
User response
Vue d’ensemble
Presents a reusable platform Form chosen at design time and validates responses against its persisted schema.
Exemple
Reuse the same bank-details or supplementary-information Form in several processes.
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 5
form_id
Identifier of the reusable
platform.form whose schema is known at design time.title
Main title presented to the participant for this action in the User Journey.
description
Optional supporting text shown under the title to explain what is expected from the participant.
allow_replay_from_here
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_boundary
Marks this interaction as a replay point of no return to bound earlier steps that can be replayed or reused.
Outputs 2
form_id
Identifier of the persisted Form actually presented during this interaction.
values
Values submitted and validated against the schema of the presented form.
Behavior
The node loads the selected platform.form, presents its schema, and produces validated values. Dynamic outputs known from the Form may be exposed by the editor.
Limits and responsibilities
- The schema belongs to a persisted Form resource; however, a saved Process revision retains the Form revision it pinned, so moving Form Working does not retroactively rewrite existing snapshots.
- Use
dynamic_formwhen the questions themselves are known only at runtime.