Enrollment 26.9.0.0

Self-Service Data Targets

District Administrators with the Configuration role can now manage Data Targets directly in the customer admin portal. A Data Target defines how approved form submission data is prepared and delivered to a district's system of record. This release supports PowerSchool SIS, eSchoolPlus SIS, and file-based CSV and TAB deliveries.

Existing in-scope delivery configurations are available in the new experience without migration. District Administrators can create, update, and delete Data Targets, manage field mappings, and work with the settings that apply to their selected delivery type. This release changes where and how delivery configurations are managed, not the workflow for reviewing and delivering approved enrollment data. That process, including the delivery review experience, remains unchanged.

Access and prerequisites vary by integration type:

• Self-Service Data Targets is available to districts with a PowerSchool SIS, eSchoolPlus SIS, or file-based CSV/TAB delivery integration. District Admins must have the Configuration role to access and manage Data Targets.

• PowerSchool SIS customers using SIS extensions can use the PowerSchool SIS 26.9 PowerQuery to automatically synchronize extension table and extension group metadata, helping keep available mapping options aligned with their SIS configuration.

• For eSchoolPlus customers, Simplified Match Logic must be enabled before an eSchoolPlus Data Target can be opened. When needed, the application guides an eligible administrator through enabling this setting.

For PowerSchool SIS Data Targets, Sync & Validate refreshes available SIS tables, columns, and extension metadata, then checks the full configuration for issues that could affect delivery. A sync occurs automatically when creating a PowerSchool SIS Data Target or changing its SIS connection, and administrators can run Sync & Validate at any time to refresh metadata or verify a configuration. Sync results help ensure that available mapping destinations reflect the district's current PowerSchool SIS configuration and identify issues before they affect delivery.

To help ensure every delivery has what it needs, Data Targets enforce the minimum fields required for the selected delivery type. When you open a Data Target, any required fields that are missing are added automatically, and required fields are protected from deletion. Fields that must exist for delivery are shown as read-only, so administrators can see exactly which mappings are required while remaining free to configure the rest.

Field mappings give administrators control over how enrollment form data is prepared for delivery:

• Basic mappings send one source value to one destination field. For example, a district can map the Preferred Name field on an enrollment form to its preferred-name field in PowerSchool SIS.

• Advanced mappings support more complex values that draw from multiple form fields or system properties. For example, a district can combine separate address fields into the value required by a destination field.

• Conditional mappings send one value when a defined condition is met and another value when it is not. For example, a district can deliver a mailing address when it is provided, or otherwise use the student's primary address.

Transformations can further prepare a value before delivery and support common needs such as trimming, replacing, splitting, padding, and formatting values.

Integration types other than PowerSchool SIS, eSchoolPlus SIS, and file-based CSV/TAB continue to use the existing configuration process and are not managed through Self-Service Data Targets in this release.

Self-Service Form Validators

District Administrators with the Configuration role can now create, edit, and manage form validation rules directly within the Form Builder, without needing to contact Support.

Six pre-built validator templates are available:

• Validate Age — Enforce age/grade eligibility cutoff rules

• Validate At Least One — Require at least one field in a group to be completed

• Validate Checkbox Count — Enforce a minimum and/or maximum number of checkbox selections

• Validate Contact Priority — Ensure contact priority numbering is sequential and unique

• Validate Match — Require multiple fields to have matching values (e.g., email confirmation)

• Validate Uniqueness — Require multiple fields to have unique values (e.g., school choice rankings)

A Custom Validation option with a guided expression builder is also available for use cases not covered by templates.

Automatic Migration: When opening the Form Builder, existing legacy validators are automatically migrated to the self-service format when a safe conversion is possible. Validators that cannot be automatically migrated remain as read-only legacy elements.

Additional capabilities:

• Typeahead search in field-mapping dropdowns for large forms

• Validation message translation support for non-English languages

• Preview and publish validation to catch configuration errors before deployment

• CSV Form Definition upload validation with detailed error messages

• Full support across Public, Restricted, Private, and YRUv2 form types

• Form cloning preserves self-service validators

Parent - Unable to Add Recommendation or Transcript Request Forms

In some Recommendation configuration scenarios, when a parent selected a recommendation or transcript request form and clicked Continue, the form was not added to the family’s recommendation account, and the message “The Page Requested Is Unavailable” was displayed. The selected forms have been added successfully, and the parent is redirected to the request dashboard. This has been resolved.

Parent - Form Name Displayed in English When Haitian Creole Was Selected

When a parent selected Haitian Creole in the Family Portal, the form name was displayed in English instead of Haitian Creole. Updated the translated form name to display correctly. This has been resolved.

Parent - School Locator Did Not Recognize Some Ordinal Street Addresses

When a parent entered an address where the house number also appeared in the street name, such as 7 7th Street, School Locator could misread the street name and fail to identify the correct zoned school. This has been resolved.

Parent - Year-Round Update Forms Displayed Unintended Fields

When a Year-Round Update form was linked to a single-page form, parents were shown all fields instead of only those configured for the update. Updated the Year-Round Update forms to display only the intended fields, consistent with multi-page forms. This has been resolved.

Admin - Custom Colors Could Not Be Applied in the Rich Text Editor

When an administrator selected a custom text or background color in the rich text editor, the color could not be applied or retained after refreshing the page. Updated the Custom color processing to select and save correctly. This has been resolved.

Admin - Online Decision Custom View Filtering and Sorting Did Not Work

When an administrator filtered or sorted the Online Decision roster using a custom view column, the expected records were not displayed in the correct order. Updated the Custom view columns to be filtered and sorted correctly. This has been resolved.

Admin - Submission Comparison Report Displayed Incorrect Form Selection Error

When an administrator selected two or more forms for a Submission Comparison Report, an error incorrectly stated that at least two forms must be selected. Updated the message to appear only when fewer than two forms are selected. This has been resolved.

Admin - Removed List Assignments Missing From All Students View

When a student was removed from a program outside their original choices, the removed list assignment did not appear in the School Choice Workspace All Students view or CSV export. Updated the removed list assignments to remain visible and export correctly, allowing administrators to review a student’s complete assignment history. This has been resolved.

Admin - Filtered Workspace Views With User Account Email Address Failed to Load

When a Submission Workspace or Roster Workspace view included the User Account Email Address column, applying a tag or form field filter caused the view to fail to load. This has been resolved.

Admin - School Choice Notification Email Contained Outdated Portal Address

School Choice notification emails displayed the outdated my.infosnap.com address. Updated these emails to include a clickable PowerSchool Enrollment Portal link that directs administrators to the correct site. This has been resolved.

Admin - Recovered Submission Records Missing Approval History Entry

When a discarded submission record was recovered, its reset to Pending Approval was not recorded in Approval History. Updated the reset and administrator details to appear in Edit Details and applicable exports. This has been resolved.

Admin - School Locator Element Could Not Be Closed in Form Builder

When an administrator edited a School Locator element, selecting Close or selecting the Edit icon again did not close the element if hidden required fields were empty. Updated the Hidden fields to no longer block the element from closing, while visible required fields continue to be validated. This has been resolved.

Admin - Contact Name Mismatch Reported for Siblings Sharing a Contact

When multiple siblings sharing the same contact were delivered together to eSchoolPlus, a Contact First and/or Last Name Mismatch error could be reported even though the contact names matched. Updated Shared contacts to be recognized correctly while genuine name mismatches continue to be identified. This has been resolved.

Admin - Roster Workspace Available for Public and Restricted Forms

When the Roster Workspace was enabled, District Administrators could access roster details for Public or Restricted forms. Updated the Roster Workspace access to be limited to Private forms. This has been resolved.