-
1. Re: task in a start-state is not considered for execution
kukeltje Sep 28, 2005 3:31 AM (in response to janapoornavel)if you create a post with 'code' in it, use the
tags, or the buttons in the 'full' editor.
And yes, the task in a start state is a kind of 'special' one. It is indeed considered as part of the start completion. The feature we are thinking of is to at least check if the user is in the right swimlane if one is configured -
2. Re: task in a start-state is not considered for execution
janapoornavel Sep 28, 2005 4:24 AM (in response to janapoornavel)hi ron,
iam sorry,i havent told problem.the intended behaviour is not exhibited.(i.e) when i try to do processinstance.signal(),i expected the engine to stop till the appropriate party signalled his task completion,but the transition happened from the start-state without considering the task present in it.
regards,
jana -
3. Re: task in a start-state is not considered for execution
kukeltje Sep 28, 2005 5:26 AM (in response to janapoornavel)afaik, that is ther default behaviour of tasks (at least in the tasknode) Tasks are non-blocking. you can configure it to wait for all tasks to be finished (making them blocking). See the docs, it's in there
-
4. Re: task in a start-state is not considered for execution
janapoornavel Sep 28, 2005 9:18 AM (in response to janapoornavel)hi ron,
thanks for the input.i just though that i have to make an explicit request to the TaskManagementInstance .
regards,
jana
P.S:- for the people who might not get what iam saying,please do start witht the websale application,i reckon thats a good place to start with,as far as learining the initials things are concerned.