Checklist template

[Pastupe]

Hello, is there any way how to control check list templates visibility ?

If user 'A' create checklist and save it as template, then also user B from different group have access to it and can use it and see it

We activated checklist functionality on GENEVA and we added checklist formatter to incident form.

Problem will occur when users start create checklict templates , list of available templates will rapidly increase as now users can see all checklist templates as indicated on the below picture - doesnt matter if you own checklist template or not.

I have tried to used ACL's but it doesnt limit number of items in the below list.

Any idea how to make items in the below list visible to users that own it or that are group members to which templates is assigned to ?, thank you

/Petr

[troyholmes]

I opened three separate enhancements

1. Checklist Template Sharing

2. Checklist Template Restrict to Table that checklist applies

3. Updating the Name on the Checklist instance table with the name of the Checklist Template so that reporting can be done against Checklist Instances and if the steps are getting completed

[garythomas200]

It looks link the Jakarta release has resolved the issue identified here.

[ty_roach]

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.