Cornerstone Forms Conditions

Cornerstone Forms comes with a number of different Conditions which will help you build out pages and Forms.

Frontend Conditions

Frontend Conditions (also called Input Conditions in the builder) let you show or hide any form input based on the live values of other inputs in the same form. They are evaluated in the browser in real time as the user fills out the form, and the same logic is mirrored server-side so hidden inputs are automatically excluded from validation.

Frontend Conditions are configured directly on each input element in the General tab. Toggle Input Conditions on to enable the feature, then build your condition rules using the condition builder that appears below.

Condition statements

Each statement targets a specific form input by name and checks its current value:

• Input Data — Select a form input from the tree picker. The picker shows all named inputs in the same form.
• Criteria — The value to compare against. The comparison is a simple string match on the live field value.
• is / is not — Flips the match. is shows the element when the value matches; is not shows it when the value does not match.

AND / OR logic

The condition builder supports grouping using the standard show-condition group model:

• Within a group — all statements must pass (AND).
• Between groups — only one group needs to pass (OR).

Add a new group with the "Add Group" button to create an OR branch.

Server-side enforcement

When a form is submitted, the same condition logic runs on the server. Any input whose Frontend Conditions evaluate to hidden is excluded from validation. This means required fields that are conditionally hidden will not block form submission when they are not visible to the user.

Form Submitted

This Condition will check if the current Form Context has had a submission. This can be useful by hiding the Form content on a submission. By using the No modifier this can display an intro message helping the user on the Form.

Form Submitted Without Errors

This differs from Form Submitted because it only triggers the Yes Condition when the Form had no errors. Using the No modifier would mean that the Form submitted and has an error.

Form Errors

This Condition checks whether the current Form Context has any Validation errors. Using Yes will trigger when errors are present, making it useful for displaying error messages or styling. Using No means the Form has no errors.

User has Submitted

This Condition checks whether the currently logged-in user has ever submitted this Form, based on stored submission data. Unlike Form Submitted, which only reflects the current page request, this persists across sessions. Using Yes can gate content for returning submitters, while No can show a Form only to users who have not yet submitted.

Note: This Condition requires a logged-in user and a valid Form Context ID. It will not function correctly for guest users or outside of a Form context.

File Upload

By using the name property of either a File Input or a Dropzone, this Condition checks whether a file was uploaded for that field.

• Exists — A file was uploaded for the specified field name.
• Empty — No file was uploaded for the specified field name.

Summary

Conditions give you control over what users see before, during, and after Form submission. Combined with Validations for data checking and Actions for post-submission logic, you can build Forms that respond to every scenario.

• Cornerstone Forms Overview — Getting started with Forms
• Form Elements — All available Form Elements
• Form Validations — Validate submitted data
• Form Actions — What happens after submission
• Dynamic Content — Access Form data with tokens