| Agenda Items |
---|
1 | Overview of the last three months: Tip |
---|
Last Quarter x Bugs fixed
🆕 x Feature Requests |
🛠️ Released Development in last 3 months |
2 | 🗺️ Roadmap Items:- |
3 | 👋 Welcome to new customers |
4 | Accolade |
5 | Points for Group Discussion |
6 | Changes around resits/retakes Removal of Capping on assessment resits. Employers decision should an Apprentice go back into further learning after failing an assessment, a discussion is held with the Apprentice / Employer to see what if any further training is required, this is not the decision of the EPA (Assessor)
Jira Legacy |
---|
server | System Jira |
---|
serverId | a2269739-3244-3b4d-bb8f-c582148d7bba |
---|
key | SD-9665 |
---|
|
|
7 | Validation on surname casing, such as McCarthy Currently the code will tidy up any issues with names entered for example like:- ”aNN aPPrentice” There has been a request to see what could be done where names have a “Son of” derivative (Mac, Mc or O') as the casing on the ROA appears with the single capital letter i.e. Mccarthy. The issue is if we remove the current code that tidies up casing, this would mean that you would need to tidy up every apprentice entry where the casing is incorrect manually?
Jira Legacy |
---|
server | System Jira |
---|
serverId | a2269739-3244-3b4d-bb8f-c582148d7bba |
---|
key | SD-7404 |
---|
|
|
8 | Integrated feedback forms for Assessment Results for Providers (relates to Jira Legacy |
---|
server | System Jira |
---|
serverId | a2269739-3244-3b4d-bb8f-c582148d7bba |
---|
key | SD-9502 |
---|
| ) Is this something customers use in addition to the fields in epaPRO? If yes, can you send us some examples of these please so we can see the level of detail you want? Would you ever move away from these forms that you currently use if we developed something within epaPRO to help us ascertain if the work would be utilised?
|
9 | Are customers using the Confirmed Toggle on the Planning Meetings? mentioned on SD-10286 Image Added
It was added to allow you to confirm the attendees at the time of the meeting being scheduled if known. These then appear on the Element Info list of attendees. We would like to know if anyone is using it as there is no other functionality linked to it and we are wondering if it should be removed? |
10 | Apprentice - Data Retention relates to SD-10068 Huge scale issue. Need to present a high level scale of issue and the problem How we anonymise - we will need to create a standardised process that all agree to and also the method of anonymising e.g. **** For dates we can use a date such as 01/01/1645 Ethnicity is a specified list, we cant null the entry.
Type of data to anonymise. Note the ULN number would need to go, we cannot replace that with a random number as there is a risk of the number actually matching another apprentice. We are not responsible for updating the data that third parties hold e.g. Aptem in linked systems (via API & Integrations) We cant anonymise data in attachments/files/recordings/Tasks/Notes etc. Anonymised records would need to be flagged in some way as locked down, to prevent editing as they would fail validation Cycling out of backups so could take 6 months or so to disappear from those areas Once its gone its gone for good and we cannot restore it
Questions for users How long the ESFA will hold data for certificate reprints? |