• FORM FIELDS AND CONDITIONAL LOGIC • SETUP GUIDE

How to Use the Date Field

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

Use Date for a calendar date relevant to the application. This guide explains setup, a practical example, and how to check the result on your Shopify storefront.

When to use it

Choose this type when you need a calendar date relevant to the application. Choose the type before configuring mappings, visibility conditions, or approval rules that depend on the answer.

Before you begin

Open the intended form in Rivio B2B Registration Forms and confirm its name and storefront slug. Inspect template fields and smart-block sub-fields so you do not ask for the same information twice. Use dummy details for your first test.

Set up Date

  1. In the form builder, select Add field and choose Date.

  2. Expand its settings and enter a clear label or heading, such as Business start date.

  3. Explain the meaning of the date rather than relying on a format-only placeholder. Review the date controls actually available and whether the answer is necessary for the reviewer.

  4. Drag the element into the intended position. If the form uses steps, review its assigned step.

  5. Select Save, preview the form, and confirm the actual storefront page loads this saved form’s slug.

Example

Question or content: Business start date

Example: A dummy date selected in the date input

Adapt this example to the information your team needs. Use help text to explain the expected answer, and require it only when your review process needs it.

Test and expected result

Choose a date, submit, and compare the recorded answer. Test the date input on desktop and mobile because the browser can present different controls.

Expected result: the saved application contains the intended answer. Any configured visibility, rule, or mapping is checked separately; collecting an answer does not itself approve an applicant.

Limitations and important behavior

Do not promise age calculations, reminder scheduling, or date-based operators that the app does not expose. A collected date is application information.

Troubleshooting

If applicants enter the wrong kind of date, clarify whether you mean registration date, store opening date, or another event. If you need a rule, inspect the operators offered for this field before designing the policy.

Screenshots to add

  • Screenshot placeholder: Builder with Date expanded, showing Business start date and the applicable saved settings.
  • Screenshot placeholder: Dummy submission showing the example answer; include the storefront input if it helps explain selection or validation.

Related guides