#11628 Expense Agent: capture submission policy evaluation history
Expense Agent now captures policy evaluation history at the report level, storing outcomes and flagged categories in the activity log during submission and resubmission with deduplication per submission round.
- 10files
- 7AL files
- 7objects
Pull request · merged into main (BC30) on 2026-10-01 by t-prda · 10 files (+1690 -30), 7 AL · feature · tier official · reviewed (checked by Opus)
What changed
- Report-level policy evaluation summaries are added to expense activity history
- Submission, resubmission and successful line evaluation confirmation invoke the history logger
- At most one PolicyEvaluated entry is written per submission round, only when policy evaluation is enabled and the report is pending approval
- Entries store the outcome, passed/failed counts and distinct flagged category codes, with a final ‘…’ entry on overflow
- Snapshots are exposed through the existing read-only activity API and preserved through posting
- Behaviour changes for users or extensions.
AL objects touched
- Page 7122 “Expense Activity Log API”, ExpenseAgent: modified
- Codeunit 7107 “Exp. Policies To Eval Builder”, ExpenseAgent: modified
- Codeunit 6926 “Expense Activity Log Mgt.”, ExpenseAgent: modified
- Table 7100 “Expense Activity Log Entry”, ExpenseAgent: modified
- Codeunit 6901 “Expense Report Approval Mgmt”, ExpenseAgent: modified
- Table 6906 “Expense Report Header”, ExpenseAgent: modified
- Table 6907 “Expense Report Line”, ExpenseAgent: modified
Also merged into
- #12257 into
releases/29.xon 2026-10-05
Context
- Work items: AB#626515, AB#634361
- Labels: AL: Apps (W1), ExpenseManagement, Team: Finance
- Systems: development
- From the description: “Adds report-level policy evaluation summaries to expense activity history.”
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).