BC Observatoryunofficial, made by waldo
codeunitPlatform, DevOps & Performanceofficial - Microsoftderived - from the source, no model text

Codeunit 1383 "Batch Processing Mgt. Handler"

Base Application · Microsoft.Foundation.BatchProcessing

Open in Claude1383.mdSource on GitHub

Across versions

  1. BC23-30present

Neighbourhood 1 connected objects and pages

Codeunit 4100 "Temp Blob" (calls, 2 links)Temp Blob

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 · Microsoft.Foundation.BatchProcessing · BC23-30 · source at ea08af5e · facts from BC29

Event subscriptions

  • SetTrueOnSystemSetBatchProcessingActive subscribes to Codeunit “Batch Processing Mgt.” OnSystemSetBatchProcessingActive
  • HandleOnAddArtifact subscribes to Codeunit “Batch Processing Mgt.” OnAddArtifact
  • HandleOnHasArtifacts subscribes to Codeunit “Batch Processing Mgt.” OnHasArtifacts
  • HandleOnGetArtifacts subscribes to Codeunit “Batch Processing Mgt.” OnGetArtifacts

Procedures

  • AddArtifact(ArtifactType: enum "Batch Processing Artifact Type"; ArtifactName: Text[1024]; var TempBlobArtivactValue: Codeunit "Temp Blob")

Plus 2 local procedures.

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.

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: "Batch Processing Mgt. Handler"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources