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

Page 8885 "Email Activities"

System Application · System.Email

Across versions

  1. BC23-30present

Neighbourhood 2 connected objects and pages

Codeunit 8885 "Email Activities" (calls, 3 links)Email ActivitiesCodeunit 8889 "Email Account Impl." (calls)Email Account 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 · captioned “Email Status” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Email Status
PageType CardPart

Fields on this page

Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).

Group Control Shows ToolTip
Email Activities Failed Emails in Outbox FailedOutboxEmails Specifies the emails that were not successfully sent.
Draft Emails in Outbox DraftOutboxEmails Specifies the emails that are saved as drafts.
Sent Emails Last 30 Days SentEmails Specifies Sent Emails in the Last 30 Days

Triggers

OnAfterGetCurrRecord, OnPageBackgroundTaskCompleted

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

Evidence 1 sources