Forms

A web form is a design your organization builds once and Rhythm shows wherever that kind of record is filled in, in the Console and in portals.

How to move through a form in your organization's portal, why the form will not let you continue, how to check your answers before you submit, and what happens after you press Submit.

Use Save & Return Later to keep a partly completed portal form as a draft, pick it up again later, and understand why a form keeps only one draft for you at a time and who else can continue it.

Create a form for a record type and design it in the form designer — pages, buttons and conditional page jumps, field groups, tables, text, custom errors, and CSS — then save, test, retire, or delete it, and understand why a save or delete is refused.

Hooks let a form call a web address or evaluate an expression while someone fills it in — to fill in answers, choose the next page, or look up information.

A reference to what members and staff experience on a web form — skipped pages, hidden questions, disabled buttons, error messages, tables, and drafts — and the design setting that produces each behavior.