Messaging - Rich Text

We have updated our messaging functionality, so that messages can be sent as ‘Rich-Text’. This allows for text formatting, such as bullet points or headers, and links to be added into the messages.

Inputting and sending the rich-text message:

Viewing the message:

Learner Portal – End of Practical Period

We have added the Learners 'End of Practical Period Date' on to the Learners ‘My Learning Plans’ dashboard. 

Bug Fixes

In this release we have fixed the following bugs:

Learning outcome accordion - We have resolved a bug in the user interface where completing the learning outcome criteria for a unit, failed to update the overall unit completion status. For example a unit may have 2 learning outcomes within, each with 2 criteria respectively. When one of the learning outcomes is marked as 'Criteria completed 2 of 2' then the overall until count should update to 'LO completed 1 of 2.' Prior to this fix the UI would have displayed 'LO completed 0 of 2.'

The learning outcome completed count for each unit will now correctly represent the status of the completed learning outcomes within it. 

ACT end date set incorrectly for completed learners who have changed employer - When an apprenticeship standard learner in Bud, that has changed employer whilst on programme, is completed, the Date Applies To value for their ZPROG001 ACT record in the ILR is incorrectly set to their Learning Actual End Date, rather than their Achievement Date. This issue has now been resolved and the achievement date will be used to populate the ACT 'Date Applies To' field.

Unable to edit the ILR for OST learners due to '500 error' when a learner has been reassigned to another trainer - A bug has been identified, and now resolved, that may have resulted in users seeing a '500 error' when accessing an OST learners learning delivery tab within the ILR. This issue was only seen following the reassignment of a different training to that learner. 

IQA Samples corrupted - In some cases, if a corrupt or incompatible file was uploaded to an IQA Sample, the sample could no longer be accessed. Our resolution means incompatible or corrupted files will be caught on the upload and an error presented to the user.

Signatures resetting in the application edit flow - learners with a previous break in learning were sometimes seeing their signatures incorrectly resetting during the application edit flow.

Re-generating a Training Plan document incorrectly re-generating the Funding document - in some cases, generating a new Training Plan document using the 'Living Training Plan' feature were causing the Funding document to be regenerated too.

Business Intelligence - 18th March at 14:45

ILR Reconciliation Reports - Duplicate ULNs

We’ve made an improvement to the Duplicate ULN report within ILR Reconciliations to make the results more accurate and useful.

Previously, the report could flag duplicate ULNs even when the records existed in different ILR years. The report has now been updated so that duplicates are only identified when the same ULN appears within the same ILR year. 

Learner Insights

We’ve updated the learner insights in the learning plan to give you more accurate and actionable information.

Messages and submissions

Automated SCORM messages are no longer included in total message counts, helping you focus on the communications that matter. Meanwhile, SCORM submissions are now counted in the submission total, ensuring your reporting reflects actual learner activity.

Skills scans

We’ve refined the logic for skills scans during the first weeks of learning to better reflect enrolment activity.

• If a learner completed a skills scan at enrolment, for the first 12 weeks you’ll now see the message: 'Info: Learner is within 12 weeks of their start date. No on-programme skills scan is required yet.' This helps prevent unnecessary warnings early in the learning journey. If a subsequent skills scan exists, we’ll continue to use our existing calculations to measure progress.  
• For learners with an enrolment skills scan that are beyond 12 weeks with no subsequent skills scan, or for learners without any recorded skills scan from enrolment, a warning will appear: 'Warning: The learner does not have a recent skills scan' until a skills scan is completed. This ensures you’re alerted when learners need updated skills assessments, helping you maintain accurate learner progress tracking.

Standard Reports

Application missing signatures  

Applications with a status of 'Signed Up' that have had their Training Plan re-generated will now appear in the 'Applications Missing Signatures' report.  

This status has been added to the application status slicer but is deselected by default, so the report continues to focus on active enrolment activity. As with all other regenerated documents, you can include these applications by selecting 'Signed Up' in the slicer, giving you full visibility over all relevant documents and signatures.

Bug Fix - OTJH on Exempt activities

We’ve updated the 'OTJH Log in Standard Reports' to include exempt activities that still contain Off-the-Job Hours (OTJH), ensuring the hours shown align with those displayed in the learner’s Learning Plan.

A new slicer, 'Activity is exempt,' has been added so you can choose whether to include these activities. This is defaulted to 'No,' meaning the report will appear as it did previously unless you choose to include them.

We’ve also added a card showing the total approved hours for exempt activities, along with a new field in the report tables to help you review and manage any updates needed in learner's Learning Plans.

Bud Mark submissions

A new field, 'Marked with Bud Mark,' has been added to the 'All Activity Submissions' page in Standard Reports. This field will show True for any activity submission that has used Bud Mark, making it easier to track and monitor Bud Mark usage across your teams. 

Datawarehouse Fields

The following fields will be added to the DWH in this release