Ecollect Forms/Enrollment Express 26.4.0.0

Admin - Improved Error Tracing with Logs

Previously, if a form contained an element linked to a PowerSchool field where the field length in PowerSchool was shorter than the length set in the form element properties—for example, a single-line text linked to a PowerSchool field with a length of 8 while the form element was set to 50—the system would error when an administrator tried to approve the response. The error shown in the error trace logs is now improved to help users identify which form element causes this issue by viewing the error trace log.

Admin - Form Sync

Previously, when an administrator imported a form via Form import in Manage forms or synchronized using Manage form templates, if a form file contained an incorrectly formatted scheduled publish start and/or end date, it corrupted the scheduled publish dates within the form created resulting in the form to not appear to responders such as parents, students, or teachers even when correct share permissions were applied. This has been resolved.

EEC-41933

Admin - Pre-Registration Emails

In rare cases, when an administrator configured enrollment emails within a pre-registration form, if the email body occasionally contained unsupported special characters, it caused the pre-registration email to fail to trigger or the email body to fail to load for editing later. This has been resolved.

EEC-41950

Admin - Edit Pending Responses

Previously, when “Edit Pending Responses” was enabled, if an administrator edited a form response containing a contact element, changed any data outside the contact element, and clicked Review and Approve, the form response would simply reload instead of opening the review contact window to approve the form. This has been resolved.

EEC-40068

Admin - Student Support Plan

Previously, when an administrator navigated to Student Forms and clicked the Student Support tab to add a new support plan without entering a valid Start Date or End Date, the system created the plan with invalid dates instead of preventing the creation of such an inactive, undated support plan. This has been resolved; users cannot create support plans without valid start and end dates.

EEC-41181

Admin - Form Submission

In some cases, form submissions failed to record when a form contained certain characters from right-to-left languages. This has been resolved by supporting proper encoding for unsupported characters.

EEC-41560

Admin - Customize Contact Element

When the system accidentally creates two entries for configuring the Customize contact element functionality instead of one, the required fields section in the contact element properties within the Form Builder becomes invisible, preventing correct configuration. This has been resolved, so the system will not create multiple entries for this configuration.

EEC-41536

Responder - Form Response

Occasionally, form submissions were allowed without selecting a required form element linked to FedEthnicity. This occurred because the FedEthnicity fields already had a value in PowerSchool SIS. As a result, the forms incorrectly considered the presence of a value in the PowerSchool SIS as the presence of a value on the form. This has been resolved.

EEC-18164

Admin - Form Builder

Occasionally, form submissions were allowed without selecting a required element when those elements were mapped to the same PowerSchool field as another element in the form. This has now been resolved.

EEC-13981

Admin - Reset Date

A defect was identified that caused the setting of a form with publish status Scheduled with the Reset Option set On Date to corrupt the reset date stored in the database. For example, storing a particular date as --2026-03- instead of a valid date. This corruption triggered errors with prefixes such as ORA-01862 on form listing pages and prevented forms and reports from loading properly.

To address this issue, the form editor's save functionality has been enhanced to prevent the incorrect date formatting that causes reset date corruption. Additionally, validation mechanisms will block the saving of invalid or partial reset dates. The system has been updated to repair and correctly display valid dates when loading forms with previously corrupted reset dates. Consequently, reset dates are now saved and loaded accurately. Administrators will also see an error if they attempt to save a reset date in an invalid format, prompting them to fix the issue.

Note: While this fix prevents the occurrence of new such errors, it does not automatically correct existing corrupted reset dates. For such a scenario, forms with corrupted reset dates will display a blank reset date field, requiring users to manually re-enter the correct date.

EEC-38912