Codeunit 4309 "SOA Agent Task Execution"

SalesOrderAgent · Microsoft.Agent.SalesOrderAgent · BC29-30 · source at ea08af5e · facts from BC29

Properties

Procedures

• AnalyzeAgentTaskMessage(AgentTaskMessage: Record "Agent Task Message"; var Annotations: Record "Agent Annotation")
• GetAgentTaskUserInterventionSuggestions(AgentTaskUserInterventionRequestDetails: Record "Agent User Int Request Details"; var AgentTaskUserInterventionSuggestion: Record "Agent Task User Int Suggestion")
• GetAgentTaskPageContext(AgentTaskPageContextRequest: Record "Agent Task Page Context Req."; var AgentTaskPageContext: Record "Agent Task Page Context")

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 4400 “SOA Setup” (2 calls: GetAgentTaskPageContext → GetAgentTaskPageContext, GetAgentTaskUserInterventionSuggestions → GetAgentTaskUserInterventionSuggestions)
• Codeunit 4399 “SOA Annotation” (1 call: AnalyzeAgentTaskMessage → GetAgentTaskMessageAnnotations)
• Codeunit 4402 “SOA Output Message Setup” (1 call: AnalyzeAgentTaskMessage → PrepareOutputMessage)

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 Agent Task Execution"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.