Codeunit 4599 "SOA Integration Events"
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 |
Event subscriptions
- OnFeedbackEventForSalesOrderAgentTasks subscribes to Codeunit “System Action Triggers” OnFeedbackEvent
Procedures
2 local procedures, no public ones.
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 1590 “Microsoft User Feedback” (4 calls:
TriggerSOATaskThumbsFeedback → RequestDislikeFeedback,TriggerSOATaskThumbsFeedback → RequestLikeFeedback,TriggerSOATaskThumbsFeedback → SetIsAIFeedback, …) - Codeunit 8711 “Telemetry” (1 call:
TriggerSOATaskThumbsFeedback → LogMessage)
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 Integration Events"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.