Unable to see variables in the Catalog Task

[Nilanjan1]

Unable to see catalog variables for an ITIL user but visible for an admin user. It was working prior to upgrade of the ServiceNow instance to Rome. I have followed the following -- Removed all the variables from the slush bucket of the flow designer and update the type === Global in the variables section. I am not sure what changed to see this behaviour?

[Maik Skoddow]

Hi

unfortunately it is not really clear what your issue is.

Please provide more details and especially screenshots, so we can better understand your situation and help you accordingly.

Especially explain why you are mentioning the Flow Designer as there is no relation between the Flow Designer and displaying catalog variables on a catalog task.

Kind regards
Maik

[Nilanjan1]

Hello Maik, 

There was a business rule that was causing the issue. 

[Maik Skoddow]

Does this mean, the problem is solved?

If so, please mark your own answer as correct so other users can see the solution in case they are searching the Community for similar cases.

Kind regards
Maik 

[shloke04]

Hi,

Couple of things you can check for this issue:

1) On the Variable Form itself there are Field such as Read Roles, Write Roles as shown below. Check if any Roles are added to the variables or not.

2) Check if there are any Client side script written can be a Client Script , Catalog client script or a Catalog UI Policy or UI Policy which might be hiding it on the form.

Also Can you confirm where are you trying to check this? Is this on a form or on a Report?

If it is a form try the above steps , In case this issue is for a Report where variable are not visible then there is a known issue as well reported in HI which is reported due to a Read ACL existing OOB. Follow the link below for resolution:

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0826409

Also refer this as well

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0956915

Hope this helps. Please mark the answer as correct/helpful based on impact.

Regards,
Shloke