Can't use Workflow Variables in the Workflow's tasks if underlying object set to no variable inheritance
Article ID: 84412
Updated On:
Products
CA Automic Workload Automation - Automation Engine
Issue/Introduction
Error Message :
N/A
Even though conditions are a part of the Workflow, variables of a workflow can't be used in preconditions and postconditions of a task of that Workflow, if the underlying Object is set to no variable inheritance.
N/A
Even though conditions are a part of the Workflow, variables of a workflow can't be used in preconditions and postconditions of a task of that Workflow, if the underlying Object is set to no variable inheritance.
Cause
Cause type:
Configuration
Root Cause: Conditions are executed in the context of the task. If the Task does not inherit values from its parent, they can not be used in Conditions of that task.
Configuration
Root Cause: Conditions are executed in the context of the task. If the Task does not inherit values from its parent, they can not be used in Conditions of that task.
Environment
Release: AUTWAB99000-11.0-Automic Workload Automation-Base Edition
Component:
Component:
Resolution
Conditions are executed in the context of the task which means that all variables of the task can be used.
All system-variables, such as &$RUNID#, &$NAME#, etc. will be set with the values of the task.
So if the task does not inherit the object values from it's parent, they cannot be used in conditions.
Fix Status: No Fix
All system-variables, such as &$RUNID#, &$NAME#, etc. will be set with the values of the task.
So if the task does not inherit the object values from it's parent, they cannot be used in conditions.
Fix Status: No Fix
Additional Information
Workaround :
N/A
N/A
Feedback
Yes
No
Powered by
