'Complete' status for Synchronous method

[Michael Pokraka]

Hi Swami,
It makes sense if you look at the method: It calls a transaction. Thus
when the user clicks back, the transaction has been called and is thus
complete. That's all the task is coded to do.
In async mode, it is told to wait for a document change, thus will not
terminate until it receives the appropriate event.
 
I'd suggest using the 'Explicit confirmation' (or something like that)
option - to let the user specify whether (s)he is done or not - they may
even need to do more than one edit before completing the task.
I am not 100% certain about how passing of parameters work in this case,
but I think it should do the trick. Alternatively (I assume you do the
call transaction and then query stuff afterwards to pass back), you can
add the post-processing into a seperate task, or - even better - create
a virtual attribut if applicable.
 
Cheers
Mike
 
On Fri, Feb 14, 2003 at 08:54:04AM -0800, Swami Bala wrote:
> Hello All,
>
> I am confused at the 'Complete' status of the workItem when it is a
> synchronous method. I have a task with sync. method and this seems to work
> fine if the application is saved. But when the user just clicks the back
> arrow button without saving it, the work item goes into 'Complete' status
> and dissapears from Inbox. I donot want a asynch.method since i am passing
> parameters from the method back to wflow. How does defining a terminating
> event in synch. method works ?
> Thanks
>
> Swami Bala
>
>
>
>
> _________________________________________________________________
> MSN 8 with e-mail virus protection service: 2 months FREE*
> http://join.msn.com/?page=features/virus