Programme Choices

A choice is the answer to the question "what are you applying to?". It is a Product Choice field on the application form that lets the applicant pick one or more classes or courses, and a campus where the class runs on several. Setting Will applicants need to choose a product? to Yes on the template's Details tab adds one. Choices decide which class the applicant's journey is created in, which fee applies, and which evaluations and offers follow.

Primary and Secondary Choices

A template can have up to two choice fields:

Choice Purpose
Primary choice What the applicant applies to. Drives the journey, the fee per programme, capacity checks and the default class for evaluations.
Secondary choice An optional second preference, with its own association settings.

Each Product Choice field defines:

Setting Description
Product choice Primary or Secondary.
Product choice selection The classes and courses offered, chosen with Edit products.
How many choices? One or Multiple.
Campus display Display all campuses, Don't display campus or Display specific campus.

A template becomes open only when its primary choice offers at least one open class or course (for institution-wide templates that require a programme choice). See Application Templates.

What Choosing Does

Journeys

Primary product choice automation on the Details tab decides what picking a product does. With Add the applicant to new products (the default), picking a class or course:

  1. Adds the applicant to that class with a journey at prospect::started_application.
  2. Links the application to that class, so it is found when staff filter applications by that class.
  3. Moves the journey on with start_application if the application is already started.

With Remove applicant from previously selected products ticked (the default), changing the choice removes the applicant's journey from the class they no longer chose. If the journey cannot be removed (for example because other records depend on it), it stays. Do not take any automated actions turns all of this off.

Secondary product choice automation has the same options. For the secondary choice it defaults to no automated actions.

After Submission

Applicants cannot change choices once the application is submitted. Staff with applics.applications_change can, by editing the product choice field on the application's form tab. When staff change the choice on a submitted application, the new journey keeps the state of the one it replaces (for example applicant::submitted) and records which journey it replaced, so the applicant does not drop back to prospect.

Note: Before submission, a new journey always starts at prospect::started_application, whatever state the replaced journey held.

Associating by Hand

Staff with applics.applications_associate can link an application to one of the profile's existing class journeys with Associate existing application, or remove the link with Disassociate application, from the class on the profile. This is useful for applications that did not create the journey themselves.

Restricting Choices to the Applicant's Own Products

Which products can applicants select in the product choice field? offers A specific selection of products (the default) or Products for which the applicant has a journey in a specific lifecycle state. The second makes the template offer only the classes and courses the applicant already holds a journey in, in a state the template is available to. Use it for forms that existing students or admitted applicants fill in about a product they already have.

With this setting on:

  • Choosing never creates, moves or removes journeys; the application is only linked to the chosen class.
  • A closed class is still accepted.
  • The template ignores whether its classes are open, because those products are usually closed by then.
  • Only offer this form for the products configured in its product choice field additionally limits the offer to products that are both held by the applicant and listed in the choice field. An applicant with no such product cannot start the application.

Validation on Submit

Check Error the applicant sees
The chosen class runs on several campuses and no campus was picked (when campuses are enabled) "campus can't be blank"
The chosen class is no longer open "selection is closed"
The chosen product is fully booked (capacity automation) "Programme · Class is now fully booked. It filled up while you were completing your application. Choose another option to submit."

The closed-class check is skipped for applications with an extended deadline, templates restricted to the applicant's roles, and UCAS templates.

Capacity Automation

With Capacity automation > Stop accepting applicants for fully booked products ticked, Full Fabric stops accepting applicants for classes and courses that have reached their maximum capacity:

  • A product that is fully booked cannot be submitted. The applicant's own place does not count against them.
  • Submissions to a product with a maximum capacity are processed one at a time, so two applicants cannot take the last place together. If the lock is busy, the applicant sees "Your submission could not be processed, please try again."
  • When every open primary-choice product is fully booked, the template is treated as closed and visitors see "All places have been filled." It reopens on its own as soon as a place frees up.

Capacity automation has no effect on templates restricted to the applicant's roles.

Choices Elsewhere

  • Start links can pre-select the primary choice. See Applying and Submitting.
  • Fees can depend on the primary choice. See Fees and Payment.
  • Subjects: when the template lets applicants pick subjects from the chosen class's study plan, the selection is checked on submit and any choice whose course closed or was deleted is removed. The applicant sees "Your subject selection has changed. Please review it before submitting."