Manual input
<sea-manual-input> edits the form required by a blocked step in an existing process. Bind it to the step's label, or use run-step-id to select an exact step instance.
When a step requires several forms, set output-form-id to choose one form or output-submission-id to choose its exact linked draft. Completing that form leaves the other inputs open.
| Integration | Entry |
|---|---|
| React | SeaManualInput from @sea-dev/widget-lit/react/manual-input |
| Without React | @sea-dev/widget-lit/manual-input |
html
<sea-manual-input step-label="applicant-input"></sea-manual-input>Place it inside a process and Sea context, with the page API host configured before mounting. The blocker supplies the required form. The widget reuses the draft linked by the backend, or prepares a draft after the user chooses to enter input. Mounting it creates no input submission.
Completing the input waits for pending field saves, finalises the submission and attaches it to the exact run step if needed. The backend then resolves the dependency. Failed saves leave the input open for correction or retry.
Attributes and properties
| Property | Attribute | Type | Default | Description |
|---|---|---|---|---|
stepLabel | step-label | string | "" | Selects the pipeline step with this unique label. |
stepRole | step-role | PipelineStepRoleWire or undefined | — | Constrains the selected step to this execution role. |
stepId | step-id | string | "" | Selects a pipeline step definition by ID. |
runStepId | run-step-id | string | "" | Selects an exact step instance in the current run. |
outputFormId | output-form-id | string | "" | Selects the required form and its linked input. |
outputSubmissionId | output-submission-id | string | "" | Selects an exact linked input submission. |
Events
| Event | Type | Description |
|---|---|---|
input-created | CustomEvent | { runId, runStepId, submissionId } after a draft is created without resuming the run. |
input-completed | CustomEvent | { runId, runStepId, submissionId } after edits are saved, the input is finalised and any new input is connected. |
Styling parts
| Part | Description |
|---|---|
root | The manual input container. |
toolbar | The input actions and the editor toolbar. |
actions | The input actions. |
content | The input editor. |
status | Input status and errors. |
API and transport
The widget reads the required form and submission, saves field corrections and finalises the input through the submission API. A new draft uses submission.create. An unlinked completed input uses pipeline.manualInput with runId, runStepId and submissionId.
Custom transports implement these operations alongside the process reads. Run creation belongs to your application.