Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-3089 Auto-generate processes based on events
  3. OPT-3827

Adds gateways after process instance/start end if next source has multiple start nodes

    XMLWordPrintable

    Details

    • Type: Feature Part
    • Status: Done
    • Priority: L3 - Default
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 3.1.0
    • Component/s: backend
    • Labels:
      None
    • Effort:
      Not defined

      Description

      At the moment, we always leave the autogenerated model in a state where the next source can build after it. However, for process instance start/end configured sources, we never leave a gateway after it. If the following source has multiple start events, this means that the sequence flows go directly from the process instance start/end call activity to the start events without a gateway existing. Another example of this problem is that connecting gateways are technically mixed direction. We should decide whether it would be an improvement to remove mixed gateways in place of having more correctness, but at the cost of more scattered diagrams.

      Update: We will follow best practices and avoid connecting mixed gateways, rather having distinct diverging and converging as per: https://camunda.com/best-practices/creating-readable-process-models/#modeling-explicitely

      ATs:

      • the joins between generated models have either no connecting gateway, a diverging gateway, a converging gateway, or both gateways, but never a mixed gateway

        mgm-controller-panel

        This is the controller panel for Smart Panels app

          Attachments

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              joshua.windels Joshua Windels
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Salesforce