Codeunit 6756 "Issue Reminder Event Handler"

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

Properties

Event subscriptions

• HandleIssueReminderSafe subscribes to Codeunit “Issue Reminder Action Job” OnIssueReminderSafe
• UpdateStatusWhenReminderIsIssued subscribes to Codeunit “Reminder-Issue” OnAfterIssueReminder

Procedures

• SetReminderAction(ReminderAction: Record "Reminder Action") (internal)
• SetReminderActionProgress(ReminderActionProgress: Codeunit "Reminder Action Progress") (internal)
• UpdateStatusAfterRun(): Updates the action log status and summary after the reminder issuing 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 393 “Reminder-Issue” (3 calls: IssueReminderSafe → (object), IssueReminderSafe → Set, IssueReminderSafe → SetGenJnlBatch)
• Codeunit 6751 “Reminder Action Progress” (3 calls: UpdateStatusAfterRun → CreateNewActionEntry, UpdateStatusAfterRun → GetLastActionEntry, UpdateStatusWhenReminderIsIssued → UpdateStatusAndTotalRecordsProcessed)

Called by

• Codeunit 6757 “Issue Reminder Action Job” (2 calls: IssueReminders → SetReminderAction, IssueReminders → 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: "Issue Reminder Event Handler"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.