codeunitAL Developmentofficial - Microsoftderived - from the source, no model text

Codeunit 8615 "Config. Progress Bar"

Base Application · System.IO

Across versions

  1. BC23-30present

Neighbourhood 9 connected objects and pages

Codeunit 8610 "Questionnaire Management" (calls, 15 links)Questionnaire ManagementCodeunit 8611 "Config. Package Management" (calls, 12 links)Config. Package ManagementCodeunit 8614 "Config. XML Exchange" (calls, 11 links)Config. XML ExchangeCodeunit 1180 "Data Privacy Mgmt" (calls, 6 links)Data Privacy MgmtCodeunit 8616 "Config. Management" (calls, 3 links)Config. ManagementCodeunit 8618 "Config. Excel Exchange" (calls, 3 links)Config. Excel ExchangeCodeunit 9852 "Effective Permissions Mgt." (calls, 3 links)Effective Permissions Mgt.Page 1181 "Data Privacy ListPage" (calls, 3 links)Data Privacy ListPageTable 8616 "Config. Package Field" (calls, 3 links)Config. Package Field

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.

Base Application · System.IO · BC23-30 · source at ea08af5e · facts from BC29

Events published

  • OnAfterInit(var Window: Dialog) (integration)
  • OnAfterUpdate(WindowText: Text; var Window: Dialog) (integration)
  • OnBeforeUpdate(WindowText: Text; var Window: Dialog; var IsHandled: Boolean) (integration)
  • OnInitOnBeforeWindowOpen(var Window: Dialog; var ProgressBarText: Text) (integration)

Procedures

  • Init(NewMaxCount: Integer; NewStepCount: Integer; WindowTitle: Text)
  • Update(WindowText: Text)
  • UpdateCount(WindowText: Text; Count: Integer)
  • Close()

Triggers

OnRun

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.

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

Evidence 1 sources