Checklist - check for completion before status change allowed ...

Zod · ‎08-22-2017

Hi there,

we'd like to use the checklist templates on the incident form.

It would be quite good to force people to confirm (when trying to provide solution = state change) that there are still open checklist items ... .

Anything to be reused out there?

I think a client script on submit should be the most reasonable way ... other opinions?

Raju Koyagura · ‎08-22-2017

Script Include:

var Test = Class.create();

Test.prototype = {

initialize: function() {

},

isChecked: function(id){

var gr = new GlideRecord("checklist");

gr.addQuery("document", id);

gr.query();

while (gr.next()) {

var gr_checkListItem = new GlideRecord("checklist_item");

gr_checkListItem.addQuery("checklist", gr.sys_id);

gr_checkListItem.addQuery("complete", false);

gr_checkListItem.query();

if (gr_checkListItem.next())

return false;

else

return true;

}

},

type: 'Test'

};

BR:

(function executeRule(current, previous /*null when async*/) {

var res=new Test().isChecked(current.sys_id);

if(res)

gs.addInfoMessage("Checklist is reviewed.");

else

gs.addErrorMessage("Please review the checklist.");

})(current, previous);

View solution in original post

ty_roach · ‎11-27-2019

Checkout Checklist Pro.

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.