Bug 813183
Summary: | Start timer event does not trigger | |||
---|---|---|---|---|
Product: | [JBoss] JBoss Enterprise BRMS Platform 5 | Reporter: | Tomas Schlosser <tschloss> | |
Component: | jBPM 5 | Assignee: | Kris Verlaenen <kverlaen> | |
Status: | NEW --- | QA Contact: | ||
Severity: | urgent | Docs Contact: | ||
Priority: | unspecified | |||
Version: | BRMS 5.3.0.GA | |||
Target Milestone: | --- | |||
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Bug Fix | ||
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1102116 (view as bug list) | Environment: | ||
Last Closed: | 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: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1102116 |
Description
Tomas Schlosser
2012-04-17 07:22:00 UTC
pull request #87 was opened Currently, only start timers using timeCycle are supported. Timer definitions can take two formats (and are internally translated into timer rules): 1) int timers: the given value is used as delay + cycle, so process will fire every time the period is over For example: <startEvent id="_1" name="StartProcess" > <timerEventDefinition> <timeCycle xsi:type="tFormalExpression">500ms</timeCycle> </timerEventDefinition> </startEvent> Int timer tranlates int timer rule: timer (int:period period) 2) cron timers (timer language is set to "cron") uses a cron expression to determine when the process should fire translates into cron timer rule <startEvent id="_1" name="StartProcess" > <timerEventDefinition> <timeCycle xsi:type="tFormalExpression" language="cron">0/1 * * * * ?</timeCycle> </timerEventDefinition> </startEvent> Adding tecnical_note to make sure this is properly documented. Sorry Tomas, adding the technical note flag to a bug that doesn't have the product release flag doesn't trigger any docs alerts. The technical_note flag should only be used for issues that require an entry in the release notes. A better way would be to raise a docs bug or reassign the bug to me with a note stating what needs to be done. I've removed the timerDelay entry from the Process Overview chapter. Thanks Lee |