Form templates
Manage reusable application form field layouts in Settings for faster form creation — and understand how templates differ from the question catalog.
Application form templates are institution-wide field layouts stored in Settings. When you create a new application form inside an application program, you can start from a template instead of an empty form builder — Fuxam pre-populates the new form with the template's fields so you customize cohorts, deadlines, and catalog blocks rather than rebuilding common questions from scratch.
Templates solve a different problem than the question catalog. Templates give you a starting point at form creation; catalog blocks give you ongoing synchronization across live forms. Understanding both — and when to use each — is central to efficient admissions form management.
Why it matters
Every intake cycle, admissions teams create new forms: new cohorts, revised deadlines, occasionally new programs. Much of the field structure repeats — contact details, motivation letter prompts, document upload slots. Without templates, administrators rebuild identical layouts manually or duplicate old forms and strip unwanted configuration.
Templates standardize that starting layout institution-wide. A well-maintained template library means a new form begins with validated field types, sensible labels, and consistent section structure — reducing setup time and lowering the risk that one program's form omits a field others include. Templates do not replace thoughtful form design: you still assign cohorts, enable catalog blocks, configure platform mapping, and preview before publish.
The portal settings page Application form templates documents the same feature from the Settings navigation perspective.
Key concepts
| Term | Meaning |
|---|---|
| Application form template | A named field layout in Settings — question types, labels, and options stored as a reusable starting configuration. |
| One-time copy | Selecting a template at form creation copies fields into the new form; no ongoing link to the template. |
| Saved field layout | The questions, labels, and options stored in the template — the same structure the form builder uses. |
| Template vs catalog | Templates bootstrap new forms; catalog blocks enable live sections that update when forms are saved or republished. |
Comparison: templates and catalog blocks
| Aspect | Form templates | Question catalog blocks |
|---|---|---|
| Location | Settings → Configuration Wizard → Applications → Go to Applications | Campus Management → Applications → Question catalog |
| When applied | At form creation, under Quick Start (Optional) in the Create sheet (optional) | Enabled anytime in form builder |
| Synchronization | One-time copy; no live link | Updates propagate when forms are saved or republished |
| Best for | Standard starting layouts for new forms | Shared sections maintained centrally across programs |
| Includes cohorts or deadlines | No — configure on each form after creation | No — configure per form in form preferences |
Many institutions use both: a template for the baseline custom-field layout, plus catalog blocks for institution-wide sections like declarations or document checklists.
How to open form templates
The template list is not in the settings sidebar. Open it from the Configuration Wizard:
Go to Settings → Configuration Wizard.
On the item Applications, select Go to Applications. The template list opens (/dashboard/settings/application-form-templates).
Search by name, or scan the columns Name, Description, fields (number of fields) and Created at.
Viewing templates requires permission to view application programs. The Applications item in the Configuration Wizard needs the Fuxam Apply package and permission to use the Configuration Wizard.
How to create a template
On the template list, select Create Template. A full-page editor opens.
Under Template details, enter a Template Name (required) and, if you like, a Description (Optional).
Add fields from the field types list on the left. Select a field on the canvas to edit its properties in the panel on the right, and drag fields to reorder them.
Switch to the Preview tab to see the form as applicants will, then back to Edit if you need changes.
Select Save. You see Template created successfully and Fuxam returns you to Settings → Management → Application, not to the template list.
Template fields support the same types as the form builder: Text, Email, Phone, Date, Long text, Number, Dropdown, Card selection, Radio, Checkbox, and File upload. Build the layout you want every new form of a given type to start with — you can always add program-specific fields after applying the template.
How to use a template when creating a form
Open the application program and go to its Forms list.
Select Create in the toolbar. The Create sheet opens.
Enter a Form Title, pick at least one Cohort, and optionally set Submission Deadline (Optional). Create stays greyed out until a title and a cohort are set.
Under Quick Start (Optional), pick your template from the Field Templates group. (Pick a form under Existing Forms to copy it instead, or keep Start from scratch.)
Select Create. You see Form Created Successfully! and the form builder opens with the template fields filled in. Adjust catalog blocks and custom fields as needed.
After creation, the form is a normal draft in the form builder. Enable question catalog blocks, configure platform mapping, set required rules, and publish when ready. Template fields and catalog block fields coexist on the same form.
How to duplicate or delete templates
| Action | Steps |
|---|---|
| Create | Select Create Template, enter a Template Name, add at least one field and select Save. |
| Edit | Select the template name. The Edit Template page opens; change fields and select Save. |
| Duplicate | Select ⋯ on the row → Duplicate, enter a Name for the copy and select Duplicate. |
| Delete | Select ⋯ on the row → Delete and confirm Delete. This cannot be undone; existing forms are not affected. |
Duplicating is useful when two programs need nearly identical starting layouts with small differences — copy, adjust, and save as a new template name.
Best practices
- Templates for structure, catalog for shared content — Put repeatable live sections in the catalog; put baseline custom-field skeletons in templates.
- Do not expect template edits to update existing forms — If a field label must change on all live forms, update catalog blocks or edit each form directly.
- Pair templates with program publish workflow — A templated form still needs cohort assignment, preview, form publish, and application program publish.
- Audit templates seasonally — Remove obsolete templates to keep the dropdown manageable for form creators.
Common pitfalls
- Assuming templates include catalog blocks — Templates copy custom fields only. Enable catalog blocks separately in the form builder.
- Choosing the wrong template at creation — Template selection happens under Quick Start (Optional) in the Create sheet. Changing the starting layout later means editing fields manually or creating a new form.
- Duplicating forms when a template would suffice — Copying a form under Existing Forms copies program-specific configuration (cohorts, deadlines, publish history context). Templates are cleaner for a fresh intake with the same field structure.
FAQ
If I edit a template, do existing forms update?
No. Templates copy fields once at form creation. To change live forms, edit each form in the builder or use catalog blocks for synchronized content.
Can I apply a template to an existing form?
The documented workflow applies templates in the Create sheet. For existing forms, add fields manually or duplicate the form and adjust.
Where is the Settings page documented?
See Application form templates in Apply portal settings for the Settings navigation overview.
Related pages
Build an application form
Customize a form after applying a template — cohorts, mapping, publish.
Manage the question catalog
Shared question blocks for ongoing reuse across forms.
Application form templates in Settings
Portal-level settings overview for template management.
Application programs
Programs that contain the forms you create from templates.