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

Enum 8890 "Email Scenario"

System Application · System.Email

Across versions

  1. BC23-30present

Neighbourhood 4 connected objects and pages

Enum extension 2650 "Email Printer Scenario" (extended by)Email Printer ScenarioEnum extension 8360 "Financial Email Scenario" (extended by)Financial Email ScenarioEnum extension 8891 "Base Email Scenario" (extended by)Base Email ScenarioEnum extension 8892 "Serv. Email Scenario" (extended by)Serv. Email Scenario

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
Extensible true

Values

Ordinal Name Caption Notes
0 Default Default

Extended by

Ask your agent

Procedure bodies are not stored here (D10). 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: "enum", object_name: "Email Scenario"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources