Service catalog container Start mandatory fields
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-11-2016 07:25 AM
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?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-11-2016 07:58 AM
Hi,
For this type, I have created a OnChange client script like this.
In the logic of hiding, Iam making them not mandatory as well. In the script of dispalying I am making them mandatory.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-11-2016 08:01 AM
Could you please share the sample script if possible?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-11-2016 08:02 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-11-2016 08:05 AM
Hi Kailash,
The best way to proceed is only through catalog UI Policy itself or you can also proceed with catalog client script. But, as conditions are changing for each record. It is advisable to proceed with Catalog UI policy.
Click "Like" & "Helpful" if you find it is useful.
Abilash JS