Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1151318

Summary:	Timer is not suitable for a synchronous operation timeout use case
Product:	[Retired] JBoss BPMS Platform 6	Reporter:	Toshiya Kobayashi <tkobayas>
Component:	Documentation	Assignee:	Vikram Goyal <vigoyal>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Tomas Livora <tlivora>
Severity:	medium	Docs Contact:	Vikram Goyal <vigoyal>
Priority:	unspecified
Version:	6.0.2	CC:	brms-docs, vigoyal
Target Milestone:	CR2
Target Release:	One-off release
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:	Build Name: 22688, User Guide-6.0-1 Build Date: 22-09-2014 06:10:00 Topic ID: 14166-592103 [Specified]
Last Closed:	2014-11-03 10:08:38 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:

Description Toshiya Kobayashi 2014-10-10 06:53:38 UTC

Title: Timing

Describe the issue:

Please add a note about that Timer is not suitable for a synchronous operation timeout use case.

Suggestions for improvement:

NOTE
===
A timer event can be triggered only after the transaction commit while the timer count-up itself starts right after entering the node (the attached node in case of a bounrary event).

In other words, a timer event is designed for a use case that there is a wait state such as "User Task". If you want to notify a timeout of a synchronous operation without a wait state, a boundary timer event is not suitable.
===

Comment 3 Vikram Goyal 2014-10-20 00:46:21 UTC

Thanks Toshiya,

I have added this note about boundary timer events and did some cleanup of this section. This can be verified here [1].

Moving this to ON_QA. Once it is verified, I will make this live.

[1] https://documentation-devel.engineering.redhat.com/site/documentation/en-US/Red_Hat_JBoss_BPM_Suite/6.0/html-single/User_Guide/index.html#Timing

Comment 5 Toshiya Kobayashi 2014-10-20 05:43:31 UTC

Thanks,

I found a similar explanation in community docs so I'm not sending a pull request to commnity.

https://docs.jboss.org/jbpm/v6.1/userguide/jBPMBPMN2.html#d0e3196

"Timer events could also be specified as boundary events on sub-processes and tasks that are not automatic tasks like script task that have no wait state as timer will not have a change to fire before task completion."

Comment 6 Vikram Goyal 2014-11-03 10:08:38 UTC

Now live: https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_BPM_Suite/6.0/html-single/User_Guide/index.html#Timing