07/10/2021: There is an issue with the daily refresh from OneFile related to a security based rate limit (the number of API requests per minute) with the OneFile API. This means that the daily sync process takes a lot longer than it needs to because we have to pause and wait for a minute every time we hit the limit. We are working with OneFile to resolve this issue so that the sync can happen in a reasonable amount of time.
The learner upload, where a learner is enrolled in OneFile from PICSWeb. This creates a learner record in OneFile with the necessary PICSWeb data, as well as OneFile records for qualifications, reviews, officers and organisations.
The automatic synchronisation, where progression and review data is pulled down from OneFile and imported back in to PICSWeb. This process happens automatically every day.
Once you have Enrolled a Learner with OneFile, the following details will be uploaded from PICSWeb to OneFile. Note that most of these details are not resent to OneFile when the refresh/synchronisation process runs.
The following details will be uploaded from the Learner Record to the corresponding OneFile learner record:
NiNo (National Insurance Number)
Planned End Date
Default Assessor – This field will use the learner’s Main Officer in PICSWeb.
Placement – This field will use the most recent placement of type P for the learner.
The following details will be uploaded for the Qualifications linked to the learner in their Delivery Plan. These details will only be uploaded for qualifications that are available in OneFile.
Review records will be created in OneFile based on the PICSWeb reviews scheduled for the learner. PICSWeb will only upload reviews that have the following details set:
The Type set to N (normal)
A Planned Date in the future
An Attended status set to Unknown
The following details will be uploaded from each review:
End Time – As there is no review duration capture in PICSWeb, this will be set to 1 hour after the Start Time.
Assessor – This field will use the Officer assigned to the review in the Review Summary. If no officer has been set, the field will instead use the learner’s Main Officer in PICSWeb.
Assessor records will also be created in OneFile from the Officers named in the learner upload. A OneFile user account will be made for each officer uploaded. The following officers will be uploaded from PICSWeb:
The learner’s Main Officer. This officer will be set as the Lead Assessor in OneFile.
The Assessor for each qualification linked to the learner, provided that they have not already been uploaded as the main officer for the learner.
The Officer assigned to each review linked to the learner, provided that they have not already been uploaded as the main officer for the learner.
No officer details apart from the Name will be included in the upload.
An Employer record will also be created for each learner based on the most recent Organisation that has been set as a placement of type P for the learner. If no placement is found with type P, then the most recent placement of any type will be used. No organisation details apart from the Name will be included in the upload.
PICSWeb automatically synchronises all OneFile learner details once a day. When this happens, the following details are updated in the PICSWeb learner record (the same data exchange also takes place when using the ‘Refresh with OneFile’ button):
The Total Elements and Elements Done for each qualification will be populated from OneFile data. As units are not meant to be used in the OneFile integration, any qualifications with units attached will be ignored during the update.
The Registration Number and Registration Date for each qualification. If either system has a value for these fields but the other doesn’t, the blank field will be updated. Where both systems have a value, the OneFile value will take priority.
The Certificate Applied ForDate for each qualification. If either system has a value for these fields but the other doesn’t, the blank field will be updated. Where both systems have a value, the OneFile value will take priority.
The Certificate Received Date for each qualification. If either system has a value for these fields but the other doesn’t, the blank field will be updated. Where both systems have a value, the OneFile value will take priority.
Any new Review Records created in PICSWeb will be uploaded to OneFile. This upload works in the same way as reviews in the learner upload explained above.
The Review Records for each OneFile learner will be updated with OneFile review data. This will either update matching reviews in PICSWeb or create new review records where a matching review cannot be found in PICSWeb. Matches are based on the unique OneFile review ID, which we add to the PICSWeb review data when it is uploaded.
Attended status is based on the review having an “Review Started” date in the API, this indicates that the review has actually taken place. If there is a date, we set the review attended as Yes, and set the actual date in PICSWeb. If there isn’t such a date, we set the status to Unknown, and ensure the actual date is blank.
If we can find a match for the OneFile assessor as an Officer in PICSWeb, we will assign this matched Officer to the review.
If the trainee has signed the review in OneFile, we set the Trainee Signed date in PICSWeb to this date.
Data values that may be sent from PICSWeb to OneFile by the synchronisation/refresh process:
Qualification Registration Date and Number,
Qualification Certificate Applied Date, and Certificate Received Date.
No further qualifications are sent from PICSWeb to OneFile by the synchronisation/refresh process.