MyProgress 8.6 Release Notes

QR Code Generation on App

Following customer feedback, regarding Practice Staff being able to give feedback on students "in the moment" and that students are increasingly becoming uncomfortable giving their devices to a member of Practice to complete a response, we have added a new feature to the app; for forms using the "email for later" workflow.

When sending a draft, via the app, when the student clicks on the "Email for Later" option, they will then be presented with an optional QR code. The Practice Staff partner can then use their own device to scan and access the draft in real time, no need to log in - this process does not replace the email going to the Practice Staff partner, it can be used as well as or instead of the QR code.

Also, within the app, if the student has generated a draft as "Email for Later", they can also re-generate the QR code, if a response has not been submitted.

Note - The QR code is only generated for drafts via the app; not via the web.

Administration Enhancements

i) Program Instances - The Program Instance page currently includes, by default, all Instances - now any live and draft Instances will show by default and any archived Instances must be chosen from the filters to appear. Guide: Program Instances

ii) Progress View Report - The addition of a "assignment" filter box enhances the report, to be able to filter out unrequired deployments, rather than reporting on all currently. Guide: Progress View Report

iii) Progress View Report - The addition of a "simple" report extract has been added, as an option - this offers a reduced snapshot of specific user data. Guide: Progress View Report

iv) Groups - Administrators will now be able to add themselves to groups; where this was not possible before.

v) Groups - Following feedback, the "group type" field is now mandatory on imports. Guide: Managing Groups

General Useability and Performance

i) OTJ Hours - If a student/trainee doesn't have an Apprenticeship Record, the OTJ Hours column will not appear on the Dashboard. This is an issue prior to 8.6, as when OTJ is used - the dashboards default to include the OTJ Hours column for every student/trainee.

ii) Reporting - Further to the success and positive feedback, of removing the "Users" filter in our Timesheet Report in 8.5; we have further expanded this to all of our standard reports, which previously included the "Users" filter, to enhance the performance of reporting.

iii) Response Times - To further support issues on response times, when submitting a response it will record against the server time and not the time in the users browser. This is to help prevent potential fraudulent submission times and help with time zone accuracy.

iv) App - Currently any pre-mapped/linked proficiencies/framework items, for Progress Views are not maintained if the response is submitted via the app. We have now developed the app, so any pre-mapped framework items remain linked to the response.

v) Timesheets - When using the "allow hours outside of placement dates" option on Program Instances, it was developed to allow users to enter future dates. This has been updated, following feedback and users cannot now enter future dates.

vi) App - Following feedback, we have updated the timesheet entry options in the app, allowing students to enter minutes individually, rather than in increments of 15.

Bug Fixes / Other

i) Duplicate Timesheet Warning - When the red "toast" warning appears and a duplicate timesheet record is not going to be submitted, we will change the error "This is a duplicate of a previously submitted record. Please check the details." to "This is a duplicate of a previous record. It has not been submitted. Please check the details."

ii) Reporting - There is a delay in ad-hoc responses, verified timesheets and/or deleted timesheet statuses being sent to the reporting database. We have re-written some underlying code to improve the robustness of this process.

iii) Persisted Responses - Following Version 8.5, an issue was identified which meant that pre-existing drafts didn't have their persisted reference updated, so when persisting to new drafts, post release, the data did not carry through. We have fixed ad-hoc since, but this will fix all existing drafts created at the time of the Version 8.5 release.

iv) Dashboard - Currently there is no logic around the ordering of instances on the Dashboard - when students have multiple Program Instances; we have updated this to show the order by date - active status first, then by most recent start date, with expired Program Instances listed last.