• CREATING AND MANAGING FORMS • SETUP GUIDE

How to Preview, Test, and Publish a Form

By Rivio Support Team
2 min read

What you will achieve in this guide

Follow this step-by-step documentation to configure custom B2B registration forms, approval workflows, and customer tagging.

EXPECTED SETUP TIME 5-10 Minutes
COMPATIBILITY All Shopify Themes & Plans
TECHNICAL DIFFICULTY Zero Code Required

Preview a Shopify registration form, check required fields and layout, and publish it after a complete test submission.

Before you begin

Identify the form by both its internal name and slug before making changes. Check where that slug is used on your storefront, and review dependent rules or mappings before removing questions.

What a complete test should cover

The builder preview helps inspect questions and styling, but it does not prove that the storefront block uses the right slug or page template. Test the real page after saving both the form and the theme configuration.

Include a valid application and an invalid attempt. Check required fields, allowed upload types, conditional visibility, Next and Back controls, the success message or redirect, and the recorded submission. Approval and integrations need their own checks after receipt.

Set up this workflow

  1. Save your form’s latest builder changes.

  2. Review the live preview beside the builder.

  3. Open the full-page preview to inspect the complete form.

  4. Check required inputs, choice options, file restrictions, conditional visibility, and steps.

  5. Publish the form and test it through the saved storefront app block.

  6. Confirm the application appears in Submissions with the expected answers and status.

Example

Test Demo Wholesale Application once with an empty required email and once with a valid email. If the form is multi-step, check Next and Back before completing it.

Expected result

Invalid input is rejected and a completed valid application reaches Submissions.

Limits and important behavior

  • The storefront theme can affect the final display, so a live preview is not a substitute for storefront testing.
  • Use a different test submission when duplicate protection rejects repeated data.

Troubleshooting and verification

If preview succeeds but the real page fails, compare the block slug and page template, then test required inputs and upload restrictions on that real page. Use a fresh test identity if duplicate protection rejects the repeated test.

Screenshots to add

Screenshot placeholder: Capture the relevant app screen for “How to Preview, Test, and Publish a Form” after completing the setup. Show the controls used to save your form’s latest builder changes. Add a second screenshot showing the result of this check: Confirm the application appears in Submissions with the expected answers and status. Use dummy applicant details and mask any secrets.

Related guides