Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-3856

I can use asyncBefore and asyncAfter on the activity wrapped in the multi instance body

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Fixed
    • L3 - Default
    • 7.4.0, 7.4.0-alpha1
    • None
    • engine
    • None

    Description

      Currently, declaring a multi-instance activity async makes the body async, that means, before the instances are created and after all are ended. For true parallelism, it is desirable to be able to declare the inner activity async. Then, all instances are created at first but their execution is asynchronous. Similary for asyncAfter, there ending is asynchronous, thus separating the synchronization aspects (that may cause optimistic locking exceptions) from the actual activity's work.

      AT:

      • I can configure asynchronous continuations for the activity wrapped in the multi instance body
      • TBD: "name of the feature" and how is it represented in XML?
      • Documentation exists

      Implementation notes:

      • the legacy behavior implemented in CAM-3826 makes assumptions that async jobs for inner activities cannot exist and automatically migrates them to jobs for the mi body. This would have to be enhanced once we implement this ticket

      mgm-controller-panel

        This is the controller panel for Smart Panels app

        Attachments

          Issue Links

            is related to

            Feature Request - A new feature of the product, which has yet to be developed. CAM-4235 I can set asyncBefore, asyncAfter and exclusive on multi instance loop characteristics

            • L3 - Default - Minor issue or issue with existing workaround, feature requests and questions
            • Closed

            Feature Request - A new feature of the product, which has yet to be developed. CAM-4248 Add multiInstanceLoopCharacteristics async attributes to BPMN model API

            • L3 - Default - Minor issue or issue with existing workaround, feature requests and questions
            • Closed

            Task - A task that needs to be done. CAM-4226 Write migration tests for job definitions/job execution for async MI tasks (7.2 -> 7.4)

            • L3 - Default - Minor issue or issue with existing workaround, feature requests and questions
            • Closed

            Activity

              People

                matthijs.burke Matthijs
                thorben.lindhauer Thorben Lindhauer
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Salesforce