Page 6185 "E-Doc. Draft Feedback"
EDocument · Microsoft.eServices.EDocument.Processing.Import.Purchase
Across versions
- BC23-28not present
- BC29-30present
EDocument · Microsoft.eServices.EDocument.Processing.Import.Purchase · captioned “E-Document Draft Feedback” · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | E-Document Draft Feedback |
| Extensible | false |
| PageType | ConfirmationDialog |
| UsageCategory | None |
| ApplicationArea | All |
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 |
|---|---|---|---|
| Content | Your experience helps us improve. | label | — |
| AP workflows differ across regions, and sometimes Payables Agent may not cover a local requirement, a validation rule, or a something your team depends on. If you’ve noticed anything like this — something that felt missing or didn’t align with your local process — we’d really appreciate you telling … | label | — | |
| Provide feedback? | label | — |
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-Doc. Draft Feedback"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.