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

Lukasz Bojara
Kilo Sage

‎04-18-2024 02:28 AM - edited ‎04-18-2024 02:39 AM

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.

0 Helpfuls
  • 1,336 Views
5 REPLIES 5

Lukasz Bojara
Kilo Sage
In response to michaelj_sherid

‎04-18-2024 07:14 AM

Unfortunatelly not an option in this case, it is not allowed in this instance, client rules 😉 

I have two solutions, one if them is to write a fix script that will do the same job a Add to Update Set. Just with the complexity of checklists it will have to iterate trough 3 different tables to have it all.

0 Helpfuls