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

Codeunit 8892 "Email Scenario Impl."

System Application · System.Email

Across versions

  1. BC23present
  2. BC241 procedures added
  3. BC25-30unchanged

Neighbourhood 5 connected objects and pages

Codeunit 8893 "Email Scenario" (calls, 7 links)Email ScenarioCodeunit 8889 "Email Account Impl." (calls, 3 links)Email Account Impl.Codeunit 8894 "Email Account" (calls, 3 links)Email AccountPage 8893 "Email Scenario Setup" (calls)Email Scenario SetupPage 8894 "Email Scenarios for Account" (calls)Email Scenarios for Account

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
Permissions tabledata “Email Scenario” = rimd

Procedures

  • GetEmailAccount(Scenario: Enum "Email Scenario"; var EmailAccount: Record "Email Account"): Boolean
  • IsThereEmailAccountSetForScenario(Scenario: Enum "Email Scenario"): Boolean + BC24
  • SetEmailAccount(Scenario: Enum "Email Scenario"; EmailAccount: Record "Email Account")
  • UnassignScenario(Scenario: Enum "Email Scenario")
  • GetScenariosByEmailAccount(var Result: Record "Email Account Scenario"): Get a list of entries, representing a tree structure with email accounts and the scenarios, assigned to each accout.
  • AddScenarios(EmailAccount: Record "Email Account Scenario"): Boolean
  • GetAvailableScenariosForAccount(EmailAccount: Record "Email Account Scenario"; var EmailScenarios: Record "Email Account Scenario"; IncludeDefaultEmailScenario: Boolean)
  • ChangeAccount(var EmailScenario: Record "Email Account Scenario"): Boolean
  • DeleteScenario(var EmailScenario: Record "Email Account Scenario"): Boolean

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.

Called by

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

Evidence 1 sources