Page 6118 "E-Document Service Status API"
EDocument · Microsoft.eServices.EDocument.API
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 1 connected objects and pages
EDocument · Microsoft.eServices.EDocument.API · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Extensible | false |
| SourceTable | E-Document Service Status |
| PageType | API |
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 |
|---|---|---|---|
| General | systemId | Rec.SystemId |
— |
| edocumentEntryNumber | E-Document Entry No | — | |
| edocumentServiceCode | E-Document Service Code | — | |
| status | Format(Rec.Status) |
— | |
| importProcessingStatus | Format(Rec."Import Processing Status") |
— | |
| fileContent | part Page 6119 “E-Doc. File Content API” | — |
Relations
- source table Table 6138 “E-Document Service Status”
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 Service Status API"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.