| Re: Task and Session Management Using Workflow [message #784 is a reply to message #783] |
Mon, 23 April 2007 04:08   |
AJM
Messages: 2352
Registered: April 2006
Location: Surrey, UK
|
Senior Member |
|
|
Why should the fact that a task in a workflow calls other tasks via navigation or popup buttons have any effect on the workflow? The whole purpose of a workflow is to identify tasks which must take place in a specific sequence, with the option to direct the sequence down different paths depending on certain conditions.
Take for example the simple sequence of Task A -> Task B. This says that when Task A is finished the workflow moves on to Task B. The fact that while processing Task A it was necessary to branch out to other tasks is totally irrelevant - this is simply activity within Task A that happens before Task A is completed.
The workflow system tells the user "you need to complete Task A", and it will not do anything else until that task is completed, which is recognised with a database update. Anything which happens before the task is completed is of no concern to the workflow system.
Tony Marston
http://www.tonymarston.net
http://www.radicore.org
|
|
|
|
Radicore Forum
Search
Help
Members
Register
Login
Home
