Enum 6429 "E-Doc. Message Status"
EDocument · Microsoft.eServices.EDocument.Processing.Message
Across versions
- BC23-28not present
- BC29-30present
EDocument · Microsoft.eServices.EDocument.Processing.Message · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Extensible | true |
Values
| Ordinal | Name | Caption | Notes |
|---|---|---|---|
| 0 | Created | Created | |
| 1 | Sent | Sent | |
| 2 | Queued | Queued | |
| 3 | Error | Error | |
| 4 | Received | Received | |
| 5 | Pending Response | Pending response | |
| 6 | Response Error | Response error |
Recent changes
- 2026-09-15 #10437 [FR E-Reporting] Add payment and invoice lifecycle messages (main, BC30, feature)
- 2026-07-27 #8698 [E-Documents Core] [Peppol] - Enabling EDI capabilities with E-Documents. PEPPOL Order Response Message Handling (main, BC30, feature, added)
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: "enum", object_name: "E-Doc. Message Status"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.