Catalog Variables not visible on Task
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-30-2023 01:45 AM - edited 10-30-2023 01:47 AM
Hi ,
I have created few variables on catalog initially and created a custom flow using flow designer with that variables -. Create catalog task action in the flow designer works fine and displays all the variables created initially.
Now again i have included few more variables and updated the flow but the new variables are not visible on the catalog task even after adding all the variables from slush bucket (selected all from available to selected) in the Create Catalog Task action on flow designer.
I need to make the new variables visible only on the catalog task and not n RITM.
So i tried making hidden variables on the catalog initially and created a UI policy to make it visible on the task.(Using 'Applies on Catalog Tasks checkbox' enabled on Ui Policy). but it didn't work as expected.
1. How to hide the (few) variables on RITM and make it visible only on Task
2.How to make all the variables visible on TASK .
Thank you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-01-2023 05:42 AM
@Community Alums
Definitely some issue with some configuration or script
Since you said when it's populated it's shown
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-30-2023 02:31 AM
However, sometimes this occurs due to the field being mandatory or not in its internal settings.
Check if the field was already defined as mandatory when it was created. If so, remove the internal condition and configure the field mandate via UI Policie.
I've had situations like this to resolve and the way I resolved it was like this.
Removing the internal field configuration from mandatory and then created a police UI setting this field as mandatory.
I don't know why this happens, but it seems that one form interferes with the other.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-30-2023 02:55 AM
@Romario DPO , When i try to set mandatory on Task it is not visible.
I need these few variables empty in the task when the task is created and the fulfillment team need to fill and close .
When i try to add default value 'xxx' to the field it is populating in the task.
Any other scenario like setting mandatory on task using UI policy also not working .
Any OOB option to make the empty variables hidden on Task ?
Please guide me to solve this issue .
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-30-2023 02:59 AM
When I encounter situations like this, I control it via script and UI police.
Where I take the desired field, create a police UI controlling visibility and include a client script on change. where if the value of the xyz field is "something" the field is visible and if it is not it is invisible.
Have you tried using client script on change?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-01-2023 05:35 AM
@Romario DPO , Sorry, could you please explain more with the workaround .
Should i need to create a UI Policy and Onhange client script both ?