best practice to create mandatory fields is UI policy why?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-06-2016 04:10 PM
I heard that best practice to create field as mandatory is UI policy and not client script. Why is it so?
Can you please let me know performance issues if any?
Thanks
Sangeetha

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-06-2016 04:15 PM
There aren't any performance issues. The main reason is that (unscripted) UI Policies are easier to maintain the client scripts. For potential less-technical people coming along after you, they don't have to know scripting. It's far easier to build a condition using the condition builder and point to certain fields than it is to write script and get wrapped up with syntax, classes, methods, properties, etc.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-22-2019 10:33 PM
Hey Chuck,
I want to make short description field mandatory on problem form, it can be done by dictionary override and ui policy can you please tell which one should be preferred ?
Regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-25-2019 02:35 AM
Just UI policy will be enough to make description mandatory.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-25-2019 02:56 AM
To make field mandatory, visible or read only always use UI policy.
Thanks!