Identifying where workflow is used

brantgluth
Kilo Expert

I inherited an environment where there are quite a few development workflows lying about. I'd like to clean them up, and am fairly confident of the "dead" workflows, but am hesitant to do so   without making sure they aren't still used anywhere.

I thought that using "Find Record References"   under Workflow properties (in workflow editor) would show me references, but even on active workflows, I get no results. Is there somewhere else i should be looking?

.

1 ACCEPTED SOLUTION

Ivano B
ServiceNow Employee
ServiceNow Employee

Hi Brant



Did you check under 'Workflows > Live Workflows > Active Contexts' ?


The table will show you all the workflows still active and the records using them.



Have a look and let me know.


ps. About deleting workflows I would suggest to think twice..maybe you can simply deactivate them and stop using them.



I hope this will help/answer your question and if it does please mark it



Cheers
R0b0


View solution in original post

3 REPLIES 3

Ivano B
ServiceNow Employee
ServiceNow Employee

Hi Brant



Did you check under 'Workflows > Live Workflows > Active Contexts' ?


The table will show you all the workflows still active and the records using them.



Have a look and let me know.


ps. About deleting workflows I would suggest to think twice..maybe you can simply deactivate them and stop using them.



I hope this will help/answer your question and if it does please mark it



Cheers
R0b0


brantgluth
Kilo Expert

Much better thought than mine, I was looking at using group by in Items, but that didn't show subworkflows. Doing a group by workflow in Contexts gave me what I needed



Te point may be moot, however, as I tested delete on a known test workflow, and the workflow remains in the catalog. I'm betting for referential integrity. We had a user who'd copy a workflow, and redo it to test issues, leaving us with multiple one-off names that can be confusing. It'd be nice if we could folder them off like we can with Custom Orchestration Activities. For nwo, I'm just going to rename them with a "zArchive-" so they;'re out of the way and easy to ID


Ivano B
ServiceNow Employee
ServiceNow Employee

Hi Brant



Ok now it makes sense.


if you are in DEV and you understand exactly what the duplicates are than I suppose you're right and you can delete them.


It is important that these duplicates never reached PROD otherwise marking with a z is absolutely a good idea.



Cheers


R0b0