Executing Objects: The Activation Stage
Executable objects go through four stages during execution. The first one is the activation stage, which is a preparatory step in the execution process. During the activation stage very few things happen. This list outlines them:
-
The activation starts.
-
The object gets a runID. If the object is a Workflow, all its tasks are also activated and they get their runIDs.
-
The task is available and visible in the Process Monitoring perspective.
The following diagram illustrates the steps that a task undergoes during activation:
Note: If you log out (or if you close the browser window) while tasks are still executing and in the activation stage, those tasks will abort. This applies to tasks that were started by the user that is currently logged in. Tasks that you have started and that are already in another stage (generation, processing or completion) continue executing. A confirmation dialog prompts you to confirm that you want to log out.
Ways of Activating Objects
There are multiple ways of activating objects:
-
Through Workflows
-
Through Schedules
-
Using the Execute Recurring option
-
Through Job Groups
-
Using script elements such as ACTIVATE_UC_OBJECT or RESTART_UC_OBJECT
-
Through object configuration. Objects can be configured to activate in reaction to specified conditions.
Next Stage
When the activation stage has finished, the task enters the Executing Objects: The Generation Stage stage.
See also: