I have implemented a couple of Custom Activities, which must be scheduled in a strict serial manner.
All custom activities are event driven and getting their infos by using a custom Workflow Service via Workflow Queues. When leaving the activities in the AES.executing state, the WF scheduler executes the next activity. How can I change this behavior?
When using the Sync Scope Activity, I can ensure that the next activity is executed not before the ancestor activity has finsihed its execution with the closing state.
Is there a way to sync my custom activities without using Sync Scope Activities?