I made a mistake in a production flow... I used a "non-interrupting timer" trying to abort a task, instead of use a "Timer"... now I have two active tasks when I should have just one...
Is there any way to put that infamous task down? :-)
I mean, any way at all... I tried using Longboard, API, Bonita Portal... I could not find any way to do that.
Can anyone help here?
Actually if you are using a community Edition, you will have to correct your process design and deploy a new version of your process in production.
The ongoing instances are going to finish using the old versions, and new instances will start with the new one.
Thank you delphine.coille for your comment... I understand that... but I need a solution for the current cases... I came up with a work around, but it seams very uncouth... I saw a cancel button in Longboard, for "cases"... as the task I want to cancel is in a subflow, I think I can cancel it after the correct task has been finalized and go back to the caller.
The problem is that Longboard just open "root cases"... as my subflow is not a root case, I can't open it with Longboard... anyway, I realized Longboard just uses an endpoint with the caseId to cancel it... it is not pretty, but it works... I've tried it in dev environment to be sure.