stephanpelikan / camunda-externaltask-handler Goto Github PK

The current implementation is a replacement for Java delegate implemenation, expression delegates or expressions.

Doing asynchronous communication Camunda suggest to use this pattern:

But on the other hand Camunda always tells us that details of the technical implementation should not be part of the business process since it is about business requirements and from that perspective it does not matter whether a bounded system provides a synchronous or an asynchronous API. So it should look like this:

Using two message flows in different directions might be a hint to the reader that async communication is done. If it's not obviously which part is the caller then only one message flow should be used to indicate the initiator of this communication:

Since the external task implemenations is a wait state in terms of Camunda's workflow processing it's predicted to use it for hidden asynchronous communication. The external task handler should provide an API which supports this pattern.

On doing asynchronous processing (e.g. asynchronous communication to bounded systems) I want an incident to be created if there is not response within a configured period. The incident should have a certain message.