eSchoolPlus 20.4.37.0 Release

If a behavioral referral was added for a building in which the Disciplinarian does not have access, then the referral was not displayed on the Behavioral Referral page for the Disciplinarian. This has been resolved.

The BCE was creating receive marks with 'N'. It has been resolved to build state course with receive marks = 'R' if all local courses have session 1 receive marks = 'R'.

The Generate HAC Credentials option was creating invalid logins when generating based on name and the last name was only two characters long. This has been resolved by adding extra characters to the string if it is less than the required amount.

If a student had no discipline records, the HAC Student Support tab included the View Discipline by Year option when the HAC building configuration page was configured to just display current year records. This has been resolved.

HAC week view page was not loading for the scenario when the student’s buildings was using timetable period attendance and had only the default timetable with bell schedule as N/A. This issue has been resolved.

Attendance widget was including counts of substitutes who were inactive in the user’s building. This has been resolved.

Users were able to run the Honor Roll Calculation using the prompts on the Honor Roll Report page when the user had the security resource to run the Honor Roll Report, but not the resource to run the calculation. This has been fixed so the user needs to have security to access the Honor Roll Calculation to run it from the Honor Roll Report page.

If two users added and saved a Master Schedule record at the exact same time, it generated the same section key for both and one of the saves resulted in an error. This has been resolved.

Users were able to edit read only fields on a district-defined screen when the screen included fields that required different security resources and the user had read for one resource and read/write for another resource. This has been resolved.

When the scheduling status was changed on the request page, the data was not always saving. This has been resolved.