Absence Reasons - PosiEd
- Jhetah Mae Leornas
- Mike French
- Darren Wright
The purpose of the Absence Reasons object is to provide a consistent structure for absence management and reporting. This extends to a variety of sections of PosiEd.
The options are available in both Internal and External Absence Submission forms.
The options are available in the Student Sign In/Out and Check In/Out Kiosks.
The reporting codes are used to generate government reporting.
The details are included in Academic Reports.
Used in notifying Parents and Carers and managing Attendance exceptions.
Please refer to the Data dictionary for technical details about each of the fields in this object.
The Attendance Rules pick list allows you to choose between multiple sets of Attendance Rules. This can be useful if in your Salesforce org you manage multiple school campuses in different states or jurisdictions. In such a case you should set up an Attendance Rules value for each of these jurisdictions and then define the various Absence Reason Codes and other details for each of those jurisdictions.
Once the configuration has been completed on each school account, you specify which attendance rules group applies to each school.
Absence Reasons’ Include in Academic Reports and Government Reports checkboxes
The Include in Academic Reports checkbox is used to indicate that if a student missed a day of school and there is an absence submission associated with that day with an absence reason that has this checkbox checked, then the student will be treated as though they were Present at school for the purposes of calculating the number of days absent in Academic Reports.
Include in Government Reporting performs a similar function but reflects in any government attendance reporting such as ACARA reporting.
The DPE jobs and any other tasks that calculate the number of days a student is absent should be adjusted to consider the "Include in Academic Reports" checkbox in the Absence Reasons.
In these cases, an absence submission should be created for the student, which will then be marked as absent during the roll call and the day attendance summary calculations. The reason code specified in the absence submission will be carried over to the day attendance record.
Once this process is completed, the calculation of days absent should reflect this scenario. Additionally, the ACARA report generation process should be modified to also take into account the "Include in Government Reporting" checkbox in the Absence Reasons object.
It is important to note that ACARA has clarified that an absence indicates that the student did not attend school at all. If a student attended school but missed less than two hours, this should be determined by checking the overlap of the absence submission—either created by the absence submission itself or by the Sign In and Sign Out processes. If the student missed less than two hours, they are still considered to be in full attendance. Conversely, if the student attended school at any point and missed more than two hours in a day, they are considered to have partial attendance.
According to ACARA, full attendance equals 1 school day, partial attendance equals 0.5 school days, and an absence equals 0 school days in attendance.
