codeunitIntegration & APIsofficial - Microsoftderived - from the source, no model text

Codeunit 137 "OCR Inc. Doc. via Job Queue"

Base Application · Microsoft.EServices.EDocument

Across versions

  1. BC23present
  2. BC241 procedures added, 1 procedures removed
  3. BC25-30unchanged

Neighbourhood 5 connected objects and pages

Table 472 "Job Queue Entry" (relates to)Job Queue EntryCodeunit 133 "Send Incoming Document to OCR" (calls, 2 links)Send Incoming Document to OCRCodeunit 132 "Release Incoming Document" (calls)Release Incoming DocumentCodeunit 1521 "Workflow Response Handling" (calls)Workflow Response HandlingCodeunit 453 "Job Queue - Enqueue" (calls)Job Queue - Enqueue

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.EServices.EDocument · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
TableNo Job Queue Entry
Permissions TableData “Job Queue Entry” = rimd

Procedures

  • EnqueueIncomingDoc(var IncomingDocument: Record "Incoming Document")
  • CancelQueueEntry(var IncomingDocument: Record "Incoming Document")

Plus 2 local procedures.

Triggers

OnRun

Relations

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.

Called by

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: "OCR Inc. Doc. via Job Queue"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources