pageAdministration & Setupofficial - Microsoftderived - from the source, no model text

Page 2610 "Feature Management"

System Application · System.Environment.Configuration

Across versions

  1. BC23-30present

Neighbourhood 3 connected objects and pages

Codeunit 1351 "Telemetry Subscribers" (event subscribers)Telemetry SubscribersCodeunit 2611 "Feature Management Facade" (calls)Feature Management FacadeEnabling upcoming features ahead of time (Learn pages)Enabling upcoming features a…

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

Properties

Property Value
Caption Feature Management
Extensible false
SourceTable Feature Key
PageType List
UsageCategory Administration
ApplicationArea All
Permissions tabledata “Feature Data Update Status” = r, tabledata “Feature Key” = rm

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
FeatureKeys Feature Rec.Description Specifies the name of the new capability or change in design.
Learn more LearnMoreLbl View a detailed description of new capabilities and behaviors that are available when the feature is enabled (opens in a new tab).
Automatically enabled from Rec."Mandatory By" Specifies a future software version and approximate date when this feature is automatically enabled for all users and cannot be disabled. Until this future version, the feature is optional.
Automatically enabled from version Rec."Mandatory By Version" Specifies a future software version when this feature is automatically enabled for all users and cannot be disabled. Until this future version, the feature is optional.
Enabled for Rec.Enabled Specifies whether the feature is enabled for all users or for none. The change takes effect the next time each user signs in.
Get started TryItOut Starts a new session with the feature temporarily enabled (opens in a new tab). This does not affect any other users.
Current Company Status FeatureDataUpdateStatus."Feature Status" Specifies the status of data update in the current company. Until it is complete the feature is not fully enabled in the current company.
Update Start Date/Time FeatureDataUpdateStatus."Start Date/Time" Specifies the earliest date and time when the data update task should be run.
Task Id FeatureDataUpdateStatus."Task Id" Specifies the id of the scheduled task.
Session Id FeatureDataUpdateStatus."Session Id" Specifies the session id where the task is being ran.
Server Instance ID FeatureDataUpdateStatus."Server Instance Id" Specifies the serviec instance id where the task is being ran.

Actions

Group Action ToolTip Runs
Data Update Schedule Schedule or run the data update task in the current or background session.
Show Log Show the error log entry.
Cancel Scheduled Job Cancel the scheduled data update task.

Events published

  • OnOpenFeatureMgtPage(var FeatureIDFilter: Text; var IgnoreFilter: Boolean) (integration)

Trigger event subscribers

Procedures

6 local procedures, no public ones.

Triggers

OnOpenPage, OnAfterGetRecord, OnAfterGetCurrRecord

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.

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

Evidence 2 sources