How come that a field in catalog client script is setmandatory false, gets true in a RITM/task

[stephaniede]

I wanted to know the reasons why a field at the client site is not mandatory anymore, (has a none), because of another field (single line text)  has a value. But at the ritm/task is mandatory again althought the other field is still filled with a string value. 

I'm looking for how to analyse it, know how could happen etc. And is this normal behaviour, because I forgot something, or not.

[aasch]

Hi,

since you're speaking of RITM/Task, I'm assuming we're in Service Catalog.

The usual places to look for field configuration on the Client Side in Service Catalog are:
- Catalog UI Policies
- Catalog Client Scripts
- mandatory Flag (Checkbox) on a Variable itself

Usually unexpected field configuration is the result of an unintuitive or non-obvious constellation of conditions.
For example developers might add Scripts to UI Policies, which can easily be overlooked when looking at the UI Policy. Or a UI Policy or Client Script might have unexpected negation logic.

If a configuration is RITM/Task-specific, you could check where the suspected UI Policies or Client Scripts are supposed to run.
You can individually make UI Policies and Client Scripts apply to the Catalog Item Form, the RITM Form or Catalog Task Form. See the "Applies on [...]" checkboxes.

Best regards
Aaron