Page 7108 "Exp. Policies To Eval API"
ExpenseAgent · Microsoft.ExpenseAgent
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 3 connected objects and pages
ExpenseAgent · Microsoft.ExpenseAgent · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Extensible | false |
| SourceTable | Exp. Policy To Eval Buffer |
| PageType | API |
Fields on this page
Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).
| Group | Control | Shows | ToolTip |
|---|---|---|---|
| General | Subject System Id | Subject System Id | — |
| Subject Version | Subject Version | — | |
| Policy System Id | Policy System Id | — | |
| Policy Line No. | Policy Line No. | — | |
| Policy Version | Policy Version | — | |
| Expense Category Code | Expense Category Code | — | |
| Description | Description | — | |
| Policy Text | Policy Text | — |
Triggers
OnInit, OnFindRecord, OnNextRecord
Relations
- source table Table 7106 “Exp. Policy To Eval Buffer”
Calls
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.
- Codeunit 6993 “Expense Agent API Validation” (1 call:
OnInit → VerifyAgentAccess) - Codeunit 7107 “Exp. Policies To Eval Builder” (1 call:
OnFindRecord → Build)
Recent changes
- 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: "page", object_name: "Exp. Policies To Eval API"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.