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

Page 6110 "Outbound E-Doc. Factbox"

EDocument · Microsoft.eServices.EDocument.Service

Across versions

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

Neighbourhood 1 connected objects and pages

Table 6138 "E-Document Service Status" (relates to)E-Document Service Status

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.Service · BC29-30 · source at ea08af5e · facts from BC29

Properties

Property Value
SourceTable E-Document Service Status
PageType CardPart
UsageCategory None
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
Details Service EDocumentServiceStatus."E-Document Service Code" Specifies the service code of an E-Dcoument
Service Status EDocumentServiceStatus.Status Specifies the status of an E-Dcoument
Document Logs EDocumentServiceStatus.Logs() Specifies the count of logs for an E-Dcoument
Integration Logs EDocumentServiceStatus.IntegrationLogs() Specifies the count of communication logs for an E-Dcoument
Created Date EDocSystemCreatedAt Specifies the date when the E-Document was created
Created By EDocSystemCreatedBy Specifies the user who created the E-Document
DocumentServices E-Document Service Code E-Document Service Code Specifies the service code of an E-Dcoument
Service Status Status Specifies the status of an E-Dcoument

Procedures

1 local procedures, no public ones.

Triggers

OnAfterGetRecord, OnAfterGetCurrRecord

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: "Outbound E-Doc. Factbox"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources