BC Observatoryunofficial, made by waldo
codeunitIntegration & APIsofficial - Microsoftderived - from the source, no model text

Codeunit 6129 "E-Doc. Deferral Matching"

EDocument · Microsoft.eServices.EDocument.Processing.AI

Open in Claude6129.mdSource on GitHub

Across versions

  1. BC23-28not present
  2. BC29present
  3. BC30changed

Neighbourhood 1 connected objects and pages

Table 6101 "E-Document Purchase Line" (relates to)E-Document Purchase Line

Open in the neighbourhood explorer

One hop out, from the extracted relations and call graph. Up to 40 shown; the sections below list them all.

EDocument · Microsoft.eServices.EDocument.Processing.AI · BC29-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Access Internal
TableNo E-Document Purchase Line

Events published

  • OnGetDeferralMatchFunctionResponse(TempEDocLineMatchBuffer: Record "EDoc Line Match Buffer" temporary) (integration)

Procedures

  • GetPrompt(): JsonObject
  • Execute(Arguments: JsonObject): Variant (internal)
  • GetName(): Text
  • GetSystemPrompt(UserLanguage: Text): SecretText
  • GetTools(): List of [Interface "AOAI Function"]
  • GetFeatureName(): Text

Plus 4 local procedures.

Triggers

OnRun

Relations

Ask your agent

Procedure bodies are not stored here (D10). 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: "E-Doc. Deferral Matching"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources