Skip to main content
P
potharajuj0799
March 11, 2024
Solved

Two gates side side

  • March 11, 2024
  • 7 replies
  • 0 views

Any two gates side by side in a process is okay ? What may be the issue? what is it called?

    Best answer by konduruc733182

    If that is all you want to do, it should not be a problem. Usually I use a script task in between, if these kind of scenarios come up.

    7 replies

    davidj137213
    davidj137213
    March 11, 2024

    Could you explain a little bit please?

    P
    potharajuj0799Author
    March 11, 2024

    Hi David,

    In a process model two gates side by side (like one XOR node and one AND gate) or ( one OR gate & And gate) is this possible? 

    davidj137213
    davidj137213
    March 11, 2024

    Yes, I think that it is possible, depending on what you want to achieve in your process.

    Check this link

    www.youtube.com/watch

    varuntejg243705
    varuntejg243705
    March 11, 2024

    Hi [mention:e1f38339f5254c84af299fc34f8b6f1c:e9ed411860ed4f2ba0265705b8793d05] ,
    Yes, you can do it. According to your use case it can be achievable.

    tejasn0320
    tejasn0320
    March 11, 2024

    You can use two gates side by side, but if it is used in a loop or recurring, it may fail. In such cases, you need to add a separate node.

    mikes0011
    mikes0011
    Brainy
    March 11, 2024

    As others have pointed out, there are no "rules" in a process model that preclude having subsequent gateway nodes (of whatever type).  However depending on the process, doing this without careful consideration can create various concerns or potential issues, from design, to visibility, to ease of troubleshooting as well as flow.

    A few considerations:

    1) in a process instance, you can't open the instance properties of a completed gateway node to see at what time(s) it was executed. I'm not actually sure WHY, but in terms of process troubleshooting this *IS* a visibility limiting factor.  I usually try to have gateways separated at least by a script task if not some other node type for this reason.

    2) Likewise in a running instance, it's not possible to "start" a gateway node like it would be possible to "start" a script task or user in put task (or most other node types).  Therefore if you want to start or re-start process execution at a particular gateway, you'd need to have a non-gateway-type node right before it which leads directly to it.  This is often important for troubleshooting as well as O&M.

    3) Some gateway nodes (xor in particular) are finnicky about how they can be called if re-executed in one process flow.  Specifically, it can't have 2 nodes both leading to it, because if re-executed from any path other than the path that originally executed it, it will stall and halt the process (intentionally as far as i know, though not SUPER well documented).  Therefore the design guidance here is to always have a single flow into an XOR, especially when there's any sort of looping in the process.

      Terms & ConditionsAccessibility statement