.Net Workflow Foundation design: Multiple workflows or one big workflow with IfElse activities? -
I am reading something about workflow design and how am I confusing my application as a model.
Sequential workflow with 5 top-level activities
For the above requirement, can you advise what is the best strategy in case of initial design and maintenance:
OR
- Design different workflows - each one type of document.
OR
- Any other better options?
Thank you!
I worked for WF 3.5 SP1 for the appropriate duration and gave the following suggestions:
-
Different workflows - Each per type of document: A straight forward no because you have to be strong enough to include new documents. You can not simply (not) type the document type as continuous, the requirement of business will change and you will be asked to add more than 10-15 documents (all real-world software has all the time).
-
As new child activities can be started In the future, you can look at defining different workflow for 5 top-level activities. This can help you to maintain a personal top-level activity.
-
There may be a big workflow with lots of e-ELSs and it looks good at the beginning but I believe that it looks terrible once the number of proper conditions Has been added. It makes a lot of effort to manage a huge workflow.
So, to sum up, you can divide your activities into top-level activities in only 5 workflows and then manage.
Hope this helps.
Comments
Post a Comment