Page 662 "Approval Request Entries"
Base Application · System.Automation
Across versions
- BC23-27present
- BC28declaration changed
- BC29-30unchanged
Neighbourhood 2 connected objects and pages
Base Application · System.Automation · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Approval Request Entries |
| SourceTable | Approval Entry |
| PageType | List |
| UsageCategory | Lists |
| ApplicationArea | Suite |
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 | Overdue | Overdue |
Specifies that the approval is overdue. |
| 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 document number copied from the relevant sales or purchase document, such as a purchase order or a sales quote. | |
| To Approve | RecordIDText |
Specifies the record that you are requested to approve. | |
| Sequence No. | Sequence No. | Specifies the order of approvers when an approval workflow involves more than one approver. | |
| Sender ID | Sender ID | Specifies the ID of the user who sent the approval request for the document to be approved. | |
| Salespers./Purch. Code | Salespers./Purch. Code | Specifies the code for the salesperson or purchaser that was in the document to be approved. It is not a mandatory field, but is useful if a salesperson or a purchaser responsible for the customer/vendor needs to approve the document before it is processed. | |
| Approver ID | Approver ID | Specifies the ID of the user who must approve the document. | |
| Status | Status | Specifies the approval status for the entry: | |
| Date-Time Sent for Approval | Date-Time Sent for Approval | Specifies the date and the time that the document was sent for approval. | |
| Last Date-Time Modified | Last Date-Time Modified | Specifies the date when the approval entry was last modified. If, for example, the document approval is canceled, this field will be updated accordingly. | |
| Last Modified By User ID | Last Modified By User ID | Specifies the ID of the user who last modified the approval entry. If, for example, the document approval is canceled, this field will be updated accordingly. | |
| Comment | Comment | Specifies whether there are comments relating to the approval of the record. If you want to read the comments, choose the field to open the Approval Comment Sheet window. | |
| Due Date | Due Date | Specifies when the record must be approved, by one or more approvers. | |
| Available Credit Limit (LCY) | Available Credit Limit (LCY) | Specifies the remaining credit (in LCY) that exists for the customer. | |
| Amount | Amount | Specifies the total amount (excl. VAT) on the document awaiting approval. | |
| Amount (LCY) | Amount (LCY) | Specifies the total amount in LCY (excl. VAT) on the document awaiting approval. | |
| Currency Code | Currency Code | Specifies the code of the currency of the amounts on the sales or purchase lines. |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Show | Record | Open the document, journal line, or card that the approval request is for. | |
| Comments | View or add comments for the record. | ||
| Overdue Entries | View approval requests that are overdue. | ||
| All Entries | View all approval entries. | ||
| Processing | Delegate | Delegate the approval request to another approver that has been set up as your substitute approver. |
Procedures
1 local procedures, no public ones.
Triggers
OnAfterGetCurrRecord, OnAfterGetRecord, OnOpenPage
Relations
- source table Table 454 “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: "Approval Request Entries"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.