cancel
Showing results for 
Search instead for 
Did you mean: 

Boundary Event on SubProcess Not Firing

puja
Champ in-the-making
Champ in-the-making

Hi,

Please provide answers for below queries -

1. I have a sub process named "Document Approval Sub Process" with activities (Start -> Approve LC Docs User Task -> Collect Approval Status -> End). Timer event is attached to this sub process and the same is not getting fired. Please let me know what's going wrong.

2. After specified time, approval process is to be escalated to escalation group (have another sub process to handle escalation "Escalation - Document Approval Sub Process" with activities (Start -> Escalation - Approve LC Docs User Task -> Escalation - Collect Approval Status -> End)). Is it possible not to cancel first sub process and both sub process remain active in case timer reached specified time? Also if any user (using user task from first sub process) or any user (using user task from escalation sub process) approves or rejects, the process can be completed successfully.

3. Also not able to design the process flow using Activiti Explorer as getting Null Pointer Exception when using timer boundary event. We need to show process diagram with current status being highlighted. The same was able to do till the time timer event was not introduced in process flow. But with timer event, how to decide co-ordinates for respective BPMNDI elements.


Uploaded BPM Process File and Activiti-Config XML files.

15 REPLIES 15

martin_grofcik
Confirmed Champ
Confirmed Champ
Hi Puja,

Job executor did not fire job execution. The question is why.

Was process engine running during the waiting hour?
Did you try original MultiInstanceTest#testParallelSubProcessWithTimer (Did the test work)?
If you create (http://forums.activiti.org/content/sticky-how-write-unit-test) project it would make things much easier.

Regards
Martin

puja
Champ in-the-making
Champ in-the-making
Hi Martin,

How to ensure the process engine is keep running?

I just run the JUnit and waited for 1 hour as specified above.

Regards,
Puja

martin_grofcik
Confirmed Champ
Confirmed Champ
Hi Puja,

Usually there is no need to wait an hour to test the event.
Process engine is driven by clock interface implementation (e.g. DefaultClockImpl). You can set time:

  Calendar tomorrow = Calendar.getInstance();
  tomorrow.add(Calendar.DAY_OF_YEAR, 1);
  processEngineConfiguration.getClock().setCurrentTime(tomorrow.getTime());
  waitForJobExecutorToProcessAllJobs(2000, 100);

Regards
Martin

puja
Champ in-the-making
Champ in-the-making
Hi Martin,

We have used Activiti in our web application. We start approval process when user clicks on submit button on user interface and BPM Process (designed for approval) creates user task(s). If user (i.e. Approver in our case) doesn't act on task, we want to escalate it to another group of users. The web app remained up and running. Process Engine also up as the bean got created through spring application context on application start up. But we found that timer event didn't get fired on its own after the specified time. That's why above conversation and number of questions.

Understood that Process engine is driven by clock interface implementation (e.g. DefaultClockImpl).

Whether we need to explicitly set time as specified above (from our some piece of code) in real scenario? I was under an assumption that timer event should get fired on its own after specified time. Please suggest and help me out in resolving this.

Thanks,
Puja







martin_grofcik
Confirmed Champ
Confirmed Champ
Hi Puja,

when I want to help you, I need to reproduce the issue. I think it is not possible to install whole environment with web app…. on my local machine. That's why I preferred jUnit tests (and all my comments were related to the jUnit tests).
Questions:
Could you reproduce the issue in failing jUnit test? (http://forums.activiti.org/content/sticky-how-write-unit-test)
Could you attach this jUnit test (as zip or on the github)?

Regards
Martin

sankalpn
Champ in-the-making
Champ in-the-making
I ran into a similar issue:

http://forums.activiti.org/content/newbie-activiti-clock-configuration

See if my debugging steps help.