Page 30092 "APIV2 - Feature Management"
APIV2 · System.Environment.Configuration
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 1 connected objects and pages
APIV2 · System.Environment.Configuration · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | ‘feature’, Locked = true |
| Extensible | false |
| SourceTable | Feature Key |
| PageType | API |
| 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 |
|---|---|---|---|
| GroupName | ID | Rec.ID |
— |
| Enabled | Rec.Enabled |
— | |
| Description | Rec.Description |
— | |
| Documentation link | Rec."Learn More Link" |
— | |
| Mandatory By | Rec."Mandatory By" |
— | |
| Can Try | Rec."Can Try" |
— | |
| Is One Way | Rec."Is One Way" |
— | |
| Data Update Required | Rec."Data Update Required" |
— | |
| Mandatory By Version | Rec."Mandatory By Version" |
— | |
| Description In English | Rec."Description In English" |
— |
Procedures
Activate(var ActionContext: WebServiceActionContext; UpdateInBackground: Boolean; StartDateTime: DateTime)Deactivate(var ActionContext: WebServiceActionContext)
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 2611 “Feature Management Facade” (2 calls:
Activate → GetFeatureDataUpdateStatus,Activate → UpdateSilently)
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: "APIV2 - Feature Management"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.