Service catalog container Start mandatory fields

[kailashthiyagar]

I m working on Service catalog. I have multiple container start and each has a bunch of controls which are mandatory.

I have drop down and which has multiple request types. On select of one request type, i show the particular set of container start and on select of another request type , i will show different set of container start. This works fine..

But on submit, it takes into account of the hidden container start controls and complains that "mandatory fields are missing"

Should i create UI policy at control levels rather than at container level? If its the only option, for each request type selection, i have to add 20+ catalog UI policy action to show the controls and make it mandatory..

Can you please help on this?

[gemini17]

Hey Kailash:

You can try to hide or show different containers, based on one of the fields in the preceeding container.   That will work fine.

Hope this helps.

P.S. Hit it correct as you see the impact.

Kind regards

Danny Raj

[kailashthiyagar]

Hi Danny, if i do it at the container level, it doesnt help much.. the hidden fields still causing issues

And from the overall discussion, it sounds like we need to use Catalog UI policy as it is the best for Catalog Item. And also i shouldnt use the Container start approach. I have to go with making individual fields visible on change of request type(controlling field),

Either i use UI policy or the script, i have to do things at indiviual control/item level and not at the container l

[gemini17]

Hey Kailash:

I agree with Abilash, Wiki recommends using UI policy as the best practice, wherever possible.   that does not mean, you can not use catalog Client Script at all.   Since you have to create so many UI policies, you will have conflicts, unless you wisely use 'Reverse if false' condition true or not for each UI policy.   Accordingly, I would go with the catalog script suggested by SriKanth.

Thanks

Danny Raj

[balsu333]

FYI   Why UI plocies.