Software Update: Thursday 29th May 2025 7am to 7:30am

On Thursday, we're updating Onefile Eportfolio and OneFile Enrol, to introduce some new enhancements and fixes. 

Eportfolio

Enhancements

Activity Log

A record is now added to the activity log when a learner's episode start date is modified.

Amendments to a timesheet record are now logged in the learner's activity log.

Delivery Plans

A new column, Last Locked Delivery Plan is now available in the Learner View Database report. This column shows the date of the learner's last locked delivery plan.

Visits

The visit columns within the learner view database report now include visits linked to register sessions.

Unit Summary

Validation warnings when signing a Unit Summary are now also displayed at the bottom of the page.

Learner Portfolio Forms

Learner Portfolio forms signatory dropdowns are now displayed in alphabetical order.

Data Exports

A new export is now available for the Review Magic Link data. This export can be made available on request.

Bug Fixes

• An error occurs in the learning journal when linking criteria to a new journal entry.
• Files added to a persistent custom data form are not retained once the assessor signs the review form.
• Pressing to add a new row on a data field table of a custom form is causing scroll issues.

Enrol

New Features

Form Packs

You can now create form packs—collections of forms grouped together and sent in sequence. Each form follows its own workflow, and recipients will receive them one after another. This new feature is designed to streamline your processes and help you save time.

Enhancements

Optional Employer Record Fields

We've made the employer identifier and the second line of the address optional in employer records. This means you only need to fill in the necessary details before the record status updates to “Complete.”

Bug fixes

Optional Fields Now Behave Correctly

We resolved an issue where pre-populated fields couldn't be set as optional when required. These fields now behave as expected.

Hidden Fields No Longer Cause Errors

Previously, hidden (sensitive) fields caused errors when a form was sent back to a recipient for corrections. This has now been fixed, and those forms should function properly moving forward.

Please note that these changes are not guaranteed to be included in this update. Any changes to the planned updates listed above will be communicated in this thread.

If you have any questions, please submit a ticket to our team.