Task not showing Variable that is in a Variable Set

[Vlad_Rozic]

This may be a very easy fix for some, but I'm a bit confused by this and didn't seem to find an answer through my search..

Currently in our Service Catalog I have created a bunch of catalog items.. some of them I have set to use a single Variable set that contains one multi-test box variable.

What I'm finding now is that when these particular catalog items are filled out and submitted, the information placed in that variable shows fine within the RITM ticket, but does not show in the subsequent task.

This is making it difficult as then the person who is taking ownership of the task at hand has to search the RITM for the information placed in my the requester..

I have tried to adjust the title of the Variable, as I thought maybe the variable itself should be a different name than the Variable set.. but this doesn't appear to have made any difference. I've also looked to make sure its not just a View issue.. every view lacks the Variable info.

What am I missing here??? The other catalog items don't display this behavior, so I'm sure its on account of this particular variable set configuration..

[shabaab_mazhar]

Under the Workflow when the Catalog task is defined the variables can be added to the list to show by dragging them on the right side of the sluch bucket. If you have already defined then to show in the WF and is not showing would like to see if there are predined client scripts that is hiding those variables on the form.

[Vlad_Rozic]

Thank you for your help! This appears to be resolved now.. I will remember from now on that the workflow needs the variable added. Much appreciated 🙂

[Vlad_Rozic]

I see now what you mean.. I was not aware that the variable must be selected within the Category section of the workflow (Another tech has been the person looking at the workflow more than I have been)

I have gone in and added the variable in question to the listing as you suggested. I will wait now to see if the info gets populated properly with the next ticket that is submitted.

If not, yes, I think a client script could be the issue.. we only have 2 that are set to "true" within the Task form.

[TJW2]

You can mark the variable as 'GLOBAL' which will make it appear on all RITMs and Catalog Tasks it is associated with. This eliminates the need to 'declare' it in the slushbucket on the Catalog task with in the workflow. You may have to personalize your variable form to show the 'Global' checkbox.