Date Picker Variant Selection β Mobile Form Renderer
The mobile form renderer supports two visual variants for date-only fields in forms. Choosing the correct variant ensures the tap experience matches your organization's expectations for how guests and providers interact with date fields on mobile devices.
Audience: Zenoti administrators who configure form rendering behavior for mobile form workflows.
On this page
- Before you begin
- How the two variants differ
- Steps
- AI auto-fill indicators on date fields
- Tips
- Troubleshooting
- Related articles
Before you begin
- You must have administrator access to your organization's form settings.
- The forms module must be active for your organization.
- This setting applies to date-only fields in forms rendered on the mobile form renderer. It does not affect date-time fields or desktop form rendering.
Permission: You need the View permission under Export forms/lists to export form configuration data. Admin path: Configuration > Security > Security roles > [your role] > Administrator > Export forms/lists
Permission: You need the View permission under Guest custom data to view guest custom form data. Admin path: Configuration > Security > Security roles > [your role] > Guest Manager > Guest custom data
Permission: You need the View permission under Service custom data to view service custom form data. Admin path: Configuration > Security > Security roles > [your role] > Administrator > Service custom data
How the two variants differ
Both variants open the same calendar picker when a guest or provider taps a date field. The only difference is the tap affordance β the visual feedback shown when the field is tapped.
The following table summarizes the two variants:
| Variant | Tap behavior | When to use |
|---|---|---|
| Default | Ripple effect is suppressed on tap, matching the original form appearance | Use when you want the date field to look and feel consistent with the original form design |
| V2 | Standard Material ripple appears on tap | Use when you want tap interactions to follow standard mobile platform conventions |
Note: Both variants render the same calendar picker after the tap. Only the tap affordance differs β the date value a guest or provider selects is handled identically by both variants.
Steps
Select the date picker variant
- Navigate to Configuration > Forms.
- Open the form renderer settings for your organization.
- Locate the date picker variant option for the mobile form renderer.
- Select one of the following:
- Default β Uses a ripple-suppressed tap trigger. The field responds to tap without a visible ripple animation, preserving the original form appearance.
- V2 β Uses a standard Material ripple on tap. The field displays a ripple animation when tapped, following standard mobile platform interaction conventions.
- Select Save to apply your selection.
Note: The variant setting is a renderer-level flag. It applies to all date-only fields across forms rendered in the mobile form renderer for your organization. You cannot set different variants for individual forms or individual date fields.
Verify the variant is applied
After saving, open a form that contains a date-only field on a mobile device and tap the date field to confirm the tap affordance appears as expected.
- If you selected Default, the calendar picker should open without a visible ripple animation on the field.
- If you selected V2, a Material ripple animation should appear on the field before the calendar picker opens.
Worked example: Your organization uses a pre-treatment intake form with a "Date of birth" field. After selecting the V2 variant and saving, a provider opens the form on a mobile device, taps Date of birth, and sees a ripple animation on the field before the calendar picker opens. The calendar picker itself looks and behaves the same as it did under the default variant.
AI auto-fill indicators on date fields
When a form uses AI auto-fill, date fields behave the same as other form fields β the mobile form renderer displays visual indicators to help guests and providers identify which fields were populated by AI and to manage any conflicts between AI-supplied values and values already entered.
Identifying AI-filled date fields
When AI auto-fill populates a date field, a pulsing spark icon appears on the field. The icon animates on a 1.2-second fade cycle and remains visible until the guest or provider interacts with the field. This indicator applies regardless of which date picker variant is active β both Default and V2 display the spark icon when the field has been touched by AI auto-fill.
Active fill highlight
While an AI auto-fill sequence is running, the date field currently being filled displays a teal highlight consisting of a background tint and a rounded border. The highlight animates in and out smoothly and has no effect on the field's layout or size. Once the field is no longer actively being filled, the highlight is removed and the field returns to its normal appearance.
Switching between AI-supplied and previous values
If AI auto-fill overwrites a date field that already contained a value, a toggle link appears beneath the field:
- When the AI-supplied value is currently applied, the toggle link is labelled Previous value.
- When the previously entered value is currently applied, the toggle link is labelled AI value.
Tapping the toggle link opens a popover showing a read-only preview of the value not currently applied. To apply that value, tap Use this β in the popover. To dismiss the popover without making a change, tap anywhere outside it.
Note: The Previous value / AI value toggle is only shown when AI auto-fill has overwritten a field that already contained a value. If the field was empty before AI auto-fill ran, no toggle link is displayed.
Important: AI auto-fill can be used only once per form per appointment. If you need to re-run auto-fill, you must open the form in a new appointment context.
Worked example: A provider opens a follow-up intake form. The "Last treatment date" field already contains the value from a prior manual entry. After tapping Fill form using AI, the AI auto-fill sequence runs, a teal highlight appears on "Last treatment date" while it is being filled, and then the spark icon appears on the completed field. Because the field had a prior value, a Previous value toggle link appears beneath it. The provider taps Previous value, reviews the prior date in the popover, decides the AI date is correct, and dismisses the popover by tapping outside it.
Tips
- If your organization uses forms that were designed before the V2 variant was available, the default variant preserves the original visual experience without any changes to existing form layouts.
- The V2 variant aligns with standard Material Design interaction patterns, which may feel more familiar to providers and guests accustomed to modern mobile applications.
- Because both variants open the same calendar picker, switching between variants does not affect how date values are stored or submitted β only the visual tap feedback changes.
- If you are unsure which variant to choose, start with the default variant. You can switch to V2 at any time without affecting form data or submitted responses.
- The spark icon and teal highlight that appear during AI auto-fill are renderer-level visual indicators only. They do not affect the underlying date value or how it is stored when the form is submitted.
- When reviewing AI-filled date fields, use the Previous value toggle to compare the AI-supplied date against any prior entry before accepting either value. This is particularly useful for fields such as "Date of last visit" or "Date of birth" where an existing value may be more accurate than the AI suggestion.
Troubleshooting
| Symptom | Likely cause | Resolution |
|---|---|---|
| The calendar picker does not open when a date field is tapped | The issue is unrelated to the variant setting β both variants open the same picker | Check that the form is fully loaded and the device has an active connection. Select Retry if a retry option is presented. |
| The ripple animation appears even after selecting the default variant | The variant setting may not have been saved, or a device-level cache is showing the previous state | Confirm you selected Save after changing the variant. Close and reopen the form on the mobile device to clear any cached rendering state. |
| The ripple animation does not appear after selecting the V2 variant | The variant setting may not have been saved | Return to Configuration > Forms, confirm the V2 variant is selected, and select Save again. Then reopen the form on the mobile device. |
| The variant setting appears to have no effect on a specific form | The form may not contain date-only fields, or the field type may be date-time rather than date-only | Confirm that the affected field is configured as a date-only field in the form builder. Date-time fields are not governed by this variant setting. |
| The spark icon does not appear on a date field after AI auto-fill runs | AI auto-fill may not have populated that specific field, or the field was already empty and no AI value was found | Check whether other fields in the form display the spark icon. If no fields show the icon, confirm that AI auto-fill completed successfully and was not skipped due to a connection issue. |
| The Previous value toggle does not appear after AI auto-fill overwrites a date field | The date field may have been empty before AI auto-fill ran, so there is no prior value to toggle to | The toggle only appears when AI auto-fill overwrites a field that already contained a value. If the field was empty, no toggle is shown. |
| The teal highlight remains on a date field after the AI auto-fill sequence completes | A rendering delay may be preventing the highlight from animating out | Close and reopen the form on the mobile device. If the issue persists, confirm that the device meets the minimum requirements for the mobile form renderer. |