Page 1529 "Workflow Overview"
Base Application · System.Automation
Across versions
- BC23-30present
Neighbourhood 2 connected objects and pages
Base Application · System.Automation · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Workflow Overview |
| SourceTable | Workflow Step Instance |
| PageType | List |
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 |
|---|---|---|---|
| Group | Workflow Step | Description | Specifies the workflow step instance. |
| Status | Status | Specifies the status of the workflow step instance. Active means that the step instance in ongoing. Completed means that the workflow step instance is done. Ignored means that the workflow step instance was skipped in favor of another path. | |
| Last Modified Date-Time | Last Modified Date-Time | Specifies the date and time when a user last participated in the workflow step instance. | |
| Last Modified By User ID | Last Modified By User ID | Specifies the user who last participated in the workflow step instance. | |
| Record | WorkflowRecord |
Specifies the record from which the window is opened from the Workflow FactBox. |
Procedures
3 local procedures, no public ones.
Triggers
OnAfterGetRecord
Relations
- source table Table 1504 “Workflow Step Instance”
Calls
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.
- Codeunit 1521 “Workflow Response Handling” (1 call:
GetDescription → GetDescription)
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: "Workflow Overview"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.