This Specification Flow Task starts an application and will pass arguments into it on execution.
DriveWorks will pause/ wait while the application is running.
When the Task is executed it will either wait for the application to finish itself, or if the timeout is reached first then the Task will terminate the application.
The Task will execute on the host machine of the DriveWorks application from which it is being run.
For example:
If the Task is triggered from a client using the web theme, the Task will execute and attempt to run the application on the DriveWorks Live server machine.
Please take care to ensure the Task only executes the intended application, particularly when dynamic rules can result in different applications being started.
| Property Name | Description |
|---|---|
| Title | Changes the Title (not the name) of the task. |
| Application | An application with which to start a process. |
| Working Directory | The working directory for the process to be started. |
| Arguments | A single string containing the arguments to pass to the target application. |
| Timeout | The amount of time, in seconds, to wait for the associated process to exit. Set to 0 for no timeout and wait for the application to exit itself. |
When this Task is added the properties are static. To be able to build rules on a static property see How To: Change A Static Property To A Dynamic Property.
| Property Name | Rule | Meaning |
|---|---|---|
| Application | python3.exe | Will run the python3.exe |
| Working Directory | C:\Python\HelloWorld | The working directory the application is run from. |
| Arguments | HelloWorld.py | The arguments to pass into the application. |
| Timeout | 10 | DriveWorks will continue after 10 seconds unless the application has already exited. |
This task has different types of Outputs. For more information about Outputs see Specification Macros Task Node.
Outputs are only available within Specification Macros. Currently Outputs are not available for Specification Flow.
This task supports Status Outputs. These can be used to perform different actions depending on what the status outcome of the task is. For more information see Status Outputs in the Task Node Outputs section of Specification Macros Task Node.
The status output navigation is as follows:
Success
Success with Warnings
Failed