Issue
Determining if a variable is defined on the workflow or execution plan
Symptoms
- No variables on form
- Variable not visible
Resolution
In some use cases, a catalog item runs a workflow or execution plan that creates a catalog task. Sometimes the catalog task may not show all or any of the variables that were in the original item.
To troubleshoot variables that are not visible on a catalog task created from a workflow:- The variable or variables may not be included in the workflow activity that defines the task. Check by finding the WF activity that is creating the task inside the Workflow editor window.
The Variables on Task Form slush bucket appears on the form, with Available and Selected variables listed. The variables that you need to see must be in the Selected list.
Note the following:
- Changing the slush bucket does not change already created tasks's variables.
- The change is applied to new tasks created after the change.
- If you have multiple tasks in a workflow, you will need to do the same for all of them.
- Incorrect formatting on the catalog task variables will be caused by missing out the containers in the selected slush bucket.
To troubleshoot variables that are not visible on a catalog task created from an execution plan:
- The variable(s) may not be included in the execution plan that is creating the task. Check by finding the execution plan that is creating the task.
The related list contains the Execution Plan Task related list.
Note the following:
- Changing the Available Variables list does not change the variables on previously created tasks.
- The change is applied to new tasks created after the change.
- A related list on this task is called Available Variables.
- The variables that you need to see must be on the Available Variables list.
- If you have multiple tasks in an Execution Plan Task list, you will need to do the same for all of them.
- Incorrect formatting on the catalog task variables are caused by missing out the containers in the list.
