top of page

In the “How Does Checklist Pro Do It?” blogpost, we talk about how Checklist Pro creates a Checklist. We discuss two options:

  • Programmatically” - through a Checklist Pro API call.

  • Conditionally” – when someone browses to a record where a checklist is defined.

Since the above-mentioned blogpost covers the “Conditionally” created option, this blogpost will cover the “Programmatic” option.

We will also discuss why you may want to do one vs the other.

In prior examples, we created a “Cascading” checklist that would appear conditionally on an incident table if the incident was in a “New” or “In-Progress” state and if the category was “Inquiry / Help” and the subcategory was “Antivirus”. Under those conditions, if you navigated to a record where those conditions were true, then Checklist Pro would create a checklist (if one did not already exist).

However, if we wanted to simply create that “Cascading” checklist on an incident (any incident we wanted), then we would use the Checklist Pro API library to programmatically create our checklist.

Creating a Checklist Programmatically

In this example, our “Cascading” checklist is in a Checklist Configuration record called “INCIDENT – Cascading Checklist”.

In this Fix Script, we’ll create the checklist, adding it to some open incident record.

WARNING – if there is already a checklist associated with a particular record, this API call will add an additional checklist, so you may want to add logic to check if there is an existing checklist. See the modified code example below:

Now, when we visit the incident that the checklist was added to, we see the checklist there. We forcefully created the checklist on our desired record even though it does not have “conditions” matching that which would be required for it to be created by the Checklist Pro engine.

So, what are the advantages and disadvantages of creating checklists “Conditionally” (Checklist Pro Engine) and “Programmatically” (Checklist Pro API)?

A common situation for checklist creation is that you need to be sure the checklist exists even if nobody has opened the record where you want the checklist to appear. That could be the case for a checklist on an approval request or some task from a workflow.

Creating a checklist programmatically (via the API), would guarantee the checklist is on the record. If your checklist had “required” items that were assumed to be completed later in the workflow (for processing), then programmatically creating the checklist items may be the way to go. This would prevent someone from just closing a task (from the list view) or approving a request (again, from the list view without ever actually opening the record) and then not having the checklist exist because the record was never opened.

110 views0 comments
  • Writer's pictureTy Roach

Version 1.9.11 of Checklist Pro is now available. This version has several new and interesting features as well as important bug fixes:

New Features

  • Hide and read-only. Provides a way to selectively hide a checklist item (and all of its descendant items) or make them read-only based on 8 different built-in functions:

  • In Group

  • Not In Group

  • In Department

  • Not In Department

  • At Location

  • Not At Location

  • Is VIP

  • Is NOT VIP

Also includes option for hiding or making read-only based on condition builder

queries against the record that the checklist is on. Click to Watch Video.

  • CLP License Database View. Interested in knowing if a user record is a "Fulfiller", "Business Stakeholder" or "Requester", the new "CLP LIcense" Database View (x_tygr_check_dv_license) joins the User Table, with the License Role and the User Role table so that you don't have to (because every DB View you create, counts against your alotted custom table count - so we're doing you this favor)!

· Additionally, we added two new API calls to a new script include:

x_tygr_check.LicenseUtil().getUserLicenseType (user_sys_id)

o You pass the sys_id of the user and the function

returns “Fulfiller” | “Business Stakeholder” | “Requester”, depending on what

that user is.

x_tygr_check.LicenseUtil().isUserLicenseType(user_sys_id, license_type)

o valid license types are “Admin”, “Approver”, “Business Stakeholder”, “Fulfiller”,


o returns “unknown” (if user cannot be found) | “true” | “false”.

  • Checklist Overview Dashboard. Reports showing any open Checklist Records assigned to you, unassigned open Checklist Records assigned to your groups and all open Checklist Records by group.

  • Improved Checklist Record. We added the "number", "state" and "short description" fields to the Checklist Record Portal page. The “Completed” button now says “Complete” and has hover-over text. The “Incomplete” button has been changed to “Cancel” and includes hover-over text. An instructional blurb was added under the “Assigned To” field to inform users that the action buttons will appear once a user is selected and the “Save” button is pressed.

  • Added Validation Routines. URL, Zip Code, IP address (ipv4 and ipv6), Is Date on Weekend, Is Date on Weekday.

  • Improved Logging.

Bug Fixes

  • Textbox checklist items would lose focus 1.5 seconds after you stopped typing.

  • Checklist Configuration condition builder corrected issue with “^NQ” (logical OR) queries.

91 views0 comments
  • Writer's pictureTy Roach

Checklist Pro is a no-code / low-code ServiceNow platform enhancement tool for your development staff (pro and citizen developers alike) to expand their options for providing optimal solutions on the ServiceNow platform. We have customers in both commercial and public sectors.

We are happy to provide product demonstrations and trial/evaluation access to our Checklist Pro ServiceNow store application.

TYGR LLC is a Premier ServiceNow Technology Partner and Public Sector Partner:

Checklist Pro in the ServiceNow App Stores (Federal & Commercial)

· Checklist Pro - ServiceNow Store (Commercial)

· Checklist Pro - ServiceNow Store (Federal)

Checklist Pro Articles

· Why Checklist Pro

· Checklist Pro: one of 22 ServiceNow Essential Applications

· Options to Help Reserve ServiceNow Capital

· Prevent "Requester" Users from becoming "Business Stakeholders"

· Checklist Pro Managing Oracle Financials

Checklist Pro Video Channel

· Creating your first Checklist

· Checklists on Service Catalog Items

· Terms of Use Capability

· Checklist Pro vs Out-of-the-Box Checklists

· Full Checklist Pro Playlist

Contact Info

· Technical Support:

· (Sub)-Partnership Opportunities:

Supported User Interfaces

  • UI16 (Jelly-based forms)

  • Service Portal (AngularJS pages)

  • Future releases will support Workspaces.

Easy form-based UI for configuring checklists.

  • Unlimited number of checklists

  • Unlimited number of users / groups

  • Unlimited custom extensions

Checklist can appear on any record in ServiceNow.

  • Most commonly on task records and approval records

  • Any record in service now (custom or global scope)

  • Even supported on record producers and catalog items

Variety of checklist item types

  • Checkboxes

  • Textboxes

  • Numbers

  • Dates

  • Customizable choice lists

  • Reference records

  • HTML objects

Support for "Required" checklist items (as well as optional)

  • Prevents closure of checklist-hosting record until all required items have been completed.

Checklist Item Validation

  • 18 built-in validations

  • Custom built validations easily added.

Hide or Read-only Checklist Item Override

  • 8 build-in functions

  • Custom built functions easily added.

Allow for cascading checklists.

  • Checklists within other checklists (as one item completes, other sub-items are exposed)

Checklist Governance

  • Define when a particular checklist is created.

  • Define when the checklist is editable.

  • Define conditions for when the hosting record (holding the checklist) is considered closed.

  • Customizable "Processing" button to allow for special checklist processing operations.

  • OOB - configurable option for displaying alerts and triggering workflow events.

Shareable Checklists

  • The same checklist accessible across multiple ServiceNow records

  • Example: Group Approval (individual user approvals can all refer to the same checklist)

ServiceNow Subscriber License Saving Options

  • Built-in “Terms of Use” workflow + checklist for securely capturing attestation of rules of behavior without misusing (over-using) Approvals or Tasks.

  • Generic Checklist Record accessible by free “Requester” type users for Task replacement within Flow Designer and legacy Workflows.

No-Code Functionality

  • Checklists Pro works with Platform UI ("classic" forms, UI16) and Service Portal

  • Add a checklist to a record (table) using condition builder.

  • Checklist can be added to any table in ServiceNow.

  • Supports Record Producer and Catalog Item input request forms too.

  • Determine who can edit the checklist using condition builder.

  • Determine enforcement of required checklist items on a record using condition builder.

  • Enforcement of required attachments (with configurable regex-based naming convention checks)

  • Create a shared checklist based on reference fields on a table.

  • Add a processing button to a checklist using condition builder.

  • Invoke a user defined workflow event upon button click.

  • Configurable HTML header before checklist items

  • Cascading checklist (i.e., checklist within a checklist)

  • Variety of Checklist Item types

  • Checkbox, HTML, choice, number, reference, date, text

  • Checklist item validations

  • 18 pre-built validations and growing.

  • Hide / Read-only checklist item override options.

  • Condition builder and built-in functions.

  • Generic "Checklist Record" allowing for ServiceNow Business Stakeholder and Fulfiller subscription reduction options.

  • Legacy Workflow for convenient drag-n-drop into workflow

  • Flow Designer option for drag-n-drop into a flow.

  • Email notifications for creating and re-assignment of Checklist Record.

  • Service Portal Main Menu item for showing Checklist Records assigned to you.

  • Pre-built "Terms of Use" checklist and workflow / flow

  • All checklist item data accessible and usable in out-of-the-box ServiceNow reports and dashboards.

  • Database Views for useful platform and commonly occurring business use cases.

  • CLP CI: Joins CMDB and Checklist Pro Items tables.

  • CLP Approval: Joins the Approval and Checklist Pro Items tables.

  • CLP CHG: Joins the Change Request and Checklist Pro Items tables.

  • CLP CLA: Joins the Checklist Pro Record and Items tables.

  • CLP License: Joins various ServiceNow tables allowing for determining the type of license for any ServiceNow user.

  • CLP RITM: Joins the Requested Item and Checklist Pro Items tables.

  • CLP Task: Joins the Task and Checklist Pro Items tables.

Low-Code Functionality

  • Customer extensible Checklist Creation functions.

  • Customer extensible Checklist Editing functions.

  • Customer extensible Checklist Sharing functions.

  • Customer extensible Checklist Closed Record handling functions.

  • Customer extensible Button Processing functions.

  • Customer extensible Validation functions.

  • Customer extensible Hide and Read-only functions.

  • Checklist Pro API library, for programmatic access to internal checklist utilities

  • Create a Checklist

  • Copy a Checklist

  • Is Checklist Item visible.

  • Is Checklist Item editable.

  • Various Get/Set Checklist Item value functions.

184 views0 comments
bottom of page