Bug 438004 - Only one outgoing connection (activity call) to other activity allowed - not conformant with BPMN 2.0
Summary: Only one outgoing connection (activity call) to other activity allowed - not ...
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Stardust (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-06-24 04:35 EDT by Gregor Gisler-Merz CLA
Modified: 2017-11-16 10:18 EST (History)
1 user (show)

See Also:

Attachments
Only one outgoing connection (activity call) to other activity allowed - not conformant with BPMN 2.0. (167.20 KB, image/png)
2014-06-24 04:35 EDT, Gregor Gisler-Merz CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Gregor Gisler-Merz CLA 2014-06-24 04:35:34 EDT 
Created attachment 244460 [details]
Only one outgoing connection (activity call) to other activity allowed - not conformant with BPMN 2.0.

Only one outgoing connection (activity call) to other activity allowed - not conformant with BPMN 2.0.
In BPMN 2.0 you don't have to explicitly model the parallel gateway. It is sufficient to have to outgoing connections to other activities. This implies parallel handling.
Please adapt according to BPMN 2.0 spec.
Comment 1 Gregor Gisler-Merz CLA 2014-06-24 05:08:49 EDT 
Tested with Google Chrome