Copy of Catalog Item changes Checkbox Group to mandatory

Ron28
Mega Sage

I have a catalog item with a Checkbox group, in this group there are 3 variables/questions of which one is hidden. None of the variables/questions are mandatory.

To simplify the catalog item and remove some of the complex UI policies set, I am splitting the functionality of this Catalog Item. I created 2 new catalog items, both copies from the original catalog item. 
Using 'Try' (or in App Engine Studio using preview) of the original item shows a Checkbox group with 2 visible questions and neither are mandatory, nor is the label.

Yet do a 'Try' or 'preview' in either of the 2 copies, the Checkbox group has a red 'mandatory' mark. 

Looking at the catalog item variables, the Checkbox group has the mandatory property set to false. The 3 options in the group also all have their mandatory property set to false. I tried forcing the Checkbox label variable mandatory property to false in an onLoad client script but that doesn't fix it. 

I'm puzzled. Has anyone else seen this (on UTAH), or know how to fix this?

Thanks

Ron

1 ACCEPTED SOLUTION

I deleted the UI policies and that then showed the item no longer as mandatory. Creating new UI policies made it mandatory again (without me specifying that in the UI policy). 

Yes I could waste time on debugging it but I think it will be much quicker to create a new Catalog Item from scratch. This is clearly a bug in ServiceNow, I think they should fix it.
Ron

View solution in original post

4 REPLIES 4

Harish KM
Kilo Patron
Kilo Patron

Are there any UI Policies/client script set on variables or variable set? Follow the below link on how to debug variables

https://docs.servicenow.com/en-US/bundle/vancouver-servicenow-platform/page/product/service-catalog-...

Regards
Harish

Yes there are UI policies on 2 of the 3 variables. Thanks for the link.

You could debug and see which one is causing the issue.

Regards
Harish

I deleted the UI policies and that then showed the item no longer as mandatory. Creating new UI policies made it mandatory again (without me specifying that in the UI policy). 

Yes I could waste time on debugging it but I think it will be much quicker to create a new Catalog Item from scratch. This is clearly a bug in ServiceNow, I think they should fix it.
Ron