Interface "Feature Management"
System Application · System.Environment.Configuration
Across versions
- BC23-30present
Neighbourhood 1 connected objects and pages
System Application · System.Environment.Configuration · BC23-30 · source at ea08af5e · facts from BC29
Procedures
GetData(IncludeFeatureKeys: List of [Text[50]]; ExcludeFeatureKeys: List of [Text[50]]; var FeatureKeyBuffer: Record "Feature Key Buffer"): IntegerGetFeatureKey(FeatureId: Text[50]; var TempFeatureKey: Record "Feature Key" temporary): Boolean: Returns number of collected records. Feature interface read the system table “Feature Key” or another source of data depends on the interface implementation. In tests it can be a temporary table “Feature Key”.SetEnabled(TempFeatureKey: Record "Feature Key" temporary): Boolean: Modifies the Enabled field in the source record in the “Feature Key” table. The new value for the Enabled field is taken from the TempFeatureKey.Enabled.GenerateDependencies(var FeatureKeyBuffer: Record "Feature Key Buffer"; var FeatureDependency: Record "Feature Dependency"): Boolean: Fills the temporary table “Feature Dependency” stored in the single instance codeunit “Feature Dependency Management”. Add new feature dependencies by passing DependentFeatureId and ParentFeatureID, FeatureKeyBuffer is passed to control data consistency: FeatureDependency.New(FeatureKeyBuffer, Depen…
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.
- Codeunit 2610 “Feature Management Impl.” (1 call:
DefaultOpenFeatureManagement → (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: "interface", object_name: "Feature Management"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.