All geek questions in one place

State Machine or Flowchart for Windows Workflow Foundation 4?

We currently have a system that processes translation jobs.

  • customer creates an order
  • the project manager transfers it to one or several translators
  • then he goes to the corrector
  • the language manager checks the quality, if this is bad, the work returns to the translator
  • project manager delivers it to the client

Currently, all status can be manually assigned and / or redefined. The value of any step can be skipped or delayed.

The application is an ASP.NET WebForms / MVC mix.

Now I would like to reimplement this with the Windows Workflow Foundation. Will a state machine make more sense than a block diagram? I really do not get the advantage of the state machine ...

+6
source share
2 answers

Given how you describe the work, you really switch between states. Therefore, the use of the state apparatus sounds logical. However, it would be entirely possible to do this using a flowchart, and it would certainly be easier to explain to business users.

Now it’s good that you can mix and match the state of the machine and the flowchart as needed.

+7
source

I prefer StateMachine for most scenarios like this. Of course you can do what you want. You should spend some time studying this. You might want to start with an introduction to the manual laboratory in the state apparatus

+6
source

Source: https://habr.com/ru/post/914899/

More articles:


All Articles