Re: Workflow impasse? New ideas.

[Michael Schneider]

A nice way of looking at workflows is EVTX diagrams/methods Where E -  Entry Criteria to start process activity V - Validation Methods (inspection methods) T - Tasks in the process activity X - Exit Criteria to say task is complete You can define your process by Listing the process activites (Each with an EVTX datum), then linking the process tasks together   This has worked well for Modeling Software Process and Manufacturing Processes, Any thoughts on this? Jonathan Asbell wrote: Hello all.  I just got back and was reading the e-mails about workflows.  By the tone and lack of dialog I think that we are not sure how we really want to design workflows still.  So lets have more discussion on the subject.  When its clearer we will better know what we want to do. Here are some ideas I thought could break down the problem a little more.  I was thinking that a workflow can be described in the following ways: 1) It has a specific order2) It DOES'NT having a specific order3) It has a combination of tasks, some of which need to be executed in order, and others that do not4) All of its tasks must be finished at the end5) It May be made up of other worklflows Therefore, you would get a workflow with the characteristics you want.  At the end you would make sure all tasks have been done in order it to be considered a completed workflow.  For items that need order we can use the struts config file to put an entry in for<workflows>     <flow name="createAccount" class="com.brooksbrothers.workflows.Account_WF">          <step ordered="yes" number="1" class="com.brooksbrothers.workflows.AccountPersonal_ITEM">          <step ordered="yes" number="2" class="com.brooksbrothers.workflows.AccountCreditCheck_ITEM">          <step ordered="no" class="com.brooksbrothers.workflows.AccountDisplayTotal_ITEM">     </flow></workflows> anyone want to add....