Codeunit 7107 "Exp. Policies To Eval Builder"
ExpenseAgent · Microsoft.ExpenseAgent
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 2 connected objects and pages
ExpenseAgent · Microsoft.ExpenseAgent · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Access | Internal |
Procedures
Build(var TempPolicyToEvalBuffer: Record "Exp. Policy To Eval Buffer" temporary; SubjectSystemIdFilter: Text)HasOutstandingPolicies(ExpenseReportLine: Record "Expense Report Line"): BooleanGetEvaluationState(ExpenseReportLine: Record "Expense Report Line"; var HasApplicablePolicies: Boolean; var HasOutstandingPoliciesResult: Boolean)GetEvaluationState(ExpenseReportLine: Record "Expense Report Line"; var HasApplicablePolicies: Boolean; var HasOutstandingPoliciesResult: Boolean; var TempMatchedEvaluations: Record "Expense Policy Evaluation" temporary; ReadIsolation: IsolationLevel)(internal): Replaces the temporary output with current applicable results (keys, compliance and timestamp only). Tests result presence, not line confirmation. Snapshot callers explicitly select their read isolation.
Plus 8 local procedures.
Called by
From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.
- Table 6907 “Expense Report Line” (3 calls:
GetPolicyStatus → GetEvaluationState,IsPolicyEvaluationComplete → GetEvaluationState,MarkPoliciesEvaluated → HasOutstandingPolicies) - Page 7108 “Exp. Policies To Eval API” (1 call:
OnFindRecord → Build)
Recent changes
- 2026-10-01 #11628 Expense Agent: capture submission policy evaluation history (main, BC30, feature)
- 2026-08-26 #10631 Integration/main to releases 29.x 31a860b5 (releases/29.x, BC29, feature, added)
- 2026-08-21 #10031 Add AI-assisted policy evaluation backend to Expense Agent (main, BC30, feature, added)
Ask your agent
Procedure bodies are not stored here (D10). The call sections above are our own, per object, from the BC29 call graph. For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: bcatlas_resolve_node(object_type: "codeunit", object_name: "Exp. Policies To Eval Builder"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.