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

Page 8930 "Email View Policy List"

System Application · System.Email

Across versions

  1. BC23-30present

Neighbourhood 8 connected objects and pages

Table 8930 "Email View Policy" (relates to)Email View PolicyCodeunit 8930 "Email View Policy" (calls, 2 links)Email View PolicyCodeunit 8703 "Feature Telemetry" (calls)Feature TelemetryCodeunit 8900 "Email Impl" (calls)Email ImplControl Access Using Security Groups (Learn pages)Control Access Using Securit…Create users according to licenses (Learn pages)Create users according to li…Define granular permissions (Learn pages)Define granular permissionsManage permissions through user groups (legacy) (Learn pages)Manage permissions through u…

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 “User Email View Policies” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption User Email View Policies
Extensible false
SourceTable Email View Policy
PageType List
UsageCategory Administration
ApplicationArea All
Permissions tabledata “Email View Policy” = rimd, tabledata User = r

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
UserPolicies User ID User ID Specifies a unique identifier for the user.
Policy Email View Policy Specifies the assigned email policy

Triggers

OnOpenPage, OnDeleteRecord, 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.

Called by

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

Evidence 5 sources