Bug Fixes
In this release, we have fixed the following bugs:
Forecast hours not reducing if activity marked for 0 hours: We have addressed a bug where an activity with a given amount of planned OTJH is marked to have taken 0 hours and the forecast hours amount does not change on the learning plan.
Risk of programme deletion when published programme is in “awaiting approval” state after editing: We have made changes to prevent programmes in 'Awaiting Approval' status from being deleted. Bud now only allows those in a “Draft” state to be deleted.
Display issues when confirming learning outcomes: Prior to this fix, a learner’s progression percentage could increases beyond 100% incrementally for each learning outcome that is confirmed. This is now capped at 100%. In addition, when confirming a learning outcome, the active tab would default back onto the functional skills tab. This is no longer the default behaviour.
OST applications 'IdentificationType' and 'DisabilityStatus' resetting to null values: We have addressed a UI issue where, in using the 'next' buttons to navigate through an OST applications, the ID type and Disability status field may be reset.
OST Applicant Archiving validation issues:
We have changed the behaviour of the OST applicant archiving process to correct the following issues that may have been present for some users:
- Operations Managers can no longer archive applicants without inputting anything into archive reason form.
- A failure banner is no longer displayed when an Operations Manager archives an applicant and the text box requirements are satisfied.
- If the "under 10 characters" validation is triggered, the archive process will no longer trigger automatically when the validation conditions are met
- OST applicants with the “Applicant Enrolment” status can now be archived without triggering an error message
OTJH calculation computes required hours based on timestamps: This issue primarily affected learners who are right on the “cusp” of a required hours bracket. It was possible that a small difference in their programme duration, caused by using the specific timestamps to calculate the programme duration could cause an unexpected required OTJH value. The calculation will now base the duration on whole days.
Apprentice Signature Box preventing compliance check: We have addressed a UI issue in the Application Summary document where, after the signature is collected, a snapshot is saved with a partial version of the signature modal stuck on the page obstructing other page elements.
Messaging Hub Page navigation: We have corrected a UI issue where users accessing the Messenger Hub may not be able to use page navigation, effectively rendering the message list stuck on pg1.
Scrollbar disappears when deleting a qualification during application self-enrolment: Prior to this bug fix there could be occasions when going through application self-enrolment, deleting a qualification from the “your existing qualifications” list will remove your ability to scroll that section.
Business Intelligence - 17th March 14:30
Standard Reports
In this release there are multiple small enhancements to the standard report suite:
- In-flight learners report now shows Last submission by Learner and Last submission by Trainer as separate fields as opposed to the singular Last submission date
- Current planned end of practical period and Current planned end date fields have been added to the below report pages. Please note these are the dates as it stands currently (ie when the learner began their break):
- Breaks
- Break Requested / Approved
- Break Return Requested
- Include in ILR slicer has been added to the All Activities Log
- All Reviews page now contains the following extra fields:
- Actual Duration Mins
- Cancelled date
- Cancelled reason
- OTJH Comments field has been added to the off the job hours log table in Off the Job Hours Log
- The previous column Withdrawal date has been replaced with Last activity date in the below areas to align with the new withdrawals process in change of circumstance
- All Withdrawals
- Withdrawal Requests and Approvals
- Rolling Withdrawals graph on Leavers Dashboard
Accountability Framework - Off-the-Job Hours
We have made changes to the Accountability Framework report to bring the OTJH metrics into alignment with the ESFA specification.
- The Planned hours vs Actual hours measure has been removed.
- A new metric flagging learners where their Actual OTJH are less than the Minimum Threshold has been added.
- A new metric flagging learners where their Planned OTJH are less than the Minimum Threshold has been added.
- Planned or actual hours equalling zero count is now combined, still calculating both but allowing you to quickly identify records which meet the At Risk category.
- Changes to the “At Risk” and “Needs Improvement” flags have been made as below:
- At risk: Any learners with 0 planned hours, 0 actual hours or 20 or more learners where the planned or actual hours are less than the minimum hours.
- Needs improvement: If 15 or more learners have planned hours less than minimum hours or 1 or more learners have actual hours less than minimum hours.
- Minimum Hours field has been added to the data table.
Management Reports
We have added the Predicted end date field to the drill-through tables in learning plan data.
Data Warehouse Fields
There are no new fields in this release.
Note for ETL and Report developers:
We are considering the removal of [Presentation].[Application (Dates)] in a future release, as this has for some time been superseded by [Presentation].[Application Status History].
Please contact your CSM if you think this would cause you any difficulties in your ETL or own reporting suite.
Coming Soon
We are currently working on a change to the signature collection method in Apprenticeship applications.
In order to provide the most compliance driven platform possible, we will in the near future be making changes to the Apprenticeship enrolment documents to bring them into line with other areas of the Bud platform. Having already updated the document signature components of OST enrolment and reviews, we will be rolling out the same signature capture method to the Apprenticeship application documents.
Training provider users will be able to request a Learner or Employer signature via email, or click to confirm the signature has been obtained offline.
To add a signature, users will type their signature and select one of two fonts.