BC Observatoryunofficial, made by waldo
enumextensionPlatform, DevOps & Performanceofficial - Microsoftderived - from the source, no model text

Enum extension 8891 "Base Email Scenario"

Base Application · System.Email

Open in Claude8891.mdSource on GitHub

Across versions

  1. BC23-24present
  2. BC25declaration changed
  3. BC26-30unchanged

Neighbourhood 1 connected objects and pages

Enum 8890 "Email Scenario" (relates to)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.

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

Extends Email Scenario.

Values

Ordinal Name Caption Notes
1 Invite External Accountant Invite External Accountant
2 Notification Notification
3 Job Planning Line Calendar Job Planning Line Calendar
4 Interaction Template Interaction Template
100 Sales Quote Sales Quote
101 Sales Order Sales Order
102 Sales Invoice Sales Invoice
103 Sales Credit Memo Sales Credit Memo
105 Purchase Quote Purchase Quote
106 Purchase Order Purchase Order
115 Reminder Reminder
116 Finance Charge Finance Charge
184 Posted Vendor Remittance Posted Vendor Remittance
185 Customer Statement Customer Statement
186 Vendor Remittance Vendor Remittance

Relations

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: "enumextension", object_name: "Base Email Scenario"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources