Enrollment 24.10.0.0
PowerSchool Enrollment version 24.10.0.0 is available as of 10/18/2024.
Enhancements
Product Area | Description |
---|---|
Expanded Support for PowerSchool SIS PersonAddress Table | Data can be imported from and delivered to the COUNTYCODESETID, VERIFICATION, ISVERIFIED, ADDRESSLINE3, ADDRESSLINE4, and ADDRESSLINE5 columns within the PersonAddress table in PowerSchool SIS. Requires PowerSchool SIS v24.9.0.0+. |
Permissions-Policy HTTP Header | A |
Referrer-Policy HTTP Header | A |
schoolrecs Pages Reflect Correct Email Address | The Recommendation Requests' Submission Confirmation page and the Contact Us page within schoolrecs list noreply@schoolrecs.com as the email address used to send schoolrecs related emails to parents and recommenders. |
X-Content-Type-Options HTTP Header | An |
Resolved Issues
Product Area | Description |
---|---|
Admin - Creating Data Delivery Batch when Submission Workspace Matching Used | If Submission Workspace Matching was enabled and the Primary Student configured with a defined delivery schema, when users attempted to create a delivery batch as part of a standard data delivery workflow, the correct data delivery configuration was not being identified, resulting in an error. This has been resolved. |
Admin - Error Sorting and Searching in Submission and School Choice Workspace | Sorting and searching by PROP:SubmissionRecordID in the Submission Workspace and by PROP:SubmissionDateTime in the School Choice Workspace resulted in an Invalid View or Filter configuration error. This has been resolved. |
Admin - Error Sorting in Roster Workspace | Sorting by PROP:EmailNotificationValidationErrors and PROP:LetterNotificationValidationErrors in the Roster Workspace resulted in an Invalid View or Filter configuration error. This has been resolved. |
Admin - Re-Delivery of PowerSchool SIS One-to-Many Auto Schemas | When attempting to deliver data to PowerSchool SIS using One-to-Many Auto delivery schemas in multiple attempts within the same data delivery workflow, an error occurred on subsequent attempts due to preserved matches with records that no longer existed. This has been resolved. |
Admin - Year-Round Update Field Value Change Detection | When a Year-Round Update was configured to require review when certain field values were changed, unpopulated text- and list-based field types were not identified as "changed" when a value was provided. Similarly, checkbox field types pre-populated with a checked value were not identified as "changed" when unchecked. These scenarios resulted in the automatic delivery of form submissions to the SIS without an opportunity for review. This has been resolved. |