Page 6115 "New E-Documents 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 |
| PageType | API |
| Permissions | tabledata “E-Document Service” = r |
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 |
|---|---|---|---|
| Group | System ID | Rec.SystemId |
— |
| edocumentEntryNumber | Entry No | — | |
| E-Document Service Code | EDocumentServiceText |
Code of the E-Document Service. | |
| File Content | FileContent |
Base64 encoded file content of the E-Document. | |
| File Name | FileName |
Name of the file including extension (e.g., document.pdf). | |
| Process Document | ProcessDocument |
Indicates whether the E-Document should be processed automatically as part of request. |
Procedures
2 local procedures, no public ones.
Triggers
OnInsertRecord, OnFindRecord
Relations
- source table Table 6121 “E-Document”
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: "New E-Documents API"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.