#10382 [Expense Agent] Fix administrative recall history access
Expense Report recall authorization is now restricted to the submitter or users with Unlimited Expense Approval, and non-submitter recalls are recorded as administrative activity outside the approval history.
- 3files
- 2AL files
- 2objects
Pull request · merged into main (BC30) on 2026-08-20 by t-prda · 3 files (+214 -5), 2 AL · feature · tier official · reviewed (checked by Opus)
What changed
- Only the captured submitter or a user with Unlimited Expense Approval can recall a pending expense report
- Recalls by someone other than the submitter are logged as BC User activity with a new Administrator role
- Administrative activity is kept out of submitter and approver history
- Tests cover genuine submitter, mapped and unmapped administrator, and unauthorized recall scenarios
- Behaviour changes for users or extensions.
AL objects touched
- Enum 6924 “Expense Activity Actor Role”, ExpenseAgent: modified
- Codeunit 6901 “Expense Report Approval Mgmt”, ExpenseAgent: modified
Context
- Work items: AB#647041
- Labels: AL: Apps (W1), Ownership: Manual, Team: Finance
- Systems: development
- From the description: “authorize pending expense report recall only for the captured submitter or a user with Unlimited Expense Approval”
Source: metadata of a merged pull request in microsoft/BCApps (bcapps): title, labels, changed paths and counts, with a summary in our words. No source text and no description beyond one short quote (D10, D61).