LaneyGuide
Browse featuresForms and submission records

Design form fields and conditions

Choose the stored outcome first.

How-toVerified Oct 12, 2026Owner Laney Product

After this taskOnly intended fields appear and missing required data blocks submission.

Starting conditions and inputs

Specify the collection purpose, required fields and display branches.

Values for this task

entry_url, form_id, response_mode, target_resource, field_definitions, branch_inputs, field_label, show_when, form_preview_url, branch_value

Command sequence

open "$entry_url" && snapshot -i

click "$form_row" && snapshot -i

click "$response_mode_picker" && snapshot -i

click "$response_mode_option" && snapshot -i

click "$form_field" && snapshot -i

fill "$field_label_input" "$field_label" && snapshot -i

# Condition: Run the next click only if the required state differs from the requested value. Otherwise skip it.

click "$required_switch" && snapshot -i

fill "$show_when_input" "$show_when" && snapshot -i

open "$form_preview_url" && snapshot -i

fill "$branch_input" "$branch_value" && snapshot -i

click "$submit_form" && snapshot -i

get text body
Ref targets and expected results
#Command / refTarget and verification
1click $form_rowForm record to configure
2click $response_mode_pickerResponse-mode picker
3click $response_mode_optionResponse mode matching the collection purpose
4click $form_fieldForm field to edit
5fill $field_label_inputField display-name input
6click $required_switchRequired switch only when its current state differs from the intended value
7fill $show_when_inputShow When input using key=value syntax
8openForm preview URL
9fill $branch_inputInput controlling the conditional branch
10snapshotRead the full snapshot to check which fields are visible.
11click $submit_formSubmit the test form with a required value missing
12get textRead the required-field validation error.

Check the result

Only intended fields appear and missing required data blocks submission.

Resuming after interruption

Read the same IDs again. Preserve correct settings and update only differences.

Define the collection task

Choose the stored outcome first. Use update_self for customer updates, insert for new reservations, profile_then_insert for profile plus reservation, and update_target for an existing reservation.

Choose field types

Choose static fields in Forms and create additional questions in Custom fields. Set target, key, label, type, required state, visibility, and form scope. Do not duplicate name, email, or phone with custom fields using those keys.

Set display conditions

Use Show When with a controlling key and value to display a conditional field. Conditions support one level, not nested branching. Hidden conditional fields are not required; check the required fields in each visible branch.

Test every input branch

Test both matching and nonmatching conditions. Test missing required values, wrong types, and options. Check how hidden values affect the saved result. Compare submissions with the customer and reservation sources.

On this page