Codeunit 137 "OCR Inc. Doc. via Job Queue"
Base Application · Microsoft.EServices.EDocument
Across versions
- BC23present
- BC241 procedures added, 1 procedures removed
- BC25-30unchanged
Neighbourhood 5 connected objects and pages
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
- runs on Table 472 “Job Queue Entry”
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 133 “Send Incoming Document to OCR” (2 calls:
OnRun → TryRetrieveFromOCR,OnRun → TrySendToOCR) - Codeunit 132 “Release Incoming Document” (1 call:
EnqueueIncomingDoc → (object)) - Codeunit 453 “Job Queue - Enqueue” (1 call:
EnqueueJobEntry → (object))
Called by
- Codeunit 1521 “Workflow Response Handling” (1 call:
ReceiveFromOCRAsync → EnqueueIncomingDoc)
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.