Codeunit 6761 "Create Aut. Event Handler"

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

Event subscriptions

• CreateReminderSafeHandler subscribes to Codeunit “Create Reminders Action Job” OnCreateReminderSafe
• HandlerReminderCreated subscribes to Codeunit “Reminder-Make” OnMakeReminderOnBeforeReminderHeaderModify
• BeforeReminderHeaderModify subscribes to Codeunit “Reminder-Make” OnBeforeReminderHeaderModify

Procedures

• SetReminderAction(var ReminderAction: Record "Reminder Action"): Sets the reminder action record used for tracking reminder creation progress.
• UpdateStatusAfterRun(): Updates the action log status and summary after the reminder creation process completes.

Plus 1 local procedures.

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 6751 “Reminder Action Progress” (3 calls: HandlerReminderCreated → UpdateStatusAndTotalRecordsProcessed, UpdateStatusAfterRun → CreateNewActionEntry, UpdateStatusAfterRun → GetLastActionEntry)
• Codeunit 392 “Reminder-Make” (2 calls: CreateReminders → (object), CreateReminders → Set)

Called by

• Codeunit 6759 “Create Reminders Action Job” (2 calls: CreateReminders → SetReminderAction, CreateReminders → UpdateStatusAfterRun)

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: "Create Aut. Event Handler"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.