Bug 998229 - Unable to add some BPMN artifacts to a subprocess.
Summary: Unable to add some BPMN artifacts to a subprocess.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: jBPM Designer
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER4
: 6.0.0
Assignee: Tihomir Surdilovic
QA Contact: Sona Mala
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-18 12:30 UTC by Marek Baluch
Modified: 2014-08-06 20:07 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-08-06 20:07:31 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Marek Baluch 2013-08-18 12:30:17 UTC
Description of problem:
Cannot add a Task (non-generic, non-manual), Swimlane or WorkFlow pattern to a subproccess.

How to reproduce:
1) add (e.g.) an embedded subprocess to the canvas
2) attempt to add one of the elements above to the embedded subprocess

Build:
Found on ER1

Comment 3 Marek Baluch 2013-08-31 06:54:00 UTC
Most modeling tests use a subprocess so they cannot be fully executed.

Comment 4 Tihomir Surdilovic 2013-09-16 19:36:24 UTC
fixed in designer master and 6.0.x branch. you will need to clear browser cache before testing

Comment 8 Sona Mala 2013-10-15 14:26:46 UTC
Verified for ER4.

All common elements which are used in subprocesses (as User, Email, Send, Manual, etc. tasks and all events) is able to add into subprocess directly from Shape Repository.

For WF Pattern there exist workarounds (as add into canvas and them mark all elements and move into subprocess or activate element in subprocess and attach WF patern). I am going to create a new bugzilla for this issue.

For Swimlanes, there is not any option how to add Swimlanes into subprocess. I think that BPMN2 specification allows such construction (LaneSet is an attribute of FlowElementsContainer and Subprocess inherit FlowElementsContainer) so I am going to create a new bugzilla for this issue.


Note You need to log in before you can comment on or make changes to this bug.