Flow designer - adding checklist template

[Sri29]

Is there a way to add checklist template as part of flow designer action. I come across a similar post (https://www.servicenow.com/community/itsm-forum/flow-designer-adding-a-checklist-to-a-form/m-p/53308... but it seems this post is discussing on creating a checklist items on the fly. I have a checklist template, but seems like I don't see a way to ad it into the flow. Please advise.?

[Ken61]

@Derek17 ,

Can you please share the sample of the code you use to populate checklist on the task.

Thanks

[Barbara Whiting]

This video helps accomplish creating a checklist from a template using Flow Designer. Even shows you how to create the Custom Action needed to parse the JSON. 

https://www.youtube.com/watch?v=Hnf5SLmCGKM

[Steven13434]

Wouldn't you just use the "Create Checklist from Template" action in the Global spoke? I see this on a Washington DC instance. Perhaps it did not exist in earlier versions. You specify the checklist template and the task.

To complete the picture: you would create the task as one action, and the following action would be to create the checklist from a template.

[Derek17]

As mentioned by original poster, they already had checklist templates that they wanted to use. If you use Create Checklist from Template, it creates a new checklist template on the fly every time the flow runs.

[Steven13434]

I disagree. This action does not create a new template. It has two inputs:

- an already existing template

- an already existing task

I read the source code. It is very similar to the code referenced by Sandeep Rajput. To use a checklist template, you need to create a checklist for a specific task from it. So this built-in action does the following:

Loads a 'checklist_template' record, creates a new 'checklist' record and associates it with the task, then for each item in the 'checklist_template' it creates a 'checklist_item' which is related to the checklist. It is the same thing, and I believe it is what the original poster was asking for.

TL;DR: use the built in action. Much easier and ServiceNow can maintain it.