pageIntegration & APIsofficial - Microsoftderived - from the source, no model text

Page 5580 "Digital Voucher Guide"

EnforcedDigitalVouchers · Microsoft.EServices.EDocument

Across versions

  1. BC23-28not present
  2. BC29-30present

Neighbourhood 3 connected objects and pages

Codeunit 8703 "Feature Telemetry" (calls, 3 links)Feature TelemetryCodeunit 1990 "Guided Experience" (calls)Guided ExperienceCodeunit 5585 "Digital Voucher Feature" (calls)Digital Voucher Feature

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.

EnforcedDigitalVouchers · Microsoft.EServices.EDocument · BC29-30 · source at ea08af5e · facts from BC29

Properties

Property Value
PageType NavigatePage

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
StandardBanner MediaResourcesStandard MediaResourcesStd."Media Reference" —
FinishedBanner MediaResourcesDone MediaResourcesFinished."Media Reference" —
OpenVoucherEntrySetupGroup OpenVoucherEntrySetup OpenVoucherEntrySetupLbl —
Voucher Entry setups defined: VoucherEntrySetupDefined Specifies the number of digital voucher setups by entry type.

Actions

Group Action ToolTip Runs
Processing Back —
Next —
Finish —

Procedures

9 local procedures, no public ones.

Triggers

OnQueryClosePage, OnInit, OnOpenPage

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

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: "Digital Voucher Guide"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources