I will try to use a custom action to set the timer value.
Thanks.

I've been looking for a way to retrieve the timer in my current state from the executionContext of a custom action, but i've not found any ! Could you please give me lead ?

Another question : in the action code, if the timer timeout is changed, should i explicitly try to save it, using a jbpm context, or will this be done in the current persistence session ?

Thanks again.

More questions !

I've changed my test code that used a state node with a task-node just as in your example.

Now, it seems the timer fires twice : my timer action writes a message on system out twice. But it seems the transition from the timer task is done only once.

The full jpdl is at the end of my message...

What goes wrong ?

<?xml version="1.0"?>

<process-definition
 xmlns="urn:jbpm.org:jpdl-3.1"
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xsi:schemaLocation="urn:jbpm.org:jpdl-3.1 http://jbpm.org/jpdl-3.1.xsd"
 name="MY-PROCESS-NUMBER-SIX">

 <start-state name="start-of-job">
 <transition
 name="to_activity-1"
 to="activity-1" />
 </start-state>

 <task-node name="activity-1">
 <task name="task_activity-1">
 <event type="task-create">
 <action
 class="my.wf.six.TimerInitializationActionHandler" />
 </event>
 <timer
 name="timer_activity-1"
 duedate="5 seconds"
 transition="to_activity-2">
 <script>
 <expression>
 <![CDATA[
 System.out.println("*** TIMER FIRED !!!!!!!");
 ]]>
 </expression>
 </script>
 </timer>
 </task>
 <transition
 name="to_activity-3(1)"
 to="activity-3" />
 <transition
 name="to_activity-2"
 to="activity-2" />
 </task-node>

 <state name="activity-2">
 <event type="node-enter">
 <script>
 <expression>
 <![CDATA[
 System.out.println("*** ENTERING : " + node);
 ]]>
 </expression>
 </script>
 </event>
 <transition
 name="to_activity-3(2)"
 to="activity-3" />
 </state>

 <state name="activity-3">
 <transition
 name="to_end-of-job"
 to="end-of-job" />
 </state>

 <end-state name="end-of-job" />

</process-definition>

Hello again.

Indeed, the ExecutionContext has a getTimer method, but it seems it always returns

null