Bug 813418

Summary:	Missing Wait Node - No Message/Notification Wait artefact in BPMN palette
Product:	[JBoss] JBoss Enterprise BRMS Platform 5	Reporter:	Derek Howlett <dhowlett>
Component:	Tooling (JBDS)	Assignee:	Kris Verlaenen <kverlaen>
Status:	CLOSED WONTFIX	QA Contact:	Lukáš Petrovický <lpetrovi>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	BRMS 5.3.0.GA	CC:	brms-jira, kverlaen, mkranz
Target Milestone:	---
Target Release:	CONTINUING
Hardware:	i386
OS:	Windows
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-11-07 15:52:35 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 Derek Howlett 2012-04-17 17:54:01 UTC

Description of problem:
No Message/Notification Wait artefact in BPMN palette - wait node hasn't been implemented yet. Work around was to use a human task. Community versions do seem include this node for modelling but no support in the runtime. Would need this as part of BRMS.

Version-Release number of selected component (if applicable):
  JBoss Developer Studio 5.  Windows Version. Java 1.6

How reproducible:


Steps to Reproduce:
1. Create a new JBPM BPMN2.0 Project
2. Create a new JBPM BPRM business process
3. Try to create a wait node in the palette
  
Actual results:
Wait Node is missing.

Expected results:
No Message/Notification Wait artefact in BPMN palette - wait node hasn't been implemented yet. 

Additional info:
Work around was to use a human task. Community versions do seem include this node for modelling but no support in the runtime. Would need this as part of BRMS.

Comment 1 Kris Verlaenen 2012-11-07 15:52:35 UTC

The wait node was something that was supported as part of RuleFlow, and was a custom node.  This node however doesn't translate well to any BPMN2 construct.  BPMN2 doesn't directly support the concept of a wait state, there are other constructs used to model something like this.  As a result, we are no longer support this node (in the BPMN2 implementation).