Uploaded image for project: 'jBPM'
  1. jBPM
  2. JBPM-8516

AdHocOrdering of Ad-Hoc sub-process property is ignored at runtime

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Major
    • None
    • 7.21.0.Final
    • Runtime Engine
    • None
    • NEW
    • NEW
    • Hide
      1. import attached process
      2. Open it and check that AdHocOrdering property is set to Sequential
      3. Close process and deploy it
      4. Run process instance and send 2 Task1 signals and 2 Task2 signals to the process.
      5. Open Menu -> Manage -> Tasks

      Actual Result

      4 tasks will be instantiated (2 instances of Task1 and 2 instances of Task2).

      Expected Result

      1 task Task1 will be active.

      Show
      import attached process Open it and check that AdHocOrdering property is set to Sequential Close process and deploy it Run process instance and send 2 Task1 signals and 2 Task2 signals to the process. Open Menu -> Manage -> Tasks Actual Result 4 tasks will be instantiated (2 instances of Task1 and 2 instances of Task2). Expected Result 1 task Task1 will be active.

    Description

      According to the BPMN 2.0 specification

      If the ordering attribute is set to sequential, another enabled
      Activity can be selected for execution only if the previous one has terminated. If the ordering attribute is set to
      parallel, another enabled Activity can be selected for execution at any time.

      But when I start Ad-Hoc sub-process - it is possible to start any amount of any different sequences.

      Attachments

        Activity

          People

            rhn-support-tsurdilo Tihomir Surdilovic (Inactive)
            kgaevski@redhat.com Kirill Gaevskii
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: