Project: mulestudio
Issue STUDIO-4701: Watermark should set flow's processing strategy
Watermark functionality requires the owning flow to have a synchronous processing strategy, which is fine. However, synchronous is not (and should not be) the flow's default. That means that when I put a watermark in a flow and I start the application, I get a deployment exception saying that the flow should be synchronous. This is confusing to the user and requires him to read the logs, find the message, change the flow an try again. It would be great if upon enablement of watermark, studio could automatically set the flow's processing strategy to synchronous.
Story points: 13