The Code is the Design

http://calibre-ebook.com/download_osx

A comprehensive comparison

(Also look at a much more detailed approval/rejection solution on MSDN ) The below solution simply uses a Flow Chart level boolean variable and a FlowDecision element to show one approval/rejection scenario. The flow has one task activity and one approval. If the 2nd is rejected, it goes back to the first one. We can configure any number of such sequential related activities. The test code is configured for persistence too so you can end your app anytime and restart any persisted workflows later. Open the sln, change the connection string and hit ctrl+f5 to test. Use the below SQL on your DB if you forget to note the GUIDs from the console output. (Look at t he previous post to see how to configure the persistence tables on your DB for WF4) select * from [System.Activities.DurableInstancing] . [InstancesTable] select * from [System.Activities.DurableInstancing] . [RunnableInstancesTable] ******************** SubmitTaskName.cs ********************