Is there a way to introduce mandatory checklist in a catalog Task without any customization?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-16-2024 01:52 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-16-2024 07:55 AM - edited ‎06-16-2024 07:56 AM
No, out of the box there is no possibility to make checklists mandatory. To be honest, I would not recommend doing so even if there were a technical possibility. Typically, trying to force people to use some functionality with technical measures only creates resistance. If you make checklists mandatory, some people will simply start checking off the items without actually performing the corresponding action, which is not the result you want to achieve.
Blog: https://sys.properties | Telegram: https://t.me/sys_properties | LinkedIn: https://www.linkedin.com/in/slava-savitsky/

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-17-2024 11:29 AM
Dee255 That depends on your definition of a "Check List." BTW (Slava) requiring fields is simply a part of process and what SNC is all about, i.e., forms driven workflow.
I would not want to modify the sc_task form, which is where I'm guessing your question is coming from. Add your required fields as variables on the cat_item. These could be "checkboxes." Hide them on the cat_item. Set them as mandatory on the sc_task with catalog ui policy or client script (assumes you have variable editor as field on form). If you want greater fanciness, use a Business Rule on the sc_task table to control when the variable is required and pop info messages, e.g., field must be populated before closure. Of course, this can get a little messy on the sc_task table as the BR has to be generally specific to the cat_item of the RITM.