Catalog Variable Showing Mandatory on RITM Without Any Rule

[neehas710]

Hi Team,

I am facing an issue with a catalog variable behaving as mandatory even though I have not explicitly set it as mandatory anywhere.

Scenario:

• Catalog Item is in Global scope

• Variable is in Request Management scope

• Variable type is Checkbox

• “Mandatory” and “Selection Required” are unchecked

• No UI Policy is setting it mandatory

• UI Policies only control visibility on RITM (no mandatory actions)

Issue:
The variable is still behaving as mandatory on the RITM form , and the form does not allow submission unless it is checked.

What I have already tried:

• Verified all Catalog UI Policies and UI Policy Actions

• Checked and deactivated Catalog Client Scripts

• Cleared cache and hard refreshed

• Confirmed no mandatory setting on the variable or variable set

Question:
Is there any known behavior where Checkbox variables (without default values) act as mandatory on RITM/Workspace?
Or could there be any hidden validation (OOB behavior, backend constraint, or workspace-specific logic) causing this?

Any help or pointers would be appreciated.

Thanks in advance!

[Tanushree Maiti]

Hi @neehas710 ,

Check your onSubmit catalog client script which is validating if Checkbox is true or not.

[Ankur Bawiskar]

@neehas710 

any onSubmit script is doing?

Did you create a fresh checkbox variable and deactivate the older one and see what's the behavior?

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏