How to stop default change tasks creation if a change is getting created by copying existing Change

[learn nv]

Hi All,

When I create a change 'Normal Change Model flow for task creation' flow is getting triggered and it is creating 3 change tasks by default. I want to stop triggering this flow if a new change is getting created from an existing change using 'copy change' option. Could some one please suggest how can we achieve it?

Thank you,

Naveen

[M Iftikhar]

Hi @learn nv ,

To prevent the "Normal Change Model flow for task creation" from triggering when a change is created using the 'Copy Change' option, you can add a condition to the flow trigger to check that the "Copied from" field is empty.

This ensures the flow only runs for newly created changes and not for those created via the copy functionality.

Thanks & Regards,
Muhammad Iftikhar
If my response helped, please mark it as the accepted solution so others can benefit as well.

[Dr Atul G- LNG]

Hi @learn nv 

I’ve worked as a Change BPC, and we faced a similar requirement from a large telecom client. To be honest and transparent — it's not as simple as it seems.

The reason is that Change flows are quite complex and tightly coupled with multiple scripts and logic. It’s not just about handling three tasks — there are edge cases too. For example, what happens if someone manually creates a different type of case outside of the standard flow?

What we did — and also based on recommendations from ServiceNow — was to create a new UI Action that copies the Change along with its tasks. Then, we built our own logic around that, rather than modifying any of the OOTB (Out-of-the-Box) functionality.

This helped us maintain system stability and avoid technical debt while still meeting the client’s requirements.

[Ankur Bawiskar]

@learn nv 

Rather than touching the OOTB Flow OR Creating a new custom UI action, you can use this approach

-> use Before Insert business rule on change_task and see if the CHG to which this CHG Task is getting created is a copied one or not

-> if yes then use setAbortAction(true) and stop task creation

If my response helped please mark it correct and close the thread so that it benefits future readers.