Boundary Event Listener Not Triggered

[jonle...@gmail.com]

Hi all,

I have configured a timer to send a reminder email 3 times (interval set as 5 minutes each for testing) if the user task is not completed.
The timer is working but the execution listener didn't trigger the send email java class

<bpmn2:boundaryEvent id="rm-hod-approve-request" name="" attachedToRef="approval-hod">
<bpmn2:extensionElements>
<camunda:executionListener event="start" expression="#{HODAdapter.notifyApprovalReminder(execution)}"/>
</bpmn2:extensionElements>
<bpmn2:timerEventDefinition id="TimerEventDefinition_3">
<bpmn2:timeCycle xsi:type="bpmn2:tFormalExpression">R3/PT5M</bpmn2:timeCycle>
</bpmn2:timerEventDefinition>
</bpmn2:boundaryEvent>

I have upgraded camunda engine to 7.1.0-SNAPSHOT but still can't get the execution listener working

Besides, is there a way to set the interval differently for each reminder? For example, first reminder triggered after 5 days, second reminder on 7 days, then the final reminder on 15 days?

Thanks & Cheers,
PL

[Roman Smirnov]

Hi,

I was able to reproduce it with 7.1.0-SNAPSHOT and created thefore a Jira issue CAM-1788. Furthermore, I fixed it:

https://github.com/camunda/camunda-bpm-platform/commit/0e3fdd26baa77c521825bcdbd5273101ce932c10

So, if you wait for a minute and refresh the camunda engine 7.1.0-SNAPSHOT the execution listener should be working on boundary events finally.

It is not possible to set the retry time cycle to be fired first after 5 days, second on 7 day and so on.

Does it help you?

Cheers,

Roman

[webcyberrob]

Hi PL,

Just a style consideration here, rather than putting an event handler on the timer, have you considered modelling a send task attached to the timer and thus send the email from the send task. My rationale is that the email action is thus visible in the model.

In addition, with regard to your question about changing the time parameters, as an approximation could you use a non interrupting timer set to repeat twice every 5 days and a separate interrupting timer set to fire after 15 days? My rationale is the 'final' email could be a message to indicate the process is taking an abandonment path and performing a business cleanup operation, hence the interrupting timer...

regards

Rob

[jonle...@gmail.com]

Hi Roman,

It's working now and thanks a lot :)

Cheers,
PL