Bug 1232661 - Property "independent" is set to 'false' when CallActivity is created by jBDS
Summary: Property "independent" is set to 'false' when CallActivity is created by jBDS
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: Eclipse Tooling
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Kris Verlaenen
QA Contact: Jozef Marko
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-17 09:12 UTC by Hiroko Miura
Modified: 2020-03-27 19:34 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-27 19:34:36 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Hiroko Miura 2015-06-17 09:12:32 UTC
Description of problem:
Property "independent" is set to false when CallActivity is created by jBDS.

Version-Release number of selected component (if applicable):


Steps to Reproduce:
1. Create a process with CallActivity in JBDS
2. Click the CallActivity and view 'Properties'


Actual results:
Property "independent" is set to 'false'

Expected results:
Property "independent" is set to 'true' by default

Additional info:
In business-central, when creating Reusable(CallActivity) sub process, it's set to 'true. According to community document[1]. default is 'true'. so this should be set to 'true' by jBDS as well in order to avoid any confusion/unexpected behavior.

[1]
https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_BPM_Suite/6.1/html/Development_Guide/sect-Activities.html#Subprocesses

Comment 2 Robert (Bob) Brodt 2015-12-07 18:09:38 UTC
Fixed in BPMN2 Modeler 1.1.4.Final and 1.2.1.Final

Comment 3 Jozef Marko 2016-01-18 14:06:43 UTC
Bob,
I do not see option to set "independent" property for CallActivity in BPMN2 Modeler 1.1.4.Final.

Comment 4 Jozef Marko 2016-01-20 08:08:44 UTC
Bob, sorry, I was using wrong wizard.
Verified on jbdsis-8.0.5, BPMN2 Modeler 1.1.4.Final


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