Table extension 6100 "E-Document Sending Profile"
EDocument · Microsoft.eServices.EDocument
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 2 connected objects and pages
EDocument · Microsoft.eServices.EDocument · BC29-30 · source at ea08af5e · facts from BC29
Extends Document Sending Profile.
Fields
Explanation: the field’s ToolTip in the code; without one, the ToolTip of a page control bound to the field (marked via the page); without that, its Caption (marked caption) when that differs from the name.
| No. | Name | Type | Explanation | Notes |
|---|---|---|---|---|
| 6102 | Electronic Service Flow | Code[20] | Specifies E-Document workflow used for sending documents. via Page extension 6101 “E-Document Sending Profile” | TableRelation Table 1501 “Workflow” (Workflow where(Template = const(false), Category = const(‘EDOC’))); DataClassification CustomerContent |
Procedures
1 local procedures, no public ones.
Relations
- Electronic Service Flow: TableRelation Table 1501 “Workflow”
- extends Table 60 “Document Sending Profile”
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: "tableextension", object_name: "E-Document Sending Profile"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.