Integrations
BETA Only applicable to institutions using the BETA release. Note that BETA documentation may be incomplete or contain errors.
The new and updated features for the 4.47 release are as follows:
Header | Business Impact | Affected Topics |
---|---|---|
UCAS Integration updated to handle multiple intakes within a single year |
A new institution setting has been added to the UCAS area UCAS HE Course matching uses Month of Entry. This setting is shipped with a default value of No to retain existing matching behaviour by default. When set to Yes, when considering which UCAS courses match ebs courses, as well as course code, year and optionally campus, the start date month will also be matched to the month of entry. This allows two course occurrences to be defined with the same UCAS Course code, but starting in January and September. |
UCAS HE Institution Settings |
UCAS application year is updated when a UIO is rolled forward |
When a course occurrence is rolled forward, if the UCAS application year is populated, then this will be incremented by one. For example, if the source UIO has a UCAS application year of 24, that is an entry year of 2024, the target UIO will automatically set the UCAS application year to 25. |
Not applicable |
UCAS Support for 3 digit HESA Ethnicity codes |
As part of the UCAS 2026 specification changes, 3 character HESA Ethnicity codes have been added to the UCAS Ethnicity reference data, and the UCAS integration modified to handle the longer codes. |
Not applicable |
Description column for UCAS reference data |
An ebs Description column has been added to the UCAS verifiers reference data screens to make it easier to identify which UCAS codes are currently mapped to active ebs codes. |
Not applicable |