Page 6756 "Reminder Action History"

Base Application · Microsoft.Sales.Reminder · BC24-30 · source at ea08af5e · facts from BC29

Properties

Property	Value
SourceTable	Reminder Action Group Log
PageType	List
ApplicationArea	All

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
ActionGroupLog	Run Id	Run Id	Specifies the unique identifier of the reminder action group log entry. Each job will get an unique identifier. from the table field
	Reminder Action Group	Reminder Action Group ID	Specifies the reminder action group that was run. from the table field
	Status	Status	Specifies the status of the reminder action group log entry. from the table field
	Started on	Started On	Specifies the date and time when the reminder action group log entry was started.
	Completed on	Completed On	Specifies the date and time when the reminder action group log entry was completed.
	Number of errors	`NumberOfActiveErrors`	Specifies the number of errors that occurred during the run.

Triggers

OnAfterGetRecord, OnAfterGetCurrRecord

Relations

card page Page 6758 “Reminder Act. History Detailed”
source table Table 6753 “Reminder Action Group Log”

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 6751 “Reminder Action Group” (1 call: ShowHistory → (object))

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: "Reminder Action History"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.