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

Page 8896 "Email Choose Scenario Attach"

System Application · System.Email

Across versions

  1. BC23-30present

Neighbourhood 4 connected objects and pages

Table 8911 "Email Scenario Attachments" (relates to)Email Scenario AttachmentsCodeunit 8703 "Feature Telemetry" (calls)Feature TelemetryCodeunit 8902 "Email Scenario Attach Impl." (calls)Email Scenario Attach Impl.Add attachments, links, and notes on records (Learn pages)Add attachments, links, and …

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 “Additional Attachments from Scenarios” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Additional Attachments from Scenarios
Extensible false
SourceTable Email Scenario Attachments
PageType List
ApplicationArea All
Permissions tabledata “Email Attachments” = rimd, tabledata “Email Scenario Attachments” = rimd

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
ScenarioAttahments File Name Attachment Name Specifies the name of the attachment
Email Scenario Scenario Specifies which Email Scenario the attachment comes from.

Actions

Group Action ToolTip Runs
Processing Download Attachments Download the selected attachment files.

Procedures

  • GetSelectedAttachments(var EmailAttachments: Record "Email Attachments")
  • SetEmailScenario(CurrentScenario: Enum "Email Scenario") (internal)

Triggers

OnOpenPage, OnAfterGetCurrRecord

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.

Documented on Microsoft Learn

Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).

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

Evidence 2 sources