1. Form Builder Platform
  2. Features
  3. Submissions
Feature · Submissions

Submissions

Keep each submitted line tied to its form.

OverviewSubmission decisions
Form Builder Platform · Submissions

Submission decisions

Form submissions

New
ParentSequenceDescriptionOutcomeSource reference
FD-8846440Pending fs-181PendingSR-937
FD-8570790Rejected fs-417PendingSR-902
FD-9515740Pending fs-856PendingSR-521
FD-6886050Rejected fs-629PendingSR-838
FD-8199260Pending fs-213PendingSR-842
6 of 6 records
Pending fs-181Form submissions · FS-40207
Pending
ParentFD-88464
Sequence40
Source referenceSR-937
Example screen with sample data

What you can do

Keep each submitted line tied to its form

Submitted data is stored as lines under a parent Form Definition. The line can carry a sequence, description, quantity, unit, observed date, amount, source reference and outcome. The parent supplies the published schema revision used when an operator accepts a line. The Form Submissions Review screen brings pending and rejected lines into the reviewer’s queue with their parent context.

Each submitted line keeps a parent form definition. Its outcome distinguishes a line awaiting review from an accepted or rejected one. Acceptance uses the parent published schema version, including conditional required answers, and increases the parent valid submission count with an operation trail.

How the work is organized

  • Keep the parent. Link the line to the published definition that supplied its rules.
  • Review the answer. The Independent Reviewer inspects pending lines, source reference and evidence in context.
  • Record the outcome. The Operator accepts a valid reviewed line; the Operator can mark a rejected line for follow-up.

What to agree during setup

The Operator and Independent Reviewer agree who checks the response against the versioned rule and who records the outcome. A line marked Pending needs review before the Operator accepts it. The source reference helps identify where the answer came from, while the parent identifies the form that governed it. Test conditional required fields using the published revision, including a case where an answer is required.

Agree who checks each pending line and who may record its outcome. A reviewer decision on a form revision should not be mistaken for a line outcome. The Operator must check that the parent is Published before accepting the line.

Check the handoff on an actual case

Use a published form with one conditional requirement. Enter a complete line and a second line that omits the conditionally required answer. Review both in the queue. The accepted line should contribute to the parent valid submission count with an operation trail; the incomplete line should not be accepted. Check the decision and any evidence before telling the requester the result.

Compare a complete line with one missing a conditionally required answer. Inspect the parent status, schema version and each outcome. Only the valid accepted line should raise the parent valid submission count. Keep a rejected line visible to the reviewer.

What your team sees

  • Submission decisions — Review pending and rejected lines with their parent form context.
  • Accepted submission lines — Inspect accepted lines with their observation date and parent.

Follow the work through

See definition and publication and submission review for the decisions that connect this module to the next one.

What it keeps track of

Data model
Form submissions
Submitted form data validated against the exact published schema version.
Form definitions
Versioned published form schemas with conditional logic and validation rules.
Review decisions
Independent review decisions recorded against an exact source revision.
Operation runs
Immutable operation run record per source and approved action revision.
Operation steps
Numbered step trace within an operation run with persisted input/output identities.

Who uses it

Permissions
Operator
Handles line outcomes.
Independent Reviewer
Checks submissions and evidence; Form Owner checks the governing definition.

Set up Form Builder Platform your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started