Codeunit 8891 "Email Scenario Mapping"

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

Properties

Events published

• OnAfterFromReportSelectionUsage(ReportSelectionUsage: Enum "Report Selection Usage"; var EmailScenario: Enum "Email Scenario") (integration): Subscribe to this event to add custom mappings from report selection usage (in case the enum was extended) to email scenarios.
  • subscribers: Codeunit 6450 “Serv. Integration Mgt.” OnAfterFromReportSelectionUsage
• OnOverrideEmailScenario(ReportSelectionUsage: Enum "Report Selection Usage"; var EmailScenario: Enum "Email Scenario"; var EmailScenarioChanged: Boolean) + BC27 (integration): Subscribe to this event to override the email scenario for a specific report selection usage.

Procedures

• FromReportSelectionUsage(ReportSelectionUsage: Enum "Report Selection Usage"): Enum "Email Scenario": Gets the document sending email scenario from report selection usage.

Called by

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 260 “Document-Mailing” (1 call: EmailFileInternal → FromReportSelectionUsage)

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