is Boundary Timer Event consider hours, minutes and seconds also to move to next task?

[riteshgupta]

I am developing the workflow where I have the requirement that the when the due date of the task is passed away then I have to move to another task. For implementing it I am using Boundary Timer Event. But I observed that when I set the time date of the timer as after five minutes from today time and date. It is getting fired and moving to next task. Instead of waiting and firing the to next task after five minutes. will the timer boundary event consider only date not the hours, minutes and seconds?. Please help on clarifying it.

[vasile_dirla]

it should work I just tested the boundary timer event with this expression:
1. "PT30S" -> to trigger after 20 seconds from the moment when the task was created.
2. R3/PT30S -> to send 3 emails 30 seconds interval.

<code>
<boundaryEvent id="boundarytimer1" name="Timer" attachedToRef="usertask1" cancelActivity="false">
   <timerEventDefinition>
    <timeCycle>R5/PT30S</timeCycle>
   </timerEventDefinition>
  </boundaryEvent>
</code>
would be nice if you could provide a demo XML file which we could use for testing.

[riteshgupta]

thanks for ur reponse. Below is the config I have done:
<boundaryEvent id="boundarytimer2" name="Timer" attachedToRef="usertask2" cancelActivity="true">
      <timerEventDefinition>
        <timeDate>${dateVariable}</timeDate>
      </timerEventDefinition>
    </boundaryEvent>

I am setting the value of dateVariable dynamically. I set 5 to15 minutes in different  process instances for the timer event but instead of trigerring the event after 5 to 15 minutes. The date format I have used is ISO8601. It got fired immediately. Please help on it.

[riteshgupta]

<boundaryEvent id="boundarytimer2" name="Timer" attachedToRef="usertask2" cancelActivity="true">
      <timerEventDefinition>
        <timeDate>${dateVariable}</timeDate>
      </timerEventDefinition>
    </boundaryEvent>