Sub Process vs Start Process

Certified Senior Developer

In new 24.4 we have Synchronous and Asynchronous option for Start Process smart service . Then what's the difference between Subprocess Synchronous and Asynchronous things ?

  Discussion posts and replies are publicly visible

Parents
  • AFAIK this is basically just a case of "feature convergence" - originally-separate features being fleshed-out (separately) to the point where they become nearly interchangeable, if not totally interchangeable.

    They may be planning to phase out the classic subprocess node altogether - though it's impossible to say either way.  The "start process" node needs a few more improvements before that can happen, though.

    • the node icon needs to let us differentiate synchronous from asynchronous, like the subprocess node currently does and traditionally always has
    • it needs to more-flexibly handle opening the subprocess from the parent level; running subprocess instances, for example, as well as subprocess model when defined by expression (at least when defined by something stupidly-easy / nonconditional, like via a single constant)
    • probably needs the ability to pass variables by reference, for the rare occurrence when it's the only way to handle something
    • when searching a model by name in the process model editor search bar, we need a way to "drag and drop" the target model as a Start Process node instead of (or preferably, in addition to) the classic subprocess node.
Reply
  • AFAIK this is basically just a case of "feature convergence" - originally-separate features being fleshed-out (separately) to the point where they become nearly interchangeable, if not totally interchangeable.

    They may be planning to phase out the classic subprocess node altogether - though it's impossible to say either way.  The "start process" node needs a few more improvements before that can happen, though.

    • the node icon needs to let us differentiate synchronous from asynchronous, like the subprocess node currently does and traditionally always has
    • it needs to more-flexibly handle opening the subprocess from the parent level; running subprocess instances, for example, as well as subprocess model when defined by expression (at least when defined by something stupidly-easy / nonconditional, like via a single constant)
    • probably needs the ability to pass variables by reference, for the rare occurrence when it's the only way to handle something
    • when searching a model by name in the process model editor search bar, we need a way to "drag and drop" the target model as a Start Process node instead of (or preferably, in addition to) the classic subprocess node.
Children
No Data