Special Programs 26.5.0.0

Integration Import Issues Panel

In this release, we’ve added a new “Import Layout Issues/Concerns” panel to Special Programs profile pages to make it easier to identify and troubleshoot data import problems from integrated systems.

When enabled, this panel:

• Surfaces import-related issues and concerns tied to the student’s profile import

• Presents messages in a clear, inline banner style consistent with other system messages

• Only appears when there are actual import concerns to review; if there are none, it does not display, keeping the page clean

To ensure stability and give districts control over rollout, this feature is currently managed via a feature flag and is off by default. When the flag is enabled, the system will begin storing and displaying import-row issues for profiles in the new panel. Existing behavior remains unchanged when the flag is disabled.

This improvement helps staff quickly see when data coming from your SIS or other integrated sources needs attention, reducing time spent tracking down import problems and improving data quality in student profiles.

Improved System Maintenance: Automatic Cleanup of Import Records

We've introduced an automated background process that periodically cleans up outdated profile import records. This maintenance runs during off-peak hours on weekends to minimize any impact on system performance.

What's changing:
Previously, import issue records associated with deleted profiles, profile types, or import layouts could accumulate over time, potentially affecting database performance. The system will now automatically detect and remove these orphaned records on a weekly basis.

What this means for you:

• Better performance – Routine cleanup of stale data helps keep the system running smoothly.

• No action required – This process runs automatically in the background with no configuration needed.

• Zero downtime – Cleanup is performed in small, controlled batches during weekend maintenance windows to ensure uninterrupted service.

Improved Performance for Large Report Exports

What changed:

The Data Collection Tool (DCT) now automatically processes large report exports in smaller batches, significantly improving reliability and performance when generating reports with large volumes of data.

Why it matters:

Previously, exporting very large reports could fail due to timeout errors, particularly when generating PDF output. This was most likely to occur during high-volume export scenarios, such as full account data exports. When a timeout occurred, all progress was lost and the export had to be restarted from scratch.

What's new:

• Automatic batching — The DCT now exports data in batches of 1,000 rows by default. This prevents timeouts and ensures that even the largest reports complete successfully without manual intervention.

• Faster exports — The DCT can now process and render one batch while simultaneously fetching the next, resulting in noticeably faster export times for large reports.

• No action required — Batching is enabled by default. No configuration changes are needed to take advantage of this improvement.

Additional details:

• To customize the batch size, use the /BATCHSIZE parameter (e.g., /BATCHSIZE:500). To disable batching, specify /BATCHSIZE:0.

• This improvement applies to DCT client exports. DCT Direct connections are unaffected, as they do not rely on web-based request handling.

• Fully backward compatible — older DCT clients and server versions will continue to work as before without batching.

PDF Export No Longer Loses Progress When Errors Occur

Previously, if an error occurred during PDF export, all progress was lost — meaning any documents that had already been successfully processed were discarded along with the ones that failed.

With this fix, PDF export now handles errors gracefully on both the server and client side:

• Errors no longer stop the entire export. If a specific document fails during PDF rendering, the export continues processing the remaining documents instead of halting completely.

• Failed documents are clearly identified. Any document that encounters an error during export will be flagged with an error detail column in the output, so you can easily see which documents succeeded and which need attention.

• Error details are included in the output file. The exported CSV will contain error information for any failed documents, making it straightforward to troubleshoot and re-process only the affected items.

Export Reconciliation: Row Count Monitoring (PS SIS Integration)

A new Alert Threshold setting is now available on the Data Connectivity Configuration page, giving administrators greater visibility into data alignment between PowerSchool SIS and PowerSchool Special Programs (PSSP).

What's new:

• A configurable Alert Threshold Percent field has been added to the export configuration page.

• The Data Connectivity Export page now displays row counts so you can compare the number of records in SIS against PSSP.

• When row counts deviate from your configured threshold, the counts are visually highlighted to call attention to potential data discrepancies.

How to use it:

1. Navigate to the Data Connectivity Configuration page.

2. Set the Alert Threshold Percent to your desired match percentage. For example, set it to 100 if your district requires a 100% match of records between PSSP and SIS.

3. On the Data Connectivity Export page, row counts that fall outside your threshold will be highlighted automatically.

Digital Signature: Pending Auto‑Acceptance Documents Report

The Digital Signature Auto‑Acceptance Activity report now includes a Pending auto‑acceptance view so district staff can see which documents are scheduled to be auto‑accepted and when.

• A new Pending auto‑acceptance option lists documents that are not yet accepted but are scheduled for auto‑acceptance based on the district’s Days Until Auto Acceptance setting.

• The report shows an Auto‑accepted Date for each document, calculated from the trigger date (for example, when all required signatures are completed) plus the number of days configured for auto‑acceptance.

• A new Auto‑Accepted Date filter and a Days entry field allow staff to refine results and preview different auto‑accept timelines (20–150 days); when auto‑acceptance is not yet enabled, the report uses 150 days by default.

• Access to this report follows existing Special Programs digital signature permissions and is available to staff with the Manage Digital Signature Documents privilege.

Digital Signature: Auto-acceptance/ Auto-voidance configuration

District administrators can configure digital signature auto-acceptance and auto-voidance at the district level.

• They control whether signatures auto-accept and set how many days before auto-acceptance.

• The default setting is off. Districts can select the number of calendar days before auto-acceptance, from 20 to 150, with 150 days as the default.

• The auto-voidance period is fixed at 160 days and cannot be changed.

Digital Signature: Upcoming Auto‑Void Documents Report

A new Digital Signature Auto‑Voidance Activity report helps districts proactively monitor documents that will be automatically voided based on the district’s Days Until Auto Acceptance setting.

• Lists documents that are scheduled to be auto‑voided, showing the Scheduled Auto‑Void Date calculated from the document’s trigger date (for example, when all required signatures are completed) plus the configured number of days.

• Allows staff to filter by date range, voidance status (Pending/Auto‑voided/Both), document type, student, and school/site, making it easier to focus on upcoming auto‑voids.

• Respects the district‑level Enable Digital Signature Auto‑Acceptance setting:

  • When auto‑acceptance is ON, eligible documents appear as Pending auto‑voidance until the scheduled date is reached.

  • When auto‑acceptance is later turned OFF, new documents no longer show as pending, but previously auto‑voided documents remain available in the report for historical and audit purposes.

• Follows existing Special Programs reporting permissions; for example, staff with the Manage Digital Signature Documents security privilege can access this report.

Merge staff profiles utility error resolved

Staff profiles can now be merged without triggering an error caused by a subquery returning multiple values, and this issue is now resolved.

Curriculum Statement Labels

The earlier issue related to Labels not getting inserted when curriculum statements were added has now been fixed.

Staff can create revision documents

Staff can create revisions for student documents accessed via the class roster, and the issue causing redirection to the home page with an error indicating they were not assigned to the class is now resolved.

Student profile merge error resolved

Errors caused by unique key constraints that prevented merging student profiles are now resolved.