A backend update concerning Nature of Action codes ensures document type and folder placement aligns with the associated form and action. This improves accuracy and consistency for HR Professionals when viewing and managing these documents in the system.
462420
Enhanced visibility of XML record number for providers. This additional information helps providers more easily identify, search for, and troubleshoot records that failed initial processing, improving efficiency during investigation and resolution of data feed issues.
495061
Removed the Help Improve This Site button from the Employee landing page for federal Employees, both Basic Users and HR Professionals who are employees and toggle to their Employee view. This change streamlines the interface and directs anyone using the Employee view to provide feedback directly through the eOPF Help Desk.
491777
Removed the Give Feedback option from the help menu (indicated by the “?” icon) that is available to all users. The menu now only displays ContacteOPF Help Desk and OPM Version#, clarifying how users can submit support requests.
Bugfixes
Item #
Description
468116
Fixed an issue in which users were unable to remove an Organization Code or Activity Code from an employment record. Although the system displayed a successful save message, the removed values were not actually cleared. Users can now successfully remove these fields and save the employment record as expected.
494070
Fixed an issue where the Description field was incorrectly required when editing an access template, even though it is optional during creation. Users can now save updates to an existing template without being forced to add a description.
494189
Fixed an issue in which changing a POID on an employment row did not display the correct error message when paired with an invalid Agency Subelement. The system now prevents the save and clearly displays an “Invalid POID/Agency Subelement combination” message. Error feedback is now visible to help users correct the issue.
455312
Fixed an issue in which creating access templates incorrectly triggered a “Duplicate Access Right” error when adding multiple records with different SSNs and no optional data entered. Users can now add multiple access records with unique SSNs without being blocked by an incorrect duplicate validation message.