Describe how one application can start/stop/pause a workflow on another application via communication APIs

[msfussell]

What content needs to be created or modified? Currently there is a limitation that the workflow API (start, stop, etc) cannot be called directly from one app to another. Instead you have to either use Service Invocation or pub sub to act as a "trigger" message and then in the method of these start, stop the workflow

Describe the solution you'd like Need to describe the work around to call remote workflows.

Where should the new material be placed? In the Workflow section, probably as a new topic.

Additional context See this Discord thread for example and details https://discord.com/channels/778680217417809931/1166296780443488266 @olitomlinson - Please add other details here from any other Discord thread.

[cgillum]

Any suggestions on where it makes sense to add this content? I think most of our existing workflow content describes the workflow feature in isolation, but is there a place for describing how to incorporate workflows into the rest of your app? Do we need to add one? In addition to this, I image it would be useful to explain other integrations, such has how to use workflow activities to use other Dapr building blocks, like service invocation or pubsub (we have samples for this, but I don't think we have docs for higher-level microservice-oriented app patterns).