pageAL Developmentofficial - Microsoftderived - from the source, no model text

Page 181 "Additional Customer Terms"

Base Application · Microsoft

Across versions

  1. BC23-30present

Neighbourhood 2 connected objects and pages

Table 140 "License Agreement" (relates to)License AgreementCodeunit 853 "License Agreement Management" (calls)License Agreement Management

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 · Microsoft · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Additional Customer Terms
SourceTable License Agreement
PageType Card
Permissions tabledata “License Agreement” = rim

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
General PleaseReadLbl PleaseReadLbl —
Control3 label —
Accepted Accepted Specifies if the license agreement was accepted.
Accepted By Accepted By Specifies the person that accepted the license agreement.
Accepted On Accepted On Specifies the date the license agreement is accepted.

Actions

Group Action ToolTip Runs
Processing Read the Additional Customer Terms Read the additional customer terms.
Accept the Additional Customer Terms Accept the additional customer terms.

Relations

Called by

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.

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: "Additional Customer Terms"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources