Codeunit 4403 "SOA Output Message Validation"
SalesOrderAgent · Microsoft.Agent.SalesOrderAgent
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 2 connected objects and pages
SalesOrderAgent · Microsoft.Agent.SalesOrderAgent · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Access | Internal |
Procedures
GetPrompt(): JsonObjectExecute(Arguments: JsonObject): VariantGetName(): Text
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 4598 “SOA Instructions” (1 call:
GetPrompt → GetOutputMessageSignatureUpdateTool)
Called by
- Codeunit 4402 “SOA Output Message Setup” (1 call:
AddSignatureToMessageBody → Execute)
Implements
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: "SOA Output Message Validation"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.