ATIPXpress Release Notes 26.2.2.0

Product Enhancements

Pre-Consultation Page Marking by Program Office  

#ID 1427065

You can now flag individual pages or page ranges for consultation directly from Document Management and assign them to one or more Program Offices before any consultation package is created. This pre-consultation staging makes it easy to build a consultation plan as you review records, then generate packages when you are ready. Page marks persist across sessions and across users (subject to permissions), so the same set of marked pages is available to anyone working on the request.

A page can be marked for multiple consultations with different recipients, and re-marking simply updates the existing set for the selected Program Office without affecting other rows. Marked pages are surfaced in the Review Log grid via a new Marked Pages column that shows a live count (or 0 Marked Pages), and Program Office rows display Marked / Unmarked badges.

To mark pages for consultation and assign them to a Program Office:

   1. Open the document in the Document Management from the Review Log. Right click on the folder or cabinet and select Mark for Consultation.

   2. Select the pages you want to flag. You can mark All pages, a specific Selection, or a Page List at the page or folder level.

   3. Choose one or more Program Offices from the list (sorted A–Z, with a real-time type-in search) and click Confirm Assignment. The pages are stored per Document + Program Office and the Program Office row shows a Marked badge.

   4. To remove marks, select the Program Office(s) and click Unmark Pages. A confirmation message appears at the bottom of the screen.

When you are ready to build a consultation package, open Edit Pages on the Program Office row.

Choose a selection mode in the Page Selection modal: All Selected Pages, Selection, Page List, or Only Marked Pages. The Selection Summary panel shows (X) pages from (Y) Document.

Save the package. The same modal is used to Add to an Existing Consultation, in which case pages are appended without overwriting or duplicating existing selections.

NOTE: Final Pages are calculated as Selected Pages filtered by Review Flag. If Final Pages is zero, Save and Create are blocked with a validation message. Once a consultation status is Sent, marking, un-marking, and page selection are locked.

Page Reference Code (PRC) for Consultation and RFD Pages

#ID 1438054

ATIPXpress now assigns a permanent, system-wide Page Reference Code (PRC) to every page of every document at the moment of ingestion. The PRC is unique across the entire system. The same code follows the page into every Consultation or RFD package it later appears in, which makes it easy for a Program Office reviewer to cite a page in their feedback and for an analyst to jump straight back to the exact source page.

PRCs are stored as AX-12345 (ATIPXpress), or CO-12345 (Collaboration Portal), and are displayed as PRC-AX-12345, or PRC-CO-12345. PRCs are generated for every ingestion pathway, including EDR, Document Management Module, Review Log uploads, Request Document uploads, and Collaboration Portal RFD-task uploads.

NOTE: Pages that were ingested before this feature shipped display Not Available in the same status bar position.

The Page Reference Code is displayed in the status bar of the viewer while reviewing a document. You can also look up a page by its PRC by entering valid PRC in either the stored form (AX-12345) or the display form (PRC-AX-12345) in the PRC Lookup widget. Click Find or press Enter. The viewer navigates directly to that page in the source document.

Annual Report Generation as a Background Job

#ID 1437763

The Annual Report is now generated asynchronously as a scheduler job rather than running inline on the application server. This change removes the performance and stability issues that large fiscal-year reports could cause during business hours, and lets you continue working in ATIPXpress while the report is processed. When the job completes, you can download the finished PDF from the standard Jobs view.

Alongside the move to a background job, the underlying report-generation logic and SQL queries have been refactored — inefficient loops, redundant method calls, and unnecessary in-memory data transformations have been removed, indexes and joins have been tuned, and high-cost query execution plans have been validated. Together these changes substantially reduce report runtime for customers with large data volumes, with no change to the report data itself.

Date Validation for Locked Annual Reporting Periods

I#ID 1437760

ATIPXpress now enforces fiscal-year (FY) annual-report locks on the date fields that determine which FY a request belongs to. Previously, the FY lock blocked create, close, and amend actions on requests inside a locked FY but did not prevent users from editing the underlying date fields — which could silently change the data behind an already-published annual report. With this change, any date edit that would move a request into or out of a locked FY is rejected at save.

The validation runs server-side at save commit and covers eight in-scope date fields: Received Date, Date Closed, Stop-the-Clock Start, Stop-the-Clock End, Appeal Received Date, Appeal Closed Date, Transfer Date, and Original Received Date. The save is rejected whenever the old date or the new date falls before the lock date of any locked FY. The check is all-or-nothing for the entire save; if any in-scope field violates the rule, no fields in the transaction are committed.

Faster page-count calculations across Request reports and correspondence templates

ID #1530206

The page-release counting logic that powers Request reports and page-count merge fields in correspondence has been performance-tuned, so reports and request close workflows that summarize page totals now load noticeably faster — particularly on environments with high request volumes or large page counts per request.

This optimization applies wherever ATIPXpress derives Pages Added to Case, Pages Reviewed, Pages Released, Total Pages, and Partial / Full / Non-Redacted counts.

Judicial Review Hold Warning and Auto-Exclusion at Delivery

#ID 1428987

This update introduces a new Related to Judicial Review checkbox on Document Review Flags and Document Review Status (unchecked by default). Judicial Review flags are protected from automated system overrides such as bulk status updates and auto-withheld logic; only authorized users can clear them manually. The Judicial Review flag is also hidden from the delivery configuration dropdown so it cannot be selected by mistake.

ATIPXpress now provides a safeguard that prevents documents marked as Related to Judicial Review from being released as part of a delivery package. When you attempt to deliver a package that contains any judicial review flagged items, the system displays a non-dismissible warning that lists the affected documents and pages.

If you Proceed, the flagged documents will be automatically excluded from the delivery package.

Bilingual Email Templates and Insert Fields in the Collaboration Portal

#ID 1438053

Agencies can now create and send fully bilingual (English & French) email templates from the Collaboration Portal, including bilingual insert fields that resolve in the recipient's selected portal language. When a Collab Portal user opens an email, it renders in their selected portal language, and any insert fields render bilingually using the configured translations.

To create a bilingual Collaboration Portal email template, navigate to Administration > System Configuration > Correspondence Templates > Email and open a new or existing template.

Enter the template Name and fill in Subject (EN) and Subject (FR). Both fields are mandatory. If the English and French subjects are identical, the system shows a warning prompt that you can acknowledge to continue.

Use the tabbed body editor to enter the English content on the EN tab and the French content on the FR tab, and save the template. Each tab retains its content independently.

Bilingual insert fields resolve automatically into the recipient's selected portal language at send time.

NOTE: Existing templates remain backward compatible. Templates with only English content display FR Missing in the grid; templates with only French content display EN Missing. The missing-language fields become mandatory the next time the template is edited. If a language is missing at send time, the email falls back to the available language.

Security Updates

We’ve made the following security updates in this version of ATIPXpress:

Bug Fixes

We’ve addressed the following bugs in this version of ATIPXpress: