Hello,
I am facing a little challenge that is going to either require some
major refactoring (mostly just moving ****ts, but a lot so it's a pain)
or being able to create a new orchestration that will be activated via
one message (from my existing orchestration) and then receive a second
message from this same "parent" orchestration later on with the info
it will need to do it's processing.
In short I'm trying to get around messages not always being
initialized and my orchestration is already so big that I don't want
to just add some dummy initializations that aren't required. I've got
three branches that do different things and start different ways, but
they all have the same result and I don't like the idea of putting
three Call Orchestration shapes inside these branches if I refactor
out the common behavior to another orchestration.
Any ideas would be great.
Kind Regards,
-Dan
