This is a bit of generic question. Our workflows will integrate with an external system (potentially using a camel task, Rest task or Service task. I am trying to understand how best to model the workflow to wait for the response.
My first approach was to mock up a a Receive Task with a message boundary event. I used the Execution Rest API to then send a message to the execution so it would move to next step. Not sure if this is a valid approach as in testing I often got a Rest response that it could not find any executions subscribed to my message. I assume I can also use a message intermediate task instead of a Receive Task. Is this better?
Another approach documented is to use a Triggerable. It talks about using a Service Task and setting the triggerable attribute. This can then be triggered by the runtime service. It is unclear how the Rest interface supports sending a trigger. Also, do you name a trigger for a process definition and then send the named trigger, similar to a message or signal. With this approach would you call your external system with the service task first and then wait for the trigger. How does this work if I use a camel task to send the details to the external system?
Apologies if this is a little broad. I am more confused at the end of the day on the correct approach than at the start so hoping for some help to keep me moving along.