Created attachment 592923 [details] defaultPackage.TestProcess.bpmn2 Description of problem: The aim is to have a start event that triggers repeatedly. That can be done by creating Start Timer event and setting it's timeCycle property to something like 10s###1s to delay the first start by 10s and then trigger start events repeatedly each 1s. However the package containing such process definition cannot be built. Version-Release number of selected component (if applicable): ER9 How reproducible: always Steps to Reproduce: Follow the description or use attached BPMN2 process. Actual results: Building a package containing this process fails (see screenshot for error message). Expected results: Should be possible to build the package. Additional info: Can be worked around by using ordinary start event node followed by an intermediate timer node.
Created attachment 592924 [details] PackageBuild.png
Created attachment 592925 [details] StartTimerEvent.png
jBPM currently does not (yet) support start timers with delay / cycle using ISO-8601, but instead using a proprietary language, linked to Drools. Marking this issue as a duplicate of bug 812006. *** This bug has been marked as a duplicate of bug 812006 ***
Not related to ISO-8601 so it cannot be duplicate of bug 812006. Using the current proprietary time language in start timer event (attachment 592925 [details]) prevents building the rule package in Guvnor (attachment 592924 [details]).
Yes, start timers are (currently) translated into Drools timer rules, and using the syntax as described here (using int or cron): http://docs.jboss.org/drools/release/5.4.0.Final/drools-expert-docs/html_single/index.html#d0e5223 Two examples could be found here: https://github.com/droolsjbpm/jbpm/blob/master/jbpm-bpmn2/src/test/resources/BPMN2-TimerStart.bpmn2 https://github.com/droolsjbpm/jbpm/blob/master/jbpm-bpmn2/src/test/resources/BPMN2-TimerStartCron.bpmn2 Afaik, the start timer event should not be part of the core set of constructs that are supported.