Skip to main content
Skip table of contents

Enrollment 22.3.0.0

PowerSchool Enrollment version 22.3.0.0 is available as of 3/18/2022.

New Feature

FeatureDescription

Form Builder Access Post-Launch

Elements within the Form Builder can now be locked. When locked, the user’s ability to alter the element is further restricted than when the element is set to Restricted. The user is unable to delete a locked element or edit any functional behavior of the element (Field Name, Read-Only, list option Stored Values and Integration Values, Requirements, Visibility, etc.). However, the user can edit textual display attributes of the element (Label, Note, Help Text, translations, etc.).

PowerSchool Enrollment Support is responsible for setting an element as Locked or Restricted. After a form has launched for parent use, once Support has locked the appropriate elements within a form, the Form Builder can be made accessible to administrative users with the Configuration role. With this functional and process change, schools and districts can continue to have access to a form’s Form Builder post-launch, make minor changes to the form, and manage the form’s print templates.

Enhancements

Product AreaDescription

eSchoolPlus Has Web Access

PowerSchool Enrollment now integrates with the Has Web Access field in eSchoolPlus (reg_stu_contact.upd_stu_eo_info). Data from this field can be pre-populated into forms. PowerSchool Enrollment can write data to this field in eSchoolPlus as part of the standard data delivery workflow.

Integration with this field must be configured by PowerSchool Enrollment Support.

eSchoolPlus Residency Status

PowerSchool Enrollment now integrates with the Residency Status field in eSchoolPlus (reg_personal.residency_code). Data from this field can be pre-populated into forms. PowerSchool Enrollment can write data to this field in eSchoolPlus as part of the standard data delivery workflow.

Integration with this field must be configured by PowerSchool Enrollment Support.

eSchoolPlus Student Scope Contact Matching by Contact Type

A new “C & O Contact Types” Student Scope contact matching option is available within the eSchoolPlus API integration to locate potential contact matches differently based on the contact type within the relationship being sent from PowerSchool Enrollment to eSchoolPlus. The C & O option effectively behaves as if Student Scope is enabled when sending a C or O-type relationship but is disabled when sending a G-type relationship.

  • When matching a contact with a G-type relationship, matching considers every contact record in eSchoolPlus that has only G-type relationships. Any contact with at least one C or O-type relationship is not considered.
  • When matching a contact with a C or O-type relationship, matching considers only those contact records in eSchoolPlus that are already linked to the student that have only C or O-type relationships. Any contact with at least one G-type relationship is not considered.

The new option allows schools and districts to share parents and guardians (contacts with G-type relationships) between siblings within a family while ensuring that emergency contacts or other contacts (contacts with C or O-type relationships) are not shared at all.

The new option must be enabled by PowerSchool Enrollment Support.

Performance Improvements for Adding or Removing Existing AccountsThe performance of using the “Add/Remove Existing Accounts” dialog when managing form permissions has been improved.
Performance Improvements for Exporting RecordsThe performance of exporting data in the Roster and Submission Workspaces has been improved.

Unlink Old eSchoolPlus Relationships

A new “Unlink Old Relationships” option is available within the eSchoolPlus API integration to remove relationships between students and contacts that are not otherwise created or updated as part of the data delivery process.

If a contact has multiple relationships to the same student (for example, a G-type and C-type relationship), when the contact is updated via the API, the relationships connecting this contact to the student that are not sent from Enrollment are removed. For example, Enrollment would send a relationship of type G and remove a preexisting relationship of type C.

This new option must be enabled by PowerSchool Enrollment Support.

Resolved Issues

Product AreaDescription

Admin – Account Locked Message Not Displaying Properly

When an admin attempted to log into their account, the error message after four failed attempts displayed unformatted HTML. This issue was resolved.

Admin – Duplicate Records with Deliver Now

When a user double-clicked the Deliver Now icon in the Submission Workspace, duplicate student records were created in the SIS. This issue is now resolved.

Admin – Enhanced Matching Criteria with eSchoolPlus Not Including Extensions

When Enhanced Matching Criteria was enabled as part of the eSchoolPlus API integration, phone extensions were not included in the contact match criteria, resulting in a large number of potential contact matches based on phone number. This issue was resolved.

Admin – No Error Shown on Copied Element

When a user copied an element in the Form Builder that was locked by PowerSchool Support and attempted to close the editor without providing a new field name for the copied element, the editor could not be closed, but no validation message appeared. This issue was resolved.

Admin – Old Delivery Options Affecting Delivery with eSchoolPlus

When Simplified Matching was enabled as part of the eSchoolPlus API integration, some old integration configuration options unrelated to Simplified Matching were retained and affected the matching process as part of the data delivery workflow. This issue was resolved.

Admin – Performance Issues with Enhanced Matching for PowerSchool SIS

When Enhanced Matching Criteria was enabled as part of the PowerSchool SIS API integration and the user initiated the matching process for a student, unnecessary, additional calls made to the SIS to match contact records resulted in performance issues during the matching process. This issue has been addressed.

Admin – Auto-Tagging Rules Based on Document Fields Not Applying

In a Roster or Submission Workspace, when an admin either uploaded or deleted a document, tagging rules were not evaluated to automatically apply or remove tags. This issue is now resolved.

Family – Duplicate Records can be Submitted for the Same Form

When an action submission record was deleted while the submission record in the Submission Workspace was retained, the roster record’s status was reset to Notified/Not Started. This allowed the parent to submit the form again, resulting in two submission records for the one roster record. This issue has been resolved. Action submission records can no longer be deleted when there is an associated submission record.

Family – No Grade Value Displayed in School Locator Results Panel

In School Locator, when a school’s Low Grade value was the same as the High Grade value, nothing displayed for the Grades value in the School Locator results panel after a zoned school had been successfully located. This issue is now resolved.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.