Class FormStepData
- All Implemented Interfaces:
StepData
It suspends the workflow exactly like a HaltData — same
pause/resume, same snapshot, same "waits for input" story — but it carries the
form to show while it waits: a semantic-ui UiNode. The run view renders
that node, and the fields the user fills become the params the workflow resumes
with.
This is why it lives in its own module rather than in the engine. A
UiNode is a semantic-ui type, and mc-workflow is deliberately
free of any UI dependency. Here — a module that already depends on both — the
step can hold the form directly. The engine never sees it: to the engine this
is just a halt (it extends HaltData, so pendingHalt and the
whole resume path treat it as one), and only the admin, which knows
semantic-ui, reads form and paints it.
Because UiNode carries its own Jackson type info, the form
round-trips through the workflow serializer with no extra wiring.
-
Constructor Summary
Constructors -
Method Summary
Methods inherited from class ai.mindconnect.workflow.domain.HaltData
canEqual, equals, getCondition, getNext, getResumeParams, getReturnResultExpression, hashCode, isReturnResult, setCondition, setNext, setResumeParams, setReturnResult, setReturnResultExpression, toStringMethods inherited from class ai.mindconnect.workflow.domain.BaseStepData
getAssignResultToVar, getName, getType, setAssignResultToVar, setName, setType
-
Constructor Details
-
FormStepData
public FormStepData()
-