Overview

In LearningBuilder, the term “Attendance” refers to records representing that a specific Practitioner has completed a specific learning activity, typically proctored by a Provider. Examples include attending a course, completing some computer based training, etc.

Technically speaking Attendance records are normal Activity Instances; the distinction is a business one, not a technical one. 

The following are frequently associated with Attendance:

• Activities are owned or created by Providers

• Staff members of those Providers log into LearningBuilder (as themselves) and use the Provider area to work on their parent Provider’s data

• When a Practitioner completes a learning activity, the Provider (or their staff) enters it through LearningBuilder on behalf of the Practitioner. These Activity Instances are considered “Provider verified” because they were entered by the Provider, not the Practitioner.

Technical Details

When adding the AI via the legacy attendance upload feature, LearningBuilder will look for an incomplete application with Cycle Dates where the completion date of the AI falls within. If there are multiple LPIs that match that criteria it will fail. If no incomplete LPIs are found it will look for completed LPIs and if none are found a new LPI will be started. The task group it is added to is the first task group that accepts that activity type, if none, uses the first task group at the top.

All Learning Plan definitions have a section for configuring Attendance rules. Dates for Attendance Upload allows users to define the range that will accept attendance. Options include Cycle Start / End and Reporting Start / End.

Limitations

The legacy attendance upload feature only reports 50 errors at a time. Therefore, if data is not scrubbed properly before import and you are importing large files it may be a tedious process to address the errors.

Ways of entering Attendance records