Submit Form

Configure form submission actions for viewer-entered MP5 values

Use the Submit Form connector when a viewer action should submit values entered in one or more Input Field connectors. Submission can save values in Blings Form Data or trigger custom handling for an external workflow.

Options

Option	What it controls	Notes
Submit layer	The button or interactive layer that submits the form.	Confirm the layer is visible, clickable, and clearly tied to the form.
Captured fields	The Input Field values included in the submission.	Confirm each field has a stable name.
Submission handling	Whether values are stored in Blings Form Data or handled with custom code.	Match this to the project's data collection and compliance workflow.
Validation behavior	What should happen when required values are empty or invalid.	Avoid submitting incomplete values when the workflow depends on them.
Success state	What the viewer sees after submission.	Use a clear next state, message, frame jump, or branch when needed.
Failure behavior	What happens if submission cannot complete.	Keep the viewer experience controlled even when an external action fails.
Internal description	A note explaining where submitted data goes.	Useful for operations and QA review.

Configure Submit Form

1

Confirm Input Fields

Make sure every value that should be submitted has an Input Field connector with a clear field name.

2

Select the Submit Layer

Choose the button, hotspot, or interactive layer that should submit the form.

3

Choose Submission Handling

Select whether the submission should be saved in Blings Form Data or handled with custom code.

4

Define Empty and Failure Behavior

Decide what happens when required fields are blank, invalid, or when submission cannot complete.

5

Preview the Full Flow

Test typing, submitting, success behavior, empty fields, and failure behavior before publishing.

Success Checks

Before publishing a Submit Form connector, confirm:

• The submit layer is clickable in the player.

• Each submitted field has a stable name.

• Empty or invalid values are handled intentionally.

• Form Data or custom handling has been tested.

• The viewer sees an appropriate state after submission.

• Submission does not interfere with other player interactions, links, or analytics.

Input FieldData, Catalog, and Forms