Execution
System Property |
Type |
Description |
Changeable |
Identity |
Required for creation |
---|---|---|---|---|---|
system_id |
Int |
Id of the execution Important! Run id and execution id refer to different concepts. The run id is generated by the Automation Engine when the execution starts. The execution id is the key that uniquely identifies a deployment in CDA. |
|
Yes |
|
system_maintype |
String |
The main type (Execution) |
|
|
|
system_status |
String |
Current execution status |
Yes |
|
|
system_planned_from |
Date/Time |
Planned date/time of the start of the execution. Note: Date/time format is set according to the display option defined in the user settings. Refresh the view or start a new session for display changes to take effect. |
Yes |
|
Yes |
system_actual_from |
Date/Time |
Actual date/time of the start of the execution. Note: Date/time format is set according to the display option defined in the user settings. Refresh the view or start a new session for display changes to take effect. |
|
|
|
system_actual_to |
Date/Time |
Actual timestamp, when the execution was finished or canceled. Note: Date/time format is set according to the display option defined in the user settings. Refresh the view or start a new session for display changes to take effect. |
|
|
|
system_actual_duration |
Timespan |
Actual duration of the execution in iso 8601 timespan format (without start date). |
|
|
|
system_failed_reason | String | Can be: <empty>, "Unknown. Please look at history for details.", "The execution failed in the Automation Engine", "The execution was not approved in time", "The execution failed due to changes on related entities", "The execution was not confirmed in time", "The execution was not started in time", "The execution failed due to lack of permission" | |||
system_process_run_id |
Int |
The run ID for the workflow in the Automation Engine. It gets set when the execution starts and is empty before. Important! Run id and execution id refer to different concepts. The run id is generated by the Automation Engine when the execution starts. The execution id is the key that uniquely identifies a deployment in CDA. |
|
Yes (Only when not empty) |
|
system_needs_manual_start | Boolean | Flag whether the execution has to be started manually. Defaults to False. | |||
system_owner |
Reference [type=Member] (to be referenced as: system_owner.system_name) |
The execution owner. | |||
system_workflow |
Reference [type=Workflow] |
Reference to the workflow to be executed | |||
system_deployment_package |
Reference [type=Package] |
Reference to assigned (deployment) package |
|
|
|
system_deployment_profile |
Reference [type=Deployment Profile] |
Reference to the assigned deployment profile |
|
|
|
system_application |
Reference [type=Application] |
Reference to assigned application |
|
|
|
system_environment |
Reference [type=Environment] |
Reference to assigned environment |
|
|
|
system_queue |
Reference [type=Queue] |
The queue the execution is assigned to. | |||
system_queue_run_position | Integer | Position of the execution within a queue run. Only relevant if the execution is scheduled in a queue. | |||
system_archived | Boolean | Flag indicating whether the entity is archived or not. | Yes | ||
system_install_mode | String |
Install mode: Possible values: Default: |
|||
system_queue_run |
Reference [type=QueueRun] |
The run of the queue the execution is scheduled in. | |||
system_manual_confirmer | Reference [type=User/Usergroup] | The user/group needed to manually start the execution. Only if system_needs_manual_start is True |
|||
system_report_url | String | Absolute URL to fetch the report definition. Can be used to fetch the report. Call has to be authenticated. |
Export
Export available, system_id is used as identifier.
Reporting
Main type is available in reports.
All system properties are available in reports.