Table 9144 "Approvals Activities Cue"
Base Application · System.Automation
Across versions
- BC23present
- BC24declaration changed
- BC25unchanged
- BC261 fields changed
- BC27-30unchanged
Neighbourhood 3 connected objects and pages
Base Application · System.Automation · captioned “Approval Entry” · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Approval Entry |
| DataClassification | CustomerContent |
Fields
Explanation: the field’s ToolTip in the code; without one, the ToolTip of a page control bound to the field (marked via the page); without that, its Caption (marked caption) when that differs from the name.
| No. | Name | Type | Explanation | Notes |
|---|---|---|---|---|
| 1 | Primary Key Δ BC26 | Code[10] | — | |
| 2 | User ID Filter | Code[50] | — | FlowFilter |
| 3 | Requests to Approve | Integer | Specifies requests for certain documents, cards, or journal lines that you must approve for other users before they can proceed. via Page 9144 “Approvals Activities” | FlowField: count(“Approval Entry” where(“Approver ID” = field(“User ID Filter”), Status = filter(Open))) |
| 4 | Requests Sent for Approval | Integer | Specifies requests for certain documents, cards, or journal lines that your approver must approve before you can proceed. via Page 9144 “Approvals Activities” | FlowField: count(“Approval Entry” where(“Sender ID” = field(“User ID Filter”), Status = filter(Open))) |
Keys
- Key1: Primary Key (clustered)
Relations
- drill-down page Page 672 “Job Queue Entries”
- lookup page Page 672 “Job Queue Entries”
- Requests Sent for Approval: CalcFormula Table 454 “Approval Entry”
- Requests to Approve: CalcFormula Table 454 “Approval Entry”
Pages and codeunits on this table
- Page 9144 “Approvals Activities” (source table)
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: "table", object_name: "Approvals Activities Cue"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.