Beginner WF4 question - When is WF4 useful, really? [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance. Closed 11 years ago.

If I want to use a trad开发者_如何学Goitional approval type workflow in a regular asp.net system, for example an order that needs an approval before order is placed. Rather than having the traditional enum for OrderStatus, can I benefit from using microsoft WF4 (Workflow version 4) for this or will I just generate more complexity and more code for no added benefit?

---

Any time you have a long running operation like this WF4 is a good possibility. The fact that the graphical designer allows you to show the actual running process, not a Visio copy of it, is also a huge benefit.

There is however a learning curve to WF4 and there are times you have to do things the WF4 way instead of the C#/VB way you did before. That said there is certainly a benefit, thinks like an approval request not being handled in, lets say, 14 days is very easy to do in WF4.