pageIntegration & APIsofficial - Microsoftderived - from the source, no model text

Page 6128 "E-Document Integration Logs"

EDocument · Microsoft.eServices.EDocument

Across versions

  1. BC23-28not present
  2. BC29-30present

Neighbourhood 1 connected objects and pages

Table 6127 "E-Document Integration Log" (relates to)E-Document Integration Log

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 · captioned “E-Document Communication Logs” · BC29-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption E-Document Communication Logs
SourceTable E-Document Integration Log
PageType List
ApplicationArea Basic, Suite

Fields on this page

Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).

Group Control Shows ToolTip
IntegrationLogs Entry No. Entry No. Specifies the log entry no.
Service Code Service Code Specifies the service code for the document.
URL Request URL Specifies the integration url used to send the document.
Method Method Specifies the http method used to send the document.
Response Status Response Status Specifies the response status of sending the document.

Actions

Group Action ToolTip Runs
Processing Export Request Message Exports request message.
Export Response Message Exports resonse message.

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: "page", object_name: "E-Document Integration Logs"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources