Bug 833394
| Summary: | Start Timer Event with timeCycle in the form of <delay>###<cycle> prevents building the package | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise BRMS Platform 5 | Reporter: | Jiri Locker <jlocker> | ||||||||
| Component: | BRM (Guvnor) | Assignee: | Kris Verlaenen <kverlaen> | ||||||||
| Status: | CLOSED UPSTREAM | QA Contact: | |||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | BRMS 5.3.0.GA | CC: | kverlaen | ||||||||
| Target Milestone: | --- | Keywords: | Reopened | ||||||||
| Target Release: | --- | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2025-02-10 03:20:10 UTC | Type: | Bug | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Attachments: |
|
||||||||||
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. This product has been discontinued or is no longer tracked in Red Hat Bugzilla. |
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.