Skip to main content

Conditional Logic for Application Steps, Sections, + Repeatable Groups | September 2026

Application conditional logic now works at the step, section, and repeatable group level, so one application can adapt to different applicant types instead of splitting into parallel applications.

Written by Michael Stephenson

Released: September 15, 2026

Overview Header

Conditional logic in applications now works at the step, section, and repeatable group level, not just on individual fields. You can show or hide an entire step based on how an applicant answered an earlier question, hide a section within a step, and conditionally show, hide, or require a repeatable group.

Conditions are built with the same condition builder you already use for fields, so there is nothing new to learn. A single application can now adapt to international versus domestic, transfer versus first-time, or adult versus traditional applicants instead of maintaining parallel applications or pushing content into Supplemental Forms.

Decision previews and PDFs have been corrected to match as well, so reviewers see the version of the application the applicant actually completed.

Details Header

Conditions on Steps and Sections

  • Step-level visibility: attach a condition to a whole step using the existing condition builder (target field, operator, value, with and/or grouping). Previously conditions could only be attached to individual fields or to a single grouping field.

  • Section-level visibility: show or hide a section within a step. The section header hides along with the section, so applicants no longer see empty labeled sections that do not apply to them.

  • Hiding a step hides everything inside it: sections and fields within a hidden step are hidden too, and the step disappears from the applicant’s navigation and progress.

Conditions on Repeatable Groups

  • Visibility: show or hide a repeatable group the same way you would a step or a section.

  • Required If: require a minimum number of entries only when a condition is met. You can require at least one previous college entry only for transfer applicants, for example.

  • Limited If: cap the number of entries only when a condition is met, and lift the cap when it is not. Required If and Limited If are separate settings, so you can use both on the same group.

  • Conditions can reference fields inside a group: a condition targeting a field within a repeatable group is met when at least one entry matches.

Decision Previews and PDFs Match What the Applicant Saw

  • Conditional markdown follows its conditions: text blocks shown only to certain applicants no longer appear in every decision preview and PDF. Reviewers see the version the applicant actually got.

  • Submission form explanations are no longer dropped: if an applicant answered Yes to a submission question such as a conduct or academic history disclosure, their explanation could be missing from the generated PDF. It now appears.

  • Hidden steps and sections are left out: with the same setting on, content inside a step or section the applicant never saw is omitted from the generated PDF.

  • These apply when Hide Unused Conditional Fields is enabled under PDF Output. That setting is off by default, so nothing changes for applications that do not use it.

  • One thing to watch on the submission form: conditions on submission form fields are not evaluated when the PDF is generated. If you used conditional logic there to keep a field out of the PDF, it will now be included. Conditions on your application steps and sections are unaffected.

Things to Know

  • Adding a condition hides the content by default. A step or section with no conditions is visible to everyone. As soon as you attach one, it starts hidden and appears only for applicants who match.

  • Hidden required content never blocks submission. Validation skips hidden steps, sections, and fields, so a required field an applicant never saw cannot stop them from submitting. This is how fields already behaved, and it now extends to steps, sections, and groups.

  • Hidden values are not cleared. If an applicant fills in conditional content and then changes the answer that hides it, those values stay on the contact record. To clear them, use the workflow method documented in Fields, Validation, + Conditional Logic.

Benefit Header

Schools running distinct applicant journeys can consolidate into one adaptive application instead of maintaining several. Content that had to live in Supplemental Forms, where applicants skip, abandon, or complete it late, can move back into the main application. International versus domestic, transfer versus first-time, adult versus traditional: one application now handles all of them without the maintenance cost of running them side by side. And because previews and PDFs now reflect the same conditions, the document staff review is an accurate record of what the applicant was asked and what they answered.

Support Docs Header
Did this answer your question?