Last updated
Last updated
If you do not use ExecutionTask
you can live with the defaults - as I have done for four years. Skip this page!
Recently I came accross a script that used the following code with ExecutionTask
:
A script is hosted in a process. This process can be a sub-process of another process(es).
For example:
Main Process calls (Level -2)
subProcess01 routes to (Level -1)
subPr.subProcess_01_01, where the script runs on! (Level 0)
What you need to undestand is, that each process execution has its own ExecutionTask
object with different properties, and you can traverse up the hierarchy using the getParent()
method.
import msPro.scriptease.*
// Important
Process Id
(=Component Id
) are set to a randowm Guid by default. This can be overridden in the ProcessExecutionProperties
constructor.
StartTime
and executionId
are set a atuomatically.
The EXECUTION_ID, PROCESS_ID, PROCESS_NAME
refer to the script's (hosting) process.
Support for main process, sub processes and process routes