Lifecycle Events - HR Template Checklist - Why it is so hard to move it between instances?

[Lukasz Bojara]

Hello Experts,

When creating an HR Template for the Lifecycle Event Activity, you have the option to assign a checklist to it and add checklist items to that template. However, problems arise when you need to move the developed Lifecycle Event to another environment, such as from DEV to TEST to PROD. The issue is that checklists are not captured in update sets, even if the HR Template is.

Ordinarily, checklists are considered records, which is why they are not captured in update sets. However, in this case, the checklist is part of a template. Even so, there is no easy way to move the checklists between instances. The only method that may work (it worked for other type of records, not yet sure it will work here) is to save the checklist as a "checklist template" (which is also not captured in the update set) is, find that record, export it to XML, import it into the second instance, and then manually assign a checklist template to the HR Template in that second instance.

When you have 20 HR Templates per Lifecycle Event, this means that you need to redo the work on every single instance, even on PROD. This brings me to the conclusion that it is pointless to configure it at all. The best way to avoid doubling or tripling the work is to leave checklist work to PROD. Unfortunately, if you want stakeholders to sign off on your work, they need to see it fully, with those checklists. Thus, you are left with the same work multiple times, and this is ironic since we prize ServiceNow for its automation capabilities (well, not for developers).

If anyone knows of a smoother, more automated method of doing this, please share.

[Community Alums]

Hi @Lukasz Bojara ,

When it comes to move the Checklist from one instance to another, we often try to move them 

1. via update set

2. extract xml of checklist.

But after some time we find that they both approach is not helpful in this case.

Here the solution to move it.
consider the a checklist created in one instance. On HR service record we have option to "Save as template".
Give a name and group to which it will be visible(Prefer HR admin group as we are migrating it). Save the template.

The record is saved to "checklist_template" table. move the XML file of the saved template to other instance.

Now on the HR service on other instance, we have a option to apply the template on checklist.

@sanket16 Credits

[Lukasz Bojara]

Hi @Community Alums ,

Thank you so much for taking the time to reply. I really appreciate your input. However, if you don't mind, let me clarify that the method you suggested is exactly what I had in mind and briefly described in my original post. While it's a feasible approach, I am a bit hesitant as it requires duplicating the work, which could lead to errors. Moreover, it may not be foolproof if someone else were to deploy it. The installation process would have to be detailed and followed to the letter, which could be challenging. There's always the risk of accidentally choosing the wrong template or missing a vital step, which could cause issues later on.

Thanks,

Lukasz

[Community Alums]

Hi @Lukasz Bojara ,

I know from where you are coming for, but those are the only approaches which i have used.

[michaelj_sherid]

@Lukasz Bojara have you tried using the update set utility that is available on the Developer's site? Here is a link to the details. Let us know if this works out for you.

If my answer has helped with your question, please mark my answer as an accepted solution and give a thumbs up.

Regards,

Mike