Codeunit 6754 "Send Reminder Action Job"

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

Properties

Events published

• OnSendReminderSafe(var IssuedReminderHeader: Record "Issued Reminder Header"; var SendReminderSetup: Record "Send Reminders Setup"; var Success: Boolean) (integration)
  • subscribers: Codeunit 6753 “Send Reminder Event Handler” HandleSendReminderSafe

Procedures

• SendReminders(var ReminderAction: Record "Reminder Action"; var ErrorsOccured: Boolean): Sends all issued reminders matching the configured filters and reports errors.

Plus 4 local procedures.

Triggers

OnRun

Relations

• runs on Table 6750 “Reminder Action”

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: RunSendReminders → CreateNewActionEntry, RunSendReminders → GetLastActionEntry, RunSendReminders → UpdateActionEntry)
• Codeunit 6752 “Reminder Automation Log Errors” (2 calls: Initialize → Initialize, RunSendReminder → LogLastError)
• Codeunit 6753 “Send Reminder Event Handler” (2 calls: SendReminders → SetGlobalReminderAction, SendReminders → UpdateStatusAfterRun)
• Codeunit 8703 “Feature Telemetry” (2 calls: SendReminders → LogUptake, SendReminders → LogUsage)

Called by

• Codeunit 6755 “Send Reminder Action” (1 call: Invoke → SendReminders)

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