Codeunit 6759 "Create Reminders Action Job"
Base Application · Microsoft.Sales.Reminder
Across versions
- BC23not present
- BC24added
- BC25-30unchanged
Neighbourhood 7 connected objects and pages
Base Application · Microsoft.Sales.Reminder · BC24-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| TableNo | Reminder Action |
Events published
OnCreateReminderSafe(var Customer: Record Customer; var CustLedgEntry: Record "Cust. Ledger Entry"; var ReminderHeader: Record "Reminder Header"; OverdueEntriesOnly: Boolean; IncludeEntriesOnHold: Boolean; var FeeCustLedgEntryLine: Record "Cust. Ledger Entry"; var Success: Boolean)(integration)- subscribers: Codeunit 6761 “Create Aut. Event Handler” CreateReminderSafeHandler
Procedures
CreateReminders(var ReminderAction: Record "Reminder Action"; var ErrorOccured: Boolean)(internal)
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:
RunCreateReminders → CreateNewActionEntry,RunCreateReminders → GetLastActionEntry,RunCreateReminders → UpdateActionEntry) - Codeunit 6752 “Reminder Automation Log Errors” (2 calls:
CreateReminderForCustomer → LogLastError,Initialize → Initialize) - Codeunit 6761 “Create Aut. Event Handler” (2 calls:
CreateReminders → SetReminderAction,CreateReminders → UpdateStatusAfterRun) - Codeunit 8703 “Feature Telemetry” (2 calls:
CreateReminders → LogUptake,CreateReminders → LogUsage)
Called by
- Codeunit 6760 “Create Reminder Action” (1 call:
Invoke → CreateReminders)
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 Reminders Action Job"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.