pageAL Developmentofficial - Microsoftderived - from the source, no model text

Page 659 "Posted Approval Entries"

Base Application · System.Automation

Across versions

  1. BC23-27present
  2. BC28declaration changed
  3. BC29-30unchanged

Neighbourhood 3 connected objects and pages

Table 456 "Posted Approval Entry" (relates to)Posted Approval EntryTable 456 "Posted Approval Entry" (pages and codeunits on it, 2 links)Posted Approval EntryCodeunit 1535 "Approvals Mgmt." (calls)Approvals Mgmt.

Open in the neighbourhood explorer

One hop out, from the extracted relations and call graph. Up to 40 shown; the sections below list them all.

Base Application · System.Automation · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Posted Approval Entries
SourceTable Posted Approval Entry
PageType List
UsageCategory History
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 Approved PostedRecordID Specifies that the approval request has been approved.
Iteration No. Iteration No. Specifies the number of handling iterations that this approval request has reached.
Sequence No. Sequence No. Specifies the order of approvers when an approval workflow involves more than one approver.
Table ID Table ID Specifies the ID of the table where the record that is subject to approval is stored.
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.
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 sent.
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 ID Last Modified By ID Specifies the ID of the person 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 related to the approval of the document. If you want to read the comments, click the field to open the Comment Sheet window.
Due Date Due Date Specifies the date when the document is due for approval by the approver.
Amount (LCY) Amount (LCY) Specifies the total amount (excl. VAT) on the document waiting for approval. The amount is stated in the local currency.
Currency Code Currency Code Specifies the code of the currency of the amounts on the sales or purchase lines.
Delegation Date Formula Delegation Date Formula Specifies for the posted approval entry when an overdue approval request was automatically delegated to the relevant substitute. The field is filled with the value in the Delegate After field in the Workflow Responses window, translated to a date formula. The date of automatic delegation is then cal…

Actions

Group Action ToolTip Runs
Show Comments View or add comments for the record.
Record Open the document, journal line, or card that the approval request is for.

Triggers

OnAfterGetCurrRecord, OnAfterGetRecord

Relations

Pages and codeunits on this table

Called by

From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.

Ask your agent

Procedure bodies are not stored here (D10). The call sections above are our own, per object, from the BC29 call graph. 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: "Posted Approval Entries"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources