Product Enhancements
Dedicated Document Management OCR Job
FOIAXpress now runs a dedicated OCR job for Document Management. When you add Pages to a Document Management Folder, OCR starts on the new Pages automatically to make them searchable — no manual step is required.
Previously, a single system job processed both Correspondence OCR and Document Management OCR, so a large volume of Pages could delay Correspondence OCR, Find and Redact, and AI-assisted redaction for everyone. The two now run independently.
A separate job is created for each Folder, so Pages in different Folders are processed at the same time. Job status shows live progress — for example, OCR Processing 8 of 73. A completion email lists the Folder name and the document, page, and reason for each failed Page. A job is marked Completed even when some Pages fail, and Failed only if the entire job fails. OCR errors never roll back a document upload.
To track a Document Management OCR job:
Navigate to Document Management and add Pages to a Folder. FOIAXpress starts the OCR job automatically.
Go to My Jobs to review the job and its live progress.
Go to Failed OCR Jobs to reprocess any Pages that did not complete.
NOTE: Pages that you set an OCR Priority for are processed by the OCR system job rather than by the automatic Document Management OCR job. If OCR is removed from the Scheduler Configuration, new Pages remain Pending in My Jobs until OCR is configured again.
Login.gov Verification Failure Page Enhancements
The Login.gov Verification Failure Page message now includes updated default body content aligned with current compliance requirements. The template is pre-populated with agency-configurable placeholders for help desk, agency, portal, contact, and website information, allowing administrators to customize the content before publishing.
.png?sv=2026-02-06&spr=https&st=2026-09-06T15%3A42%3A19Z&se=2026-09-06T15%3A56%3A19Z&sr=c&sp=r&sig=aU7ENK%2B4FzjRNXifwzEsTr8D77tWILfnhv8zBTdtZjI%3D)
1. In PAL Config, navigate to Messages.
2. Select the Login.gov Verification Failure Page message type.
Review and update the pre-populated body content with your agency-specific information.
3. Save and publish the updated content.
The portal-facing verification failure page displays the configured content exactly as published, ensuring a consistent experience for requesters during identity verification failures.
Page Count for Packages Delivered to FOIAXpress
When you send documents from Casepoint to FOIAXpress through Export Documents or Produce for FOIA, Casepoint now delivers the total page count with the package. You can confirm how many pages were received without opening the package, and no additional action is required to display the count..png?sv=2026-02-06&spr=https&st=2026-09-06T15%3A42%3A19Z&se=2026-09-06T15%3A56%3A19Z&sr=c&sp=r&sig=aU7ENK%2B4FzjRNXifwzEsTr8D77tWILfnhv8zBTdtZjI%3D)
After the import job completes, review the page count in FOIAXpress to verify the exported or produced documents. For an export set, open the eDiscovery tab in the associated FOIAXpress request and check the Page Count column. For a Produce for FOIA package created with the production type set to Image, open Request Folder > Documents in the FOIAXpress request after the package is received and review the Pages column.
The total is the combined number of PDF pages across every image-converted document in the package. Documents that have not been converted to image, audio and video files, load files, metadata files, and the package file itself are excluded from the total. If a package contains no image-converted documents, the count is 0, and when the production type is not Image, no page count is sent, and the column remains unchanged.
The page count applies to packages transferred after this release. Packages delivered earlier, and any correspondence or reports already generated from them are not updated retroactively. All other behaviors of the Export Documents and Produce for FOIA flows remain unchanged.
Security Updates
We’ve made the following security update in this version of FOIAXpress:
ID | Description |
|---|---|
1589751 | Addressed a SQL injection vulnerability, identified during a vulnerability assessment, in the reference value used when the application checks for duplicate and linked requests. |
1593932 | Upgraded AngleSharp and Microsoft.Kiota.Abstractions to remediate security vulnerabilities in the third-party components. |
Bug Fixes
We’ve addressed the following bugs in this version of FOIAXpress:
ID | Description |
|---|---|
1338606 | Fixed an issue where redaction codes applied through Find and Redact were misaligned on pages that had been rotated left, right, or 180 degrees. |
1534282 | Addressed an error that prevented new Review Statuses, Alerts, and Notes from being created once a large number of records already existed. |
1560697 | Fixed an issue where Request for Documents records of the Prudential Search Request and Investigation request types were not created automatically in eRecords. |
1587585 | Resolved an error where two entries in the month drop-down menu of the User Logins custom report were labeled "March.Text" and "April.Text" instead of the month names. |
1587935 | Fixed an issue where header, footer, and page number text appeared smaller on redacted pages than on non-redacted pages in generated documents. |
1588150 | Fixed an issue where the "As of" date filter for Request Status in the Request for Documents report did not filter results by the selected date, so the report included requests opened after that date. |
1590460 | Resolved an issue where the Request for Documents list stretched beyond the page and its scroll bar did not work. |
1591621 | Fixed an issue where the Request Type field became read-only as soon as a file was added to the request description attachment, before the request was saved. |
1593473 | Addressed an error that prevented the Create Request page from loading after a new requester was created. |