March 2026 Release Notes

ALLOVUE-3340

Roles have hidden/display/plan permission for SEs

Supplemental Expenses (SE) now respect budget user-role access levels (Hide / Display / Plan). Users will only see SE navigation, tabs, widgets, exports, and edit actions when their role allows it. When access is restricted, SE amounts are hidden/redacted, and SE-specific actions/buttons are removed.

Notes:

• Also includes updates for Personnel Expenses (PE) in the Budget Overview allocation table that were missed in earlier related work.

ALLOVUE-3338

Non-Personnel Expenses (NPEs) now respect budget user-role access levels (Hide / Display / Plan). Users will only see NPE navigation, tabs, widgets, exports, and edit actions when their role allows it. When access is restricted, NPE amounts are hidden/redacted, and NPE-specific actions/buttons are removed.

ALLOVUE-4130

Display Approver Step/Name for Proposals Awaiting Approval

On the Budget Proposals page, proposals that are awaiting approval now display an additional tag indicating which role is next in the approval workflow (other proposal statuses do not show this tag).

ALLOVUE-3844

Prevent Archiving Pays and Benefits Elements When There are Active P&B Proposals

In Pays & Benefits configuration, users can no longer archive pay/benefit setup items (Vacant Job Pays, Employee Benefits, Pay Schedules (and related details), and Benefit Packages) if those items are being changed in an active Pays & Benefits proposal (Draft or Awaiting Approval). Users will see a message explaining the item can’t be archived until active proposals are submitted/approved.

ALLOVUE-4222

Remove the "how many digits" validations for FTE in New Positions/Edit Positions Form

FTE fields across the application no longer enforce a browser “step” precision (previously effectively limiting entry to 0.01 increments). Users can now enter any decimal precision for FTE values (for example, 0.123 or 0.99999) while existing range validations (such as > 0 and ≤ 1 where applicable) remain unchanged.

ALLOVUE-4220

Account history reporting issue.

Fixed an issue in Reporting → Account History export where the “Planned” column could be labeled and populated for the wrong fiscal year (shifting year columns by one). The export now correctly uses the scenario’s fiscal year for the Planned column and aligns historical Budget/Spent columns with the correct years.