Long running workflows to simulate activities from mobile application (like a wizard / page flow) with user actions on the app.

[prashantkalkar]

We have a mobile application. The mobile application navigation can be thought of similar to a workflow as what the user is doing. When we were evaluating cadence, it seems that it is primarily can be used for starting a workflow on a user request but no subsequent interactions are required from the application to the workflow.

In our case, we are thinking of the workflow that progressed along with the screens in the application. That means the workflow progress will be controlled by the requests from the mobile application (on user's interaction with the app). During our POC, we managed to simulate this with the help of blocking the workflow process and then using a signal method to progress it on the basis of user interaction. We used Query methods to retrieve information from the workflow. This also made the workflow stateful (as the data produced by the activity is maintained in the workflow class).

Is this the right way to using cadence to use it for page flow. Is there any better way of achieving that same? Is there any other way supported/recommended by cadence to achieve the same?

[mfateev]

We are going to introduce support for something like SignalWithReply that is going to block until the signal handler returns. I'll update this issue as soon as it is added.

[sandys]

hi guys, is there any progress on this ? what is the currently acceptable mechanism to block on a workflow for external input and then resume ?

[mfateev]

We are actively working on the synchronous update feature. This stack answer outlines the current workarounds.