- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-10-2019 08:50 AM
Hi All,
Is there a way to restrict checklist from adding and removing the checklist_items on catalog task?
Only User with Admin role should able to add and delete checklist_items.
I tried using ACL'S but unable to achieve the expected output.
Any suggestions would be helpful.
Thanks and Regards,
Meenal
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-10-2019 09:00 AM
Hi Meenal,
OOB checklist_item can be added to any form that has checklist layout addef it the logged in User is created by for the ticket. If required you will have to modify ACL of type write on checklist_item table that has a scirpt that makes it works for created by User. All you can do is comment the script & make sure the ACL has Admin overrides marked as true.
Thanks,
Jaspal Singh
Hit Helpful or Correct on the impact of response.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-10-2019 10:27 AM
Hi Dharani,
Thank you , This works fine but the users with ITIL role is unable to check the checkbox.
How this can be achieved ?
Thanks and regards
Meenal
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-27-2019 09:18 PM
The problem with the OOB checklists is that they are unreliable, meaning, people can change the content of the checklist item after the fact, add items, delete items, change items. There's also no guarantee that the same checklist will appear for same situation. There is no way to restrict who can edit the checklist or when it can be edited (like do you really want people changing checklist responses after the record has been closed).
Enter Checklist Pro. We built Checklist Pro to solve all those problems and more. Checklist Pro application administrators can define when checklists get created and associated with records in a table (any table - not just those that extend TASK), when these checklists can be edited, when the associated record is considered "closed" (and thus should prohibit further checklist updates). We even added the ability to define "Required" checklist items that allow enforcement, thereby preventing a record from closing unless the required items are completed. We've built convenience Database Views to go with the most common checklist tables, which include TASK, SYSAPPROVAL_APPROVER, CMDB_CI.
They work in the Service Portal as well as in the Classic UI.
They'll work with other Scoped Applications (like HR or SecOps or even custom scoped apps & tables).
For more information contact TyGR LLC or goto our youtube channel to see it in action.
Also - besides the classic Checkbox Item, Checklist Pro allows you to include various data types, including Textbox fields, Date, Integer, Custom Choice Lists and Reference fields.