Bug 1263526 - Conditional boundary event can't be edited
Summary: Conditional boundary event can't be edited
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: Eclipse Tooling
Version: 6.2.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-09-16 05:32 UTC by Jozef Marko
Modified: 2020-03-27 19:39 UTC (History)
0 users

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

Attachments (Terms of Use)

Description Jozef Marko 2015-09-16 05:32:01 UTC 
Description of problem:
If user adds conditional boundary event to some task, he can't edit this boundary event.

Version-Release number of selected component (if applicable):
jbds-9.0.0.CR1_jbdsis-9.0.0.Alpha1
BPMN2 Modeler - 1.2.1.x

Steps to Reproduce:
1. Create process with some task
2. Add Conditional Boundary event to this task
3. Double click on boundary event
4. Select tab Event
5. Select event in Event Definitions table
6. Click last Edit button

Actual results:
In step 6. nothing happens

Expected results:
In step 6. is user able to edit given event

Additional info:
Other types of boundary events seems to be fine
Comment 1 Jozef Marko 2015-09-16 05:34:09 UTC 
The same for Conditional start event.
Comment 2 Robert (Bob) Brodt 2015-10-29 20:54:22 UTC 
Fixed in:
Luna build 1.1.4.201510291907
Mars build 1.2.1.201510291906
Comment 3 Jozef Marko 2015-11-02 07:47:45 UTC 
Bob, thank. Fix looks good. I will mark as verified when fix will be mirrored in JBDS integration stack.
Comment 4 Robert (Bob) Brodt 2016-02-01 22:05:07 UTC 
This seems to be fixed in the latest Mars (1.2.3) and Neon (1.3.0) builds for BPMN2 Modeler
Comment 5 Jozef Marko 2016-02-16 15:04:21 UTC 
Verified on:
jbtis-4.3.0.Beta1
BPMN2 Modeler - 1.2.3.CR2-v20160209-2002
Note You need to log in before you can comment on or make changes to this bug.