Codeunit 6753 "Send Reminder Event Handler"

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

Events published

• OnAttachRelatedDocumentsBeforeEmailFileInternalOnAfterAttachRelatedDocument(var TempEmailItem: Record "Email Item" temporary; var PostedDocNo: Code[20]; SendRemindersSetup: Record "Send Reminders Setup"; SourceTableID: Integer; SourceRelationID: Integer; SourceID: Guid; ReportUsage: Integer) + BC27 (integration)

Event subscriptions

• HandleSendReminderSafe subscribes to Codeunit “Send Reminder Action Job” OnSendReminderSafe
• UpdateAfterEmailSendFailed subscribes to Codeunit “Email” OnAfterEmailSendFailed
• DeleteFailedEmailsBeforeSendingEmail subscribes to Codeunit “Document-Mailing” OnBeforeSendEmail
• UpdateStatusAfterEmailSent subscribes to Codeunit “Document-Mailing” OnAfterEmailSent
• UpdateStatusWhenReminderIsSend subscribes to Codeunit “Reminder-Send” OnAfterSendReminder
• HandleGetSendToCustomerDirectly subscribes to Table “Report Selections” OnGetSendToCustomerDirectly
• HandleOnGetReportParameters subscribes to Table “Issued Reminder Header” OnGetReportParameters
• AttachRelatedDocumentsBeforeEmailFileInternal subscribes to Codeunit “Document-Mailing” OnBeforeEmailItemPreparation

Procedures

• SetGlobalReminderAction(ReminderAction: Record "Reminder Action") (internal)
• GetEmailsSent(): List of [Text]: Retrieves the list of issued reminder numbers that were successfully emailed.
• GetEmailsFailed(): List of [Text]: Retrieves the list of issued reminder numbers that failed to send via email.
• UpdateStatusAfterRun(): Updates the action log status and summary after the reminder sending process completes.

Plus 3 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” (4 calls: SetGlobalReminderAction → GetLastEntryForGroup, UpdateStatusAfterRun → CreateNewActionEntry, UpdateStatusAfterRun → GetLastActionEntry, …)
• Codeunit 545 “Send Reminder” (2 calls: DeleteFailedEmailsBeforeSendingEmail → DeleteFailedOutboxMessageIfExists, UpdateStatusAfterEmailSent → SetFailedOutboxMessageID)
• Codeunit 6752 “Reminder Automation Log Errors” (2 calls: SetGlobalReminderAction → Initialize, UpdateStatusAfterEmailSent → LogLastError)
• Codeunit 6762 “Reminder-Send” (2 calls: HandleSendReminderSafe → (object), HandleSendReminderSafe → Set)
• Codeunit 260 “Document-Mailing” (1 call: AttachDocument → GetAttachmentFileName)
• Codeunit 4100 “Temp Blob” (1 call: AttachDocument → CreateInStream)
• Codeunit 452 “Report Distribution Management” (1 call: AttachDocument → GetFullDocumentTypeText)

Called by

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