Page 666 "Overdue Approval Entries"
Base Application · System.Automation
Across versions
- BC23-28present
- BC29declaration changed
- BC30unchanged
Neighbourhood 2 connected objects and pages
Base Application · System.Automation · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Overdue Approval Entries |
| SourceTable | Overdue Approval Entry |
| PageType | List |
| UsageCategory | History |
| ApplicationArea | Suite |
| Permissions | TableData “Overdue Approval Entry” = d |
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 |
|---|---|---|---|
| Control1 | Due Date | Due Date | Specifies the date when the document is due for approval. |
| Approver ID | Approver ID | Specifies the ID of the user who must approve the document. | |
| Sent to ID | Sent to ID | Specifies the ID of the user who sent the mail notifying the approver that they has document approvals that are overdue. | |
| Sent Date | Sent Date | Specifies the date when the overdue notification mail was sent to the approver who should approve the document. | |
| Sent Time | Sent Time | Specifies the time when the overdue notification mail was sent to the approver who should approve the document. | |
| Table ID | Table ID | Specifies the ID of the table where the record that is subject to approval is stored. | |
| Document Type | Document Type | Specifies the type of document that an approval entry has been created for. Approval entries can be created for six different types of sales or purchase documents: | |
| Document No. | Document No. | Specifies the number of the document that was sent for approval. The number is copied from the relevant sales or purchase document, such as a purchase order or a sales quote. | |
| Sequence No. | Sequence No. | Specifies the order of approvers when an approval workflow involves more than one approver. | |
| Specifies the email address of the user to whom the overdue notification was sent. |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Show | Record | Open the document, journal, or card that the approval request applies to. | |
| App. Entry | Open the approval entry. | ||
| Processing | Delete Entries | Delete the overdue approval entries. |
Procedures
1 local procedures, no public ones.
Triggers
OnOpenPage
Relations
- source table Table 458 “Overdue Approval Entry”
Documented on Microsoft Learn
Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).
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: "Overdue Approval Entries"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.