Page 8893 "Email Scenario Setup"
System Application · System.Email
Across versions
- BC23-28present
- BC29declaration changed
- BC30unchanged
Neighbourhood 5 connected objects and pages
System Application · System.Email · captioned “Email Scenario Assignment” · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Email Scenario Assignment |
| Extensible | false |
| SourceTable | Email Account Scenario |
| PageType | List |
| UsageCategory | Administration |
| ApplicationArea | All |
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 |
|---|---|---|---|
| ScenariosByEmail | Scenarios by email accounts | Display Name | Specifies the scenarios that are using the email account. |
| Default | DefaultTxt |
Specifies whether this is the default account to use for scenarios when no other account is specified. |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Account | Assign scenarios | Assign email scenarios for the selected email account. When assigned, everyone will use the account for the scenario. For example, if you assign the Sales Order scenario, everyone will use the account to send sales orders. | |
| Scenario | Reassign | Reassign the selected scenarios to another email account. | |
| Unassign | Unassign the selected scenarios. Afterward, the default email account will be used to send emails for the scenarios. | ||
| Set Scenario Attachments | Attach one or more files that can be attached to emails for this scenario. |
Procedures
SetEmailAccountId(AccountId: Guid; Connector: Enum "Email Connector")(internal)
Plus 1 local procedures.
Triggers
OnOpenPage, OnAfterGetRecord
Relations
- source table Table 8907 “Email Account Scenario”
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.
- Codeunit 8703 “Feature Telemetry” (1 call:
OnOpenPage → LogUptake) - Codeunit 8889 “Email Account Impl.” (1 call:
OnOpenPage → IsUserEmailAdmin) - Codeunit 8892 “Email Scenario Impl.” (1 call:
OnOpenPage → GetScenariosByEmailAccount)
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 Scenario Setup"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.