codeunitPlatform, DevOps & Performanceofficial - Microsoftderived - from the source, no model text

Codeunit 8888 "Email Dispatcher"

System Application · System.Email

Across versions

  1. BC23-25present
  2. BC262 procedures added
  3. BC27-30unchanged

Neighbourhood 7 connected objects and pages

Table 8888 "Email Outbox" (relates to)Email OutboxCodeunit 8905 "Email Message Impl." (calls, 8 links)Email Message Impl.Codeunit 8703 "Feature Telemetry" (calls, 6 links)Feature TelemetryCodeunit 8909 "Email Retry Impl." (calls, 4 links)Email Retry Impl.Codeunit 8890 "Send Email" (calls, 3 links)Send EmailCodeunit 8901 "Email" (calls, 2 links)EmailCodeunit 8999 "Email Rate Limit Impl." (calls, 2 links)Email Rate Limit Impl.

Open in the neighbourhood explorer

One hop out, from the extracted relations and call graph. Up to 40 shown; the sections below list them all.

System Application · System.Email · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Access Internal
TableNo Email Outbox
Permissions tabledata “Sent Email” = ri, tabledata “Email Outbox” = rimd, tabledata “Email Message” = r, tabledata “Email Error” = ri, tabledata “Email Rate Limit” = r

Procedures

  • GetSuccess(): Boolean

Plus 8 local procedures.

Triggers

OnRun

Relations

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.

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: "Email Dispatcher"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources