Maybe this is answered elsewhere. I spent a good amount of time looking and didn’t see what I wanted which was a way simpler explanation of what these things mean.
here’s my use case. its common. i’m sure a thousand people have solved it.
I have a serviceTask written in Java. It does something that could take a while. I want to do that task asynchronously in the meaning that it runs execute, returns, but does not complete the task and move on in the process until I explicitly say the task is complete. I have been told that even when using asynchronous tasks when execute returns the process continues, meaning that the task may be executed by flowable asynchronously, the task itself is not asynchronous.
my hope was to have some other mechanism to trigger the continuation of the process outside of whats automated by flowable. And I’d prefer to do it in a way that doesn’t require many tasks to do essentially just waiting for notification. So if that’s possible it would be ideal because it makes using our task components easier with less boilerplate in the workflow just to access remote systems.
How would I do this? I think my understanding (or lack of) of two terms is at the heart of this problem. Async and Triggerable.
from my searches it looks like there are ways to trigger actions on tasks but if they already complete when execute returns then whats the point?
I would appreciate any help. I’m sure this has been done successfully by many people.