Available Columns in the Processes Monitor
The following columns are available in the processes monitor:
| Field | Description |
|---|---|
| Completion Strategy | How the process completes. This is used for processes started from web services, an external completion strategy means that the process completes when the web service reports back and sets the process to completed. |
| Created | The time the process was created. |
| Definition | The process definition that was submitted to create this process. |
| Description | The name of the process. Equals the description of the submitted process definition that created this process. |
| Documentation | A comment on the process. |
| Gantt Chart | Progress chart to display the progress of the process or chain. This chart uses statistics; if these are not available, the chart will consist of two horizontal lines. |
| Hold on Submit | If the process was submit on Hold, this field will be true . |
| ID | The ID for this process. This is unique for every process. |
| Maintenance | Displays the maintenance type of the process. Standard for built-in maintenance, Custom for custom maintenance, and blank for non-maintenance processes. |
| Modified | The last modification date of the process. |
| Next Submit Base Time | The time that will be used as a start time for the calculation of the next requested start time for a process with a submit frame, or for the requested start time of a new process where it has an infinite recurrence pattern. |
| Owner | process or chain owner. |
| Parent Job | If the process has a parent, the ID of the parent will be listed. |
| Priority | The priority of a process in the range 1 to 100. Higher values have precedence. |
| Process Server | The process server assigned to handle the process. |
| Queue | The queue the process was submitted into. |
| Remote Event | The remote event. |
| Remote ID | The remote unique identifier. |
| Remote Run End | The date and time when the process finished in the remote system. |
| Remote Run Start | The date and time the status started executing in the remote system. |
| Remote Status | The remote status. |
| Remote System | The remote system. |
| Requested Start Time | This is the time that the user has requested that the process start. In the absence of other restrictions, for example, time windows, this will be the scheduled start time. |
| Requested Start Time Type | Has the requested start time been explicitly set by the user, or has it been inherited from the parent. |
| Return Code | The return code of the process. |
| Run End | The date and time when the process finished. |
| Run Start | The date and time the status started executing. |
| Run Time | The time the process was in status Running. |
| Scheduled Start | The scheduled start date and time of the process. This is calculated by the dispatcher, and is dependent on any time windows associated with the process, or the process's queue, and the requested start time set by the user. This value is also set on a best effort basis when this process was submitted. |
| Status for Recurrence | The current status of the recurrence. |
| Status | The current status of the process. |
| Submit Frame | The submit frame the process was submitted into. |
| Time Window | The time window of the process. |
note
On clusters with multiple nodes, ID's are not necessarily sequential in time. Each node in the cluster will have a range of ID's.