Two ways of setting Tasks inactive, within a workflow, or directly on a task? what to use?

Discussion created by Harald_Heidinger_152 on Sep 2, 2016
Latest reply on Sep 2, 2016 by Harald_Heidinger_152
Basically there are two ways how to set a task inactive at all, but how to determine what to use in which situation.

Within an executable object (e.g. Workflow, Script, Job...) you do have the possibility within "Header" - Tab to set the Object inactive.

This function you can use, if you want to prevent any job from running at all. If it is scheduled or planned in any Scheduler, Workflow, Event... it will not start, since it is inactive. It will end with 

"U0007072 Activation of object 'SCRI.HEA.TEST.PREP' ended. Object is inactive due to definition."

You can use this if you want to avoid an object to be executed at all. e.g. you found a mistake in its definitions, or on target system the prerequisites are not given to run this task smoothly.

If you want a task just not be running in a workflow, you can set it inactive on workflow level, in that case, the object is not set inactive itself, but for the workflow it will be overleaped. In that case, ensure that the following tasks within the workflow can accept the inactive status as and OK status so it will run further.

Important notice: For a workflow it makes a big difference if a task is set inactive on workflow level or on object level. If you set an object inactive on object level, a earliest starttime within the workflow will wait until this starttime is given, and only then overleap the task. To avoid this, you have to set the task inactive on workflow level, so the workflow process will recognize the active-setting before waiting the earliest starttime.