May 2026 eOPF Release Notes

We continue to implement automatic scrolling functionality in eOPF. Now HR Admin and Transfer users will experience an automatic scrolling feature when they open a document in the Review Folder For: [User] screen while initiating a transfer.

This new feature allows them to immediately view the document without manual scrolling.

524985

532197 

We have fine-tuned notification settings regarding access template creation and editing. Now, when either adding or editing access rows in an access template and checking the Excluded check box, HR Admin users will receive a banner notification to add an Org code, Activity code or SSN.

The banner notification will disappear when one or more of the required criteria for the exclusion are added, e.g. Org code, Activity code or SSN.

We have also enhanced notifications around duplicate access rows when creating and editing access templates.

Now, if HR Admin users add an access row with a POID and Select All selected for the Agency Subelement Code field to an access template, and an access row with the same POID and a specific Agency Subelement Code already exists in the template, HR Admin users will receive the following error message:

This Access Right already exists in the grid below.
Row [Numeral]
Edit or remove one or more of the [number] Access Right in order to proceed.

The same notification will trigger if an HR Admin user attempts to add an access row with a POID and a specific Agency Subelement Code, and the same POID with Select All selected for the Agency Subelement Code field is already present in the template.

We made access provisioning for employees more efficient by facilitating end date population into employee access.

Now, if employees whose employments have future end dates receive elevated permissions and access, the future end dates in employee employments will populate the Effective to fields in access rows.

Certain agencies have submitted SSNs via EDF as Employee IDs. The Employee ID field is not designed to mask part of the number in the way that the SSN field is. HR Professional users have reported that SSNs submitted as Employee IDs display unmasked (all numerals showing instead of just the last 4) in eOPF.

We have implemented a change prompting the system to scan for SSNs in EDFs and prevent SSNs from being received by and displayed in the Employee ID field in eOPF. The ICD is also being updated to advise agencies against submitting SSNs as Employee IDs via EDF.

534637

530693

Users were experiencing an issue in which the Data Feed Summary Report status would not update beyond Pending when users generated a report. We fixed the issue that was stalling the report.

Now when users generate a report, the Date processed field should update from Pending to a date and time as expected.

We were alerted to an issue in which records failed to reprocess and load new documents into a Gaining agency folder if an active employee did not have an email address in their profile,

We fixed the issue so that the FDF now finds the Gaining folder even if an email address is present in the employee’s folder.

We identified an issue in which HR Professional employments with elevated permissions were being reverted to Basic User profiles due to an EDF issue.

We have fixed that issue to prevent recurring loss of access.