Easy way to add a checklist to a task to help 'guide' fulfiller

[Dan R3]

I'm looking for a way to add a set of checkboxes on a Catalog Task ticket so when the fulfiller works the ticket, they are required to check each box of the checklist, before the system let's the fulfiller close the ticket. Essentially this is a checklist to make sure they hit all the required tasks to process the request, before they close the ticket.

I've been able to get this working using some scripts that validate how many checkboxes are set to TRUE on the form, and if it doesn't meet the value I specified, it throws an error. 

The problem with this method is that the script applies to all task tickets that open that are attached to the RITM. 

At this point, I have 2 different sized checklists, for 2 different tasks that spawn off the same RITM. Is there an easier way to make these checklists "selection required mandatory" for each ticket.

a bit more info:  I did some investigating and many people suggest setting the "label" of the checklist to mandatory which is supposed to make the checklist mandatory as well, however I have been unable to achieve this.

Essentially, the question "in a nutshell" is: How do you set 'require selection' for checkboxes that are only visible on the catalog task, without having them also show on the service portal?

Let me know if I can provide more information, thanks in advance for anyone who can attempt to resolve this!

Dan R

[ty_roach]

You want Checklist Pro, a ServiceNow store app.

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.

[Pooja Gupta]

Is it possible to add multiple checklist to a record using Checklist Pro?