I just want to ask what is the right process to delete a workflow. Sometimes the users did something wrong, so they delete the workflow process in their task to perform or impact analysis directly. Then corrupted workflow appeared, lots of efforts to delete.
Is it right to first abort the workflow, then delete it in the impact analysis. I am assuming less corrupted workflow by doing this, is it true?
The business rule here is only one WF process should be referenced by revision.
Thanks for your reply
Solved! Go to Solution.
My preference is to block all users by DBA to delete workflows. Make them abort, then an admin would need to clean it out. Only one WF process ever on your revisions? I usually only allow one ACTIVE workflow at a time but I've not had a need to restrict to only one WF process ever.
You need to modify your ACL's. Find "Has Class (EPMJob)" and deny access to everyone besides your DBA or Admin group. I suggest doing this in a test environment to get it working correctly before doing it in your Production environment.
It is a lot of admin work. Maybe another idea is to allow only one active workflow at a time but allow more than one completed workflow on the item rev? I suggest adding the date/time stamp to the workflow names as well, so when you see more than one, you know when it was created without having to go into each one and view the properties.
Try EPM-set-job-protection handler. Add this to the first user task in your workflow and from that point onwards users will not be able to delete that instance of the workflow. Only an admin will be able to delete that workflow instance.