Best Practice for Adding a Checklist to SCTASK Without Creating New Fields

[saint]

I have a catalog item where multiple groups work on a single task. Each group has a checklist of actions they need to complete before passing the task to the next team.

I’d like to display a checklist on the SCTASK form that each team can interact with (e.g., check off items) before moving forward. However, I want to avoid creating additional fields on the SCTASK table.

Is there a recommended best-practice approach to achieve this functionality? Any suggestions or alternative solutions would be greatly appreciated.

[RaghavSh]

You can create variables on that catalog item and make them only visible on sc_task (hidden for ritm and catalog item) using catalog ui policies/catalog client scripts.

In this way you will not have to create fields on table.

[saint]

Hi @RaghavSh ,

I’ve created a variable that should only display on the Catalog Task and Requested Item. However, all variables appear as read-only in both places. I checked the out-of-box client script “Variable Editor Readonly”, and both scripts are inactive. I also don’t see any ACLs applied.

How can I make this variable editable? I tried using a Catalog Client Script for this item, but it’s still not working. Where else can this be configured?

[RaghavSh]

I think even if the client script is active you can make the variables editable using catalog UI policies.

Refer: https://www.servicenow.com/community/developer-forum/make-variables-editable-on-ritm-form/m-p/149775... 

Try changing the order of your UI policy and run it only on RITMor SCtask as per your need.

[lauri457]

I would recommend looking into separating the single task into multiple sequential tasks instead of multiple teams juggling a single task. Consider e.g. reporting benefits or how the transition of work items from one team to another works in a single task scenario.

However you can have a look at the checklist formatter . Tables are [checklist], [checklist_item] and [checklist_template].