The Delay Macro Timeout task will delay the period before the timeout prompt is displayed on any other, potentially long running, tasks.
|Delay Time||The amount of time, in seconds, to delay the prompt for Macro abortion (relative to the time that this task is ran).|
|Title||Changes the Title (not the name) of the task.|
Looping or nested Macros in DriveWorks have an inbuilt timer that will ask the user whether to continue or stop the execution of the looping Macro after 20 seconds.
This is to ensure that DriveWorks returns control to the user IF the Macro is caught in an infinite loop (Hangs) or a looping Macro in DriveWorks is looping indefinitely (i.e. if the loop Limit Value is never reached).
In some cases it may be expected that looping Macros take longer that this default time (20 seconds) to run, in which case, the timeout period can be temporarily changed using this task.
This task will allow a delay period to be defined when running other tasks that have the potential to trigger the default timeout period in DriveWorks.
Triggering the delay
The Macro timeout will be triggered when DriveWorks executes a Macro. Therefore the Delay Macro Timeout task should be the first task that appears in the list of tasks within a Macro.
To increase the timeout on a Specification Flow Event, Transition or Operation a Run Macro task should be added to the Event, Operation or Transition. This Run Macro task then runs a Specification Macro that contains the Delay Macro Timeout task.
When this task is added the properties are static by default.
See How To: Change A Static Property To A Dynamic Property to enable rules to be built on these properties.
|Property||Example rule||Example result||Meaning|
|Delay Time||2 * DWVariableNumberOfTasks||With the variable NumberOfTasks equal to 10, this rule would return 20.||DriveWorks will increase the timeout period for 20 seconds.|
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 with Warnings
Failed (One of the following occured)