Page 6959 "Exp. Rules Preview"

ExpenseAgent · Microsoft.ExpenseAgent · captioned “Expense management rules” · BC29-30 · source at ea08af5e · facts from BC29

Properties

Property	Value
Caption	Expense management rules
Extensible	false
SourceTable	Expense Rule Header
PageType	List
ApplicationArea	Basic, Suite

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
Group	Expense Category Code	Expense Category Code	Specifies the expense category to which the rule applies.
	Expense Location	Expense Location	Specifies the expense location to which the rule applies.
	Effective Date	Effective Date	Specifies the date from which the rule is effective.
	Justification Required	Justification Required	Specifies whether justification is required for expenses that match this rule.
	Currency Code	Currency Code	Specifies the currency for monetary values in the rule.
	Status	`StatusText`	Specifies whether the row is a new default that will be added or already exists.
Content	Conditions	part Page 6965 “Exp. Rule Conditions Preview”	—

Procedures

1 local procedures, no public ones.

Triggers

OnOpenPage, OnAfterGetRecord

Relations

source table Table 6927 “Expense Rule Header”

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 6973 “Create Expense Categories” (1 call: ReloadPreview → LoadRulesPreview)

Recent changes

2026-08-04 #9859 [Master] - Move Expense Agent (Preview) app into BCApps (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. Rules Preview"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.