Codeunit 5979 "Service-Post and Send"

Base Application · Microsoft.Service.Posting · BC23-30 · source at ea08af5e · facts from BC29

Properties

Events published

• OnAfterPostAndBeforeSend(var ServiceHeader: Record "Service Header") (integration)
• OnBeforeCode(var ServiceHeader: Record "Service Header") (integration)
• OnAfterCode(var ServiceHeader: Record "Service Header") (integration)
• OnConfirmPostAndSendOnBeforeGetDocumentSendingProfile(ServiceHeader: Record "Service Header"; Customer: Record Customer; var DocumentSendingProfile: Record "Document Sending Profile"; var IsHandled: Boolean) (integration)

Procedures

3 local procedures, no public ones.

Triggers

OnRun

Relations

• runs on Table 5900 “Service Header”

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 5980 “Service-Post” (2 calls: Code → (object), Code → SendPostedDocumentRecord)
• Codeunit 6464 “Serv. Electr. Doc. Format” (1 call: ValidateElectronicFormats → ValidateElectronicServiceDocument)
• Page 365 “Post and Send Confirmation” (1 call: ConfirmPostAndSend → (object))

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: "Service-Post and Send"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.