Form Submission Workflow

How a visitor's form submission flows — capture, record landing, notification, integration push.

The Form Submission Workflow is the cross-product process that handles a form submission from the moment a visitor clicks Submit on the public site through the moment the form data lands in the admin, fires the configured notifications, and pushes to any wired integrations. This page is the Reference definition.

What is this for?

Read this page when you want the structural definition of the submission-flow path — entry from the public site, the handoff into the admin, the notification fire, and the integration push.

Good use cases

• You are scoping a form-driven capture workflow.
• You are explaining to a stakeholder how SGEN handles form data.
• You hit a "did the form data go anywhere?" question and want the model laid out.

What NOT to use this for

• Step-by-step form-build procedures — open the relevant Guide.
• Per-release shipped change — open What's New or Changelog.
• Per-component capability detail — open the corresponding surface Reference.

How this connects to other features

• Workflows Overview — parent Reference area.
• Lead and Tracking Workflow — sibling that often consumes form submissions as leads.
• SG-Admin Overview — surface where the submission record lands.
• Notification Logic — automation layer that delivers the notification.
• Email and SMTP — transport for response emails.

Definition

The Form Submission Workflow is the cross-product process triggered by a visitor's form submission. It carries the data from the public capture surface through the admin record landing, fires the configured notifications, and pushes to any wired integrations.

The defining property is multi-handoff. A single submission event produces effects across the public surface, SG-Admin, the notification layer, and (often) one or more integrations.

Purpose

The purpose of this page is to define the submission flow as a Reference layer. It explains the entry surface, the handoff sequence, and the downstream effects.

Scope

This page covers the workflow at the Reference level.

The page covers:

• The entry surface (public site form).
• The record-landing handoff (the admin → My Forms).
• The notification fire (Notification Logic).
• The integration push (where wired).
• The boundary against form-build procedures.

• Step-by-step form-build — Guides.
• Per-form-type configuration — SG-Admin Forms module Reference.
• Per-release shipped change — What's New or Changelog.

Entry surface

Public site form

The visitor fills out the form on the public site and clicks Submit. The submission event fires.

Handoff sequence

Handoff 1 — Public site → SG-Admin record

The submission lands as a record in the admin → My Forms. The record carries the form identity, the submitted field values, the visitor metadata (timestamp, source page).

Handoff 2 — the admin → Notification Logic

If the form configuration includes notifications, Notification Logic fires the configured notifications per channel preferences. Operator-facing email or in-app alert reaches the recipient.

Handoff 3 — the admin → Integration push (where wired)

If the form is wired to an integration (CRM, email-marketing system, custom endpoint), the submission also pushes to the connected service. Integration-driven Automation handles the push.

Downstream effects

Operator visibility

The operator sees the submission in the admin → My Forms and (per notification preferences) in their notification surface.

Visitor confirmation

If the form configuration includes a confirmation email, Email and SMTP transport delivers the confirmation to the visitor.

Audit trail

The submission event records to the platform audit log per Notification Logic / audit pattern.

Constraints and boundaries

This Reference covers the cross-product submission flow.

Use this Reference for:

• Understanding the multi-handoff submission path.
• Reasoning about where a submission goes after Submit fires.
• Routing operators to the correct surface for diagnosis.

• Per-step form build — Guides.
• Per-form-type configuration — SG-Admin Forms module Reference.
• Per-release shipped change — What's New or Changelog.

Public boundary

This page is intentionally public-safe.

Examples

Example 1 — Contact form submission flows end-to-end

A visitor submits the contact form. The record lands in the admin → My Forms; the operator gets an email + in-app notification; the submission pushes to the connected CRM. The visitor receives a confirmation email. All four handoffs complete cleanly.

Example 2 — Notification did not arrive

The submission lands in the admin (visible in My Forms). The notification did not arrive. The operator opens this Reference, walks the handoff sequence, identifies that the issue is at Handoff 2 (Notification Logic) rather than at the form itself, and proceeds to the Notification Logic Reference for diagnosis.

Example 3 — Stakeholder asks "where does the data go?"

The platform lead opens this page and walks the stakeholder through the four handoffs. The Reference grounds the conversation in the platform's submission model.

Documentation guidance

Use this page as the structural definition for the form submission flow. Procedural detail belongs in Guides; per-release behavior change belongs in What's New or Changelog.

Reading order

Open this page when scoping form-driven capture or troubleshooting submission-flow questions.

Related reading

• Workflows Overview — parent Reference area.
• Lead and Tracking Workflow — downstream consumer of submission data.
• SG-Admin Overview — record landing surface.
• Notification Logic — automation layer.
• Email and SMTP — transport for confirmation email.
• Content Update Workflow — sibling for editorial update cycle.
• Publishing Workflow — sibling for publish mechanics.

Vocabulary cross-reference

• Submission event is the moment the visitor clicks Submit.
• Record landing is the moment the submission becomes a record in the admin.
• Notification fire is the moment Notification Logic delivers the operator-facing alert.
• Integration push is the moment (where wired) the submission flows to a connected service.

Maintenance discipline

When the form submission flow changes across releases (new handoff, new integration push surface, new notification rule), update this Reference and log the change in Changelog.

Related reading