UCAS
The UCAS integration brings applications made through UCAS, the UK admissions service, into Full Fabric. It supports two UCAS schemes, UCAS Undergraduate and UCAS Conservatoires, each connected and enabled on its own. Full Fabric pulls each applicant's details, choices, qualifications, personal statement, references and background information from UCAS twice a day, creates or updates their profile and application, and places them in the programme and class you map to each UCAS course. When staff move an applicant's journey to a state you choose, Full Fabric sends the matching decision back to UCAS.
This page covers setup, cycles, course matching and decisions. For the sync schedule, how applicants appear and troubleshooting, see UCAS sync and troubleshooting.
How It Works
- An administrator connects a scheme: in Settings → Other integrations → UCAS, enter the scheme's UCAS credentials, validate them and enable the scheme.
- Full Fabric prepares the cycle: enabling creates the locked application template that UCAS applications are imported into, then starts a first sync.
- Applications arrive on a schedule: syncs run twice a day, or on demand with Sync Now.
- Staff map UCAS courses: under Course Matching, each UCAS course code is mapped to a Full Fabric programme and class. An application is submitted once one of its choices is mapped.
- Decisions go back to UCAS: moving a journey to a mapped state sends a UCAS decision for that choice.
Connecting a Scheme
Go to Settings → Other integrations → UCAS. The page has one card per scheme (UCAS Undergraduate and UCAS Conservatoires) and an Advanced card. The UCAS link only appears when the UCAS integration is switched on for your institution; it is off by default.
Each scheme card has a Credentials section. Click Add credentials (or Update credentials) and fill in:
| Field | Required | Notes |
|---|---|---|
| Institution code | Yes | Your UCAS institution code for this scheme. Each scheme keeps its own. |
| Username | Yes | The UCAS XML-Link username issued for this scheme |
| Password | Yes | The XML-Link password. Never shown after saving; leave it empty to keep the saved one. |
The Environment dropdown selects which UCAS service to connect to: HEP1 (Test), HEP2 (Test) or Production. It is shared by both schemes.
Click Validate and save credentials. Full Fabric signs in to UCAS with the values and only stores them if UCAS accepts them. On success the page shows Credentials valid. The password expires on a date, and the card lists Password expiry and First synced cycle. Once credentials are saved, Validate credentials re-checks them without retyping the password.
Warning: UCAS locks an account after three failed sign-in attempts. Check the values before validating again after a rejection.
Enabling and disabling
The Enable button on the scheme card is available once the credentials have been validated, have not since been rejected by UCAS, and are not open for editing. Enabling a scheme:
- Creates the scheme's application template for its latest cycle, named UCAS Applications followed by the year (with (Conservatoires) appended for that scheme)
- Records the First synced cycle the first time UCAS is enabled
- Adds the default decision mappings the first time the scheme is enabled
- Refreshes UCAS reference data, then runs a sync (the very first one fetches every application UCAS currently holds for the scheme)
While a scheme is enabled its credentials are read only (Disable the scheme to change its credentials.). Disable asks for confirmation, stops the scheme's syncs and removes any queued ones. Imported profiles, applications, templates and course mappings are kept.
Note: Full Fabric checks each enabled scheme's password every day and changes it in UCAS automatically when 14 days or fewer remain before it expires. The new password is never displayed, so give Full Fabric a UCAS username that no other system signs in with.
Cycles and Templates
A UCAS cycle is identified by its year of entry. First synced cycle is the earliest cycle the integration imports; applications from earlier cycles are skipped. Later cycles are picked up automatically: when a sync first finds applications for the next cycle, Full Fabric creates that cycle's template, refreshes reference data, carries course mappings forward and runs a follow-up sync (see UCAS sync and troubleshooting).
The latest cycle and the one before it stay live. Course matching and decision sending work on both, so late decisions on the previous cycle can still be sent.
UCAS templates are generated by Full Fabric and locked: the card shows a Template locked label once the template exists, and the template, its documents, fields and sections cannot be edited. Evaluation settings on the template can still be changed.
Course Matching
Course Matching appears on an enabled scheme card. It lists every UCAS course that imported applicants chose, with the number of Applicants and a status:
| Status | Meaning |
|---|---|
| matched | The course is mapped to a programme and its choices have a class |
| partial | The course has a programme but its choices have no class |
| unmatched | No programme yet. An application is only submitted once at least one of its choices is matched. |
When both live cycles have templates, buttons above the table switch between them. Click Map on a row, or Add Mapping for a course not yet listed, then choose:
| Field | Notes |
|---|---|
| UCAS Course Code | Prefilled when mapping a listed course |
| UCAS Campus Code | Undergraduate only. Leave empty to match any campus of the course; an exact campus mapping takes priority. |
| Programme | Required |
| Class | Optional. Without one, Full Fabric picks a class when it imports the choice: the open class starting in the choice's entry year, else the only open class, else the programme's next available class. |
| Campus | Undergraduate only, optional |
For a course with applicants, Update N existing application(s) with this mapping (on by default) applies the mapping to the applications already imported and submits any that were waiting for a match. Unchecked, existing applications stay as they are and the mapping applies as UCAS sends applicants in later syncs. A course can only be mapped once per campus code in a cycle; a second mapping fails with A mapping for this course and campus code already exists.
Use the edit and remove icons on a mapped row to change it or remove it. Remove Course Mapping offers Clear programme assignment from N existing application(s) to remove the programme and class from imported applications. Conservatoires rows show the UCAS course attributes (Main, Joint, Secondary, Alternative, DBS, Full-time or Part-time) instead of campus columns.
When a new cycle starts, Full Fabric copies the previous cycle's mappings for courses UCAS still lists, moving each to the programme's class starting in the new year when there is exactly one, and leaving the class empty otherwise. Review the new cycle's table after rollover.
Decisions Sent to UCAS
Decision mappings on an enabled scheme card pairs journey states with UCAS decisions. When an imported applicant's journey in the class matched to one of their UCAS choices moves to a mapped state, Full Fabric sends the decision for that choice. Unmapped states send nothing, and with no rows the page shows No mappings configured. UCAS write-back is disabled.
| Scheme | Journey state | UCAS decision |
|---|---|---|
| UCAS Undergraduate | applicant::accepted |
U (unconditional offer) |
| UCAS Undergraduate | applicant::rejected |
REJ (reject) |
| UCAS Conservatoires | applicant::accepted |
GU (guaranteed unconditional offer) |
| UCAS Conservatoires | applicant::rejected |
REJ (reject) |
These defaults are added when a scheme is first enabled. Use + Add mapping, pick a Journey state (any state of your lifecycle's journey, see Lifecycle & Journeys) and a UCAS decision, then Save. Each state can be mapped once. U, REJ and GU are the only codes available: U and REJ are the Undergraduate codes, GU and REJ the Conservatoires ones.
- The first decision for a choice is sent as a new decision; later ones as an amendment.
- A decision equal to the last one sent is not sent again.
- Once U or GU has been sent, moving the applicant to a state mapped to REJ sends nothing, because UCAS does not allow that offer to be withdrawn this way.
- Only choices from the two live cycles, on an enabled scheme, are sent.
UCAS's own decision and the applicant's reply appear in the application's Choices document and refresh on each sync.
Permissions
Configuring UCAS (credentials, enabling, course mappings, decision mappings, Sync Now) requires Global integrations (core.institutions.global_integration_settings); see Integrations. Sending decisions needs no permission of its own: it follows any change of an imported applicant's journey state.