Codeunit 6762 "Reminder-Send"
Base Application · Microsoft.Sales.Reminder
Across versions
- BC23not present
- BC24added
- BC251 events added
- BC26-30unchanged
Neighbourhood 3 connected objects and pages
Base Application · Microsoft.Sales.Reminder · BC24-30 · source at ea08af5e · facts from BC29
Events published
OnBeforePrintRecords(var IssuedReminderHeader: Record "Issued Reminder Header"; ShowRequestForm: Boolean; SendAsEmail: Boolean; HideDialog: Boolean; var IsHandled: Boolean)(integration)OnAfterPrintRecords(var IssuedReminderHeader: Record "Issued Reminder Header"; ShowRequestForm: Boolean; SendAsEmail: Boolean; HideDialog: Boolean; var DocumentSendingProfile: Record "Document Sending Profile")(integration)OnAfterSendReminder(var IssuedReminderHeader: Record "Issued Reminder Header")(integration)- subscribers: Codeunit 6753 “Send Reminder Event Handler” UpdateStatusWhenReminderIsSend
OnBeforeGetDocumentSendingProfile(var IssuedReminderHeader: Record "Issued Reminder Header"; var DocumentSendingProfile: Record "Document Sending Profile"; var DocumentSendingProfileFound: Boolean; var IsHandled: Boolean)+ BC25 (integration)
Procedures
SendReminder(): Sends the issued reminder using the configured document sending profile settings.Set(var IssuedReminderHeader: Record "Issued Reminder Header"; var SendReminderSetup: Record "Send Reminders Setup"): Initializes the reminder send parameters with the issued reminder and sending setup.
Plus 3 local procedures.
Triggers
OnRun
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 452 “Report Distribution Management” (1 call:
SendReminderImplementation → GetFullDocumentTypeText)
Called by
- Codeunit 6753 “Send Reminder Event Handler” (2 calls:
HandleSendReminderSafe → (object),HandleSendReminderSafe → Set)
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: "Reminder-Send"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.