Codeunit 1642 "Intelligent Info Manifest"
Base Application
Across versions
- BC23-30present
Neighbourhood 4 connected objects and pages
Base Application · BC23-30 · source at ea08af5e · facts from BC29
Event subscriptions
- OnCreateAddin subscribes to Codeunit “Add-in Manifest Management” CreateDefaultAddins
- OnGenerateManifest subscribes to Codeunit “Add-in Manifest Management” OnGenerateManifest
- OnGetAddin subscribes to Codeunit “Add-in Manifest Management” GetAddin
- OnGetAddinID subscribes to Codeunit “Add-in Manifest Management” GetAddinID
- OnGetAddinVersion subscribes to Codeunit “Add-in Manifest Management” GetAddinVersion
- OnGetCodeunitID subscribes to Codeunit “Add-in Manifest Management” GetManifestCodeunit
Procedures
11 local procedures, no public ones.
Triggers
OnRun
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 1652 “Add-in Manifest Management” (9 calls:
DefaultManifestText → XMLEncode,OnCreateAddin → CreateAddin,OnGenerateManifest → SetCommonManifestItems, …) - Codeunit 1643 “Hyperlink Manifest” (7 calls:
GetDocType → GetNameForPurchaseCrMemo,GetDocType → GetNameForPurchaseInvoice,GetDocType → GetNameForPurchaseOrder, …) - Codeunit 457 “Environment Information” (1 call:
SetupResourceImages → IsSaaS) - Codeunit 9179 “Application Area Mgmt. Facade” (1 call:
GetPurchaseOrderMenuItem → IsSuiteEnabled)
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: "codeunit", object_name: "Intelligent Info Manifest"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.