Uploaded image for project: 'JBoss BPMS Platform'
  1. JBoss BPMS Platform
  2. RHBPMS-4333

Inconsistent 'Compensation End Event' behavior

XMLWordPrintable

    • User Experience
    • ER1
    • Hide

      In both BPMN2 Modeler and jbpm-designer:

      1. Create new process with the following elements
        • Start Event: Start
        • Manual Task: Manual
        • Compensation End Event: End
      2. Connect elements in this way
        • Start -> Manual -> End
      3. Select the End
      4. Open properties panel and selected the Manual as the activity that will be compensated.
      5. 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".

      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.

              kverlaen@redhat.com Kris Verlaenen
              rh-ee-jomarko Jozef Marko (Inactive)
              Jozef Marko Jozef Marko (Inactive)
              Jozef Marko Jozef Marko (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: