It just doesn't make much sense.
You'd probably rather have a mainflow where the MQInput is linked to the subflow... and then just have a subflow reusable where the you just have an input node. However if you go for that design you should be aware of the problems created if you use an HTTP or SOAP input instead of an MQ input...
You may well need to have conditional header handling in your subflow, or need to have the mainflow do all that conditional handling before and after calling the subflow.
I have used this model where I wanted to make accessible the same functionality via a reusable subflow and via an MQ Request/Reply pattern. The one condition was the message must arrive in the same structure in either usage pattern.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum