| Task and Session Management Using Workflow [message #783] |
Mon, 23 April 2007 02:27  |
nnones
Messages: 5
Registered: January 2007
Location: Thailand
|
Junior Member |
|
|
I'd appreciate feedback that Tony (or anyone else) can give on the approach we're taking for managing tasks and sessions using workflow.
The issue is: when a transition is fired and it launches Task X, how should the workflow routing and/or navigation be set up when Task X has one or more navigation buttons? A navigation button will always launch another task; say, Task Y, that the workflow engine (which is listening to Task X) won't know anything about.
I think the solution is to treat Task Y as a child of Task X, instead of making it part of the workflow. Consequently it should navigate back to its parent Task X (using the getPreviousTask function, for instance) when it’s finished. In explicit OR split situations, Task X, in turn, should inspect one or more session variables set in Task Y to determine the appropriate routing. I believe this approach is feasible because of the way Radicore manages tasks and sessions; i.e. when you invoke a child task, the parent task is suspended but its state is still retained in the session variables, so when you navigate back to the parent from the child it resumes where it left off.
We are going to conduct some experiments using this approach and of course I will share the results of those experiments on this Forum. In the meantime, however, I'd appreciate knowing if there are any better (proven) ways of addressing this issue.
|
|
|
|
Radicore Forum
Search
Help
Members
Register
Login
Home
