Enable scenarios to call other scenarios directly through a module

[#1]

Description - Enable a module that can call another scenario directly

Why is this feature important to you - This would enable a more modular design of our workflow by having common functionality in one scenario that can be called by other scenarios without having to duplicate the functionality across all of the scenarios.

How would you like the feature to work - A simple module that provides the input of the scenario name to call and the inputs to pass.

Current Behaviour - Have to code custom webhooks to call scenarios

[#2]

Hi Jason

Agreed.  We've asked Adobe for this also.  As well as the above, when scenario are getting large, having to repeat downstream paths is not great.  Referencing a sub-flow would be perfect but perhaps it would be difficult to make the subflows synchronous.

[#3]

This is absolutely doable by leveraging the custom HTTP modules in order to call fusion webhooks.

[#4]

Hi Chris

Thanks for that.  How do you solve the asynchronous issue where the scenario that calls the other scenario's webhook won't wait for the called scenario to finish before it continues?  My understanding is that after you've called the other scenario's webhook, the current scenario will just keep going, regardless of the other one.

All the best

Stuart

[#5]

The originating scenario will actually wait to proceed until it recieves a response from the secondary one, so if you need some data out of that one you can set up the secondary to respond with that data.

[#6]

My request, though, is to make this much simpler by wrapping all that in an easy to call and input module.  Would also be good to provide the option in the module if you want the sub-scenario call to be synchronous or asynchronous so that the caller can determine the flow behavior.

[#7]

Chris: that's big news.  Thanks v much

Jason: definitely agree