Page 6135 "E-Document Service Status"
EDocument · Microsoft.eServices.EDocument
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 1 connected objects and pages
EDocument · Microsoft.eServices.EDocument · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| SourceTable | E-Document Service Status |
| PageType | ListPart |
| 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 |
|---|---|---|---|
| DocumentServices | E-Document Service Code | E-Document Service Code | Specifies the service code of an E-Document |
| Status | Status | Specifies the status of an E-Document | |
| Logs | Rec.Logs() |
Specifies the count of logs for an E-Document | |
| Communication Logs | Rec.IntegrationLogs() |
Specifies the count of communication logs for an E-Document |
Triggers
OnAfterGetRecord
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"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.