Msite Verision V7.55 - Maintenance

New Features

  1. New setting added, Feature:Pre-registrationIncludeWorkforceAppLink. When enabled, all pre-reg invites to a site (excluding ‘No Access Control’ sites) will include a Workforce App code that workers can register with.
  2. Consent Audit Report now includes columns for showing consent to each of the three Biometric modalities used in MSite – Hand, Fingerprint, Face & ‘Yes’ or ‘No’ responses indicating whether consent was given for each or not.
  3. Consent Audit Report now includes ‘Most recent only’ checkbox, that when checked, hides all but the latest consent answer for each worker displayed in the report.
  4. Added the ability for worker notifications to send via Email as well as through the Workforce App. (Emails will only send to workers with a verified email on their profile.)
  5. Auto Grow Recipients checkbox added to the Add/Edit Accreditation Expiry Alert modal. Checkbox will be enabled by default and will be retrospectively enabled on all existing Accreditation Expiry alerts.
  6. New setting added, Feature:OnlineInductionsSCORMEnabled. When enabled, SCORM file upload features will be available in the Online Inductions course editor UI.
  7. Added the ability to upload SCORM files to Online Inductions.
  8. Custom Field Lookup endpoint added to the External API.
  9. Custom Field Group’ added to the Get, Add and Update Contractor endpoints on the External API.
  10. Overtime buffer added to the working rule configuration for Labour Hours.
  11. Added the ability to apply rounding to overtime on Labour Hours timesheets.
  12. ‘Discount time off site’ checkbox added to the working rules config. When checked, will allow worker timesheets to time off site between transactions throughout the day.
  13. Calculation of working rules now supports hours/activity on any site in a day. E.g. if a working rule stipulates that standard working rules for a site is 8hrs, but a worker works 4hrs on a previous site and 4hrs on another site, then the standard hours calculation in the working rule should be satisfied.
  14. ‘Prior hours from site’ row added to timesheets, this row will show hours that have been accumulated on a previous site. Where there are no hours that have been accumulated throughout the week from previous sites, then the row will be hidden.

Bug Fixes

  1. Fixed an issue whereby, Site Users were able to see contractors they were not associated to on all monolith reports.
  2. Fixed an issue whereby, the QR code for linking the Workforce App was not generating on the webpage.
  3. Fixed an issue whereby, Custom Fields added to the Visitor Custom Field group were not showing on the Visitor Management form on the Supervisor App.
  4. Fixed an issue whereby, the Site Orientation Report was not respecting UK browser culture and was showing induction dates in American format.
  5. Fixed an issue whereby, the ‘Invite’ button on the Training Accreditations section of the worker profile was incorrectly visible to site users who didn’t have the Worker Add/Edit role(s).
  6. Fixed an issue whereby, SJIB Accreditations were incorrectly having their certification numbers overwritten by the smartcheck validation service, SJIB cert numbers commonly end in -1 or -2, these were being removed and therefore causing the accreditations to be flagged as invalid by MSite.
  7. Fixed an issue whereby, the Worker Statistics Report was ignoring the ‘Apprentices Only’ filter option when selected and displaying incorrect data.
  8. Fixed an issue whereby, the ‘Randomise question selection’ within Online Inductions was not working correctly.
  9. Fixed an issue whereby, courses that were unpublished after an invite had been sent would still show in the worker pre-registration workflow. These should be hidden.
  10. Fixed an issue whereby, the Local Labour Breakdown Report CSV export was incorrectly showing the Worker ID and Bio ID as the same numeric value.
  11. Fixed an issue whereby, the Requisitioning user role was incorrectly allowing users to view Level 2 & 3 sensitivity custom fields. These fields should require users to have either the Worker view sensitive data user role and/or the visitor view sensitive data user role.

Was this article helpful?

0 out of 0 found this helpful