Page 2508 "Extension Deployment Status"

System Application · System.Apps · captioned “Extension Installation Status” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property	Value
Caption	Extension Installation Status
Extensible	false
SourceTable	NAV App Tenant Operation
PageType	List
UsageCategory	Administration
ApplicationArea	All
Permissions	tabledata “Nav App Tenant Operation” = 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
Group	Name	`AppName`	Specifies the name of the app.
	Publisher	`AppPublisher`	Specifies the name of the app Publisher.
	Operation Type	`OperationType`	Specifies the deployment type.
	Status	`Rec.Status`	Specifies the deployment status.
	Schedule	`DeploymentSchedule`	Specifies the deployment schedule.
	App Version	`Version`	Specifies the version of the app.
	Started Date	`Rec."Started On"`	Specifies the deployment start date.

Actions

Group	Action	ToolTip	Runs
Processing	View	Specifies the status of the deployment.
	Refresh	Refresh the deployment details.
	Upload Extension	Upload an extension to your application.	Page 2507 “Upload And Deploy Extension”
Navigation	Extension Management	Open the Extension Management page.	Page 2500 “Extension Management”

Procedures

1 local procedures, no public ones.

Triggers

OnAfterGetRecord, 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.

Codeunit 2503 “Extension Operation Impl” (2 calls: OnAfterGetRecord → GetDeployOperationInfo, OnAfterGetRecord → RefreshStatus)
Codeunit 457 “Environment Information” (1 call: DetermineEnvironmentConfigurations → IsSaaS)

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: "Extension Deployment Status"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.