Why Checklist Pro?
The ServiceNow platform is an amazingly powerful tool that follows ITIL principles and provides a myriad of features and services in areas such as ITSM, ITOM, ITBM, HR, Security Operations, GRC, and more. Besides the "out of the box" (OOB) capabilities, this platform was built to allow for easy customizations suiting each organization's business needs. As such, new features and business workflow processes can be quickly built and ServiceNow even provides a native checklist application to enhance common tasks. The idea of a "checklist" is familiar to everyone, we use them for personal reasons like when we go grocery shopping or are packing for a vacation, etc. We can use them at work as well (e.g. like collecting keys from an employee being offboarded and cancelling any travel or training classes scheduled for them). Having a checklist helps augment the functionality within ServiceNow workflows, guiding the team through what may potentially be many sub-steps. They can also help track work performed in other systems or for enforcing that best practices are followed. It may also be that not all of the instructions in a task are required and knowing which of these tasks were performed (or not) is important for audit or evidence gathering purposes. The problem with native ServiceNow 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 in the same situation. There is no way to restrict who can edit the checklist or when it can be edited (e.g. do you really want people changing checklist responses after the record has been closed). There is no concept of "required" vs "optional" checklist items. Enter Checklist Pro, a ServiceNow Store Application from TYGR LLC a Premier Technology Partner and Public Sector Partner. 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 can be placed in Catalog Items, Record Producers as you submit your request, or placed on any record in ServiceNow.
The same Checklist can be shared across multiple different records (think group approvals) where everyone sees and uses the same checklist.
A Checklist can have nested Checklists such that as one item is completed, it can reveal a whole new set of Checklist items
We even have built-in Checklist Item validation logic and allow end users to build their own item validators.
Our Checklists works with other Scoped Applications (like HR or SecOps or even custom scoped apps & tables).