Page 1306 "O365 Tour Complete"
Base Application
Across versions
- BC23-30present
Neighbourhood 2 connected objects and pages
Base Application · captioned “Tour Complete” · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Tour Complete |
| SourceTable | O365 Getting Started |
| 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 |
|---|---|---|---|
| Control2 | Image1 | ImagePageDataMediaResources."Media Reference" |
— |
| That’s it | BodyText1 | BodyText |
— |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Processing | Return to Getting Started | — |
Procedures
3 local procedures, no public ones.
Triggers
OnAfterGetCurrRecord, OnInit, OnOpenPage, OnQueryClosePage
Relations
- source table Table 1309 “O365 Getting Started”
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.
- Codeunit 1309 “O365 Getting Started Mgt.” (2 calls:
MarkWizardAsDone → AreUserToursEnabled,OnOpenPage → AreUserToursEnabled)
Called by
- Codeunit 1309 “O365 Getting Started Mgt.” (1 call:
CheckOrLaunchWizard → (object))
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: "O365 Tour Complete"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.