Reduced Support Availability: 30th April - 1st May 2025

Just to let you know, our team is attending the Onefile all company meeting on 30th April to 1st May 2025, so we won't be as responsive as usual!

You can still access our help guides - just search the Help Centre to find the answers you need. Otherwise, you can submit a ticket and we'll get back to you as soon as possible. If you have an urgent issue, set the priority accordingly.

Eportfolio Mobile App Update

Our newest mobile app update is now available, grab your free download now!

Apple App Store ➡️ OneFile Eportfolio App on the App Store (apple.com)  version 1.0.27

Google Play Store ➡️ OneFile Eportfolio – Apps on Google Play   version 1.0.27


OneFile Eportfolio Software Update: Tuesday 29th April 2025

On Tuesday, we're updating OneFile Eportfolio, to introduce some enhancements and fixes.

Please ensure you are logged out of your Eportfolio account before 7am to prevent any data loss.

Release notes can be found here.


Help centre

Submit a ticket Log in

Software Update: Monday 18th March 2024

On Monday, we're updating RPL to introduce some fixes.  

Fixes

RPL

  • The application counter against the standards was calculating incorrectly. This has now been fixed and is showing the correct number of applicants per standard
  • There was an issue with Additional Costs at Applicant Level where it was not allowing the user to amend the values.
  • There was an issue that was stopping the ability to create a record for an existing applicant on a different standard with the same email address.
  • If the duration of the apprenticeship is less than 12 months after the RPL has been calculated, the reduction duration is shown as zero and a message is now displayed to explain that the duration can not be less than 12 months.
  • There was an issue with the rounding when the system was calculating the Min OTJ. This was causing the value to sometimes be 1hour less than the recommended.
  • There was an issue when creating new RPL accounts on the portal, it was not setting the client id field correctly. This was causing issues when the centres were trying to sync.

 

Login to post a comment