cancel
Showing results for 
Search instead for 
Did you mean: 

[Solved]Timer (Boundary Event)not getting activated

anuppc
Champ in-the-making
Champ in-the-making
I'm trying to run the sample in Activiti in Action examples (Loan Request Process). The Task gets created for the original user however the process fails to  escalates if the assignee fails to complete the task within 1 min (PT1M). Wondering how to debug. I don't see due date details in ACT_RU_TASK table. Looks like the deployment ignored the Duration.

BTW i'm running Activiti 5.6.

Please do let me know if there is something else that i can check to get this working.
-Anup
3 REPLIES 3

anuppc
Champ in-the-making
Champ in-the-making
Tried changing duration to timeDate to 2011-07-12T15:48:00Z. That didn't create any entry for DUE_DATE_ in ACT_RU_TASK table. Although deploy using Probe succeeded.

However i do see under the Jobs tab in Activiti Probe. The pending Task has a " Due Date" = Tue 12 Jul 2011 16:48:00. Looks like it has added 1 hr. Day light saving???

Tried reverting back to duration =  PT1M. Now the pending task in the Jobs tab in the Probe app shows correct Due_Date.However the ACT_RU_TASK table still has empty due date. The escalation fails.

anuppc
Champ in-the-making
Champ in-the-making
Well looks like the activity is still sitting in the Assignee's task list when the due date / duration has expired. When i go to probe app and use the jobs tab to invoke the actions. Then the Task is escalated. My expectation was that the activity would automatically be removed from assignee's user list when the Task expires.  Any idea why the engine is behaving this way??

anuppc
Champ in-the-making
Champ in-the-making