Loading...

XML

Word

Printable

Details

Type: Bug
Resolution: Won't Do
Priority: Major
Fix Version/s: None
Affects Version/s: 6.4.0
Component/s: Eclipse Tooling, jBPM Designer
Labels:
- reported-by-qe
Environment:

JBDSIS-9.0.2.CR1

Affects:

User Experience
Affects Build:
ER1
Target Release:
Steps to Reproduce:
Hide

In both BPMN2 Modeler and jbpm-designer:

Create new process with the following elements

Start Event: Start

Manual Task: Manual

Compensation End Event: End

Connect elements in this way

Start -> Manual -> End

Select the End

Open properties panel and selected the Manual as the activity that will be compensated.

Save the process and see the source code

In jbpm-designer the Manual will contain attribute "isForCompensation=true".

In BPMN2 Modeler the Manual won't contain attribute "isForCompensation=true".
Show
In both BPMN2 Modeler and jbpm-designer: Create new process with the following elements Start Event: Start Manual Task: Manual Compensation End Event: End Connect elements in this way Start -> Manual -> End Select the End Open properties panel and selected the Manual as the activity that will be compensated. Save the process and see the source code In jbpm-designer the Manual will contain attribute "isForCompensation=true". In BPMN2 Modeler the Manual won't contain attribute "isForCompensation=true".

SFDC Cases Counter:
SFDC Cases Links:

Description

Compensation End Events behave in a different manner in jbpm-designer and BPMN2 Modeler. In both of these editors the user selects the activity to be compensated. However jbpm-designer adds "isForCompensation=true" to the selected activity and BPMN2 Modeler doesn't add "isForCompensation=true" to the selected activity.

Attachments

Activity

People

Assignee:: Kris Verlaenen

Reporter:: Jozef Marko

Tester:: Jozef Marko

QA Contact:: Jozef Marko

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Dates

Created:: 2016/10/03 2:56 AM

Updated:: 2021/10/24 6:26 AM

Resolved:: 2018/08/09 3:50 AM