Synchronization issues when canceling workflows - kinda solved

[Michael Pokraka]

Thanks Patrick/Martijn,
This needs to be a separate event as it can occur throughout the flow.
 
I've just found the problem though and it was staring me in the face... s=
ortof.
Part of a custom method is a dialog with a button that allows the user to
jump to a document display. From there the user would click on the change
icon and modify the document, then back out into the main dialog of the
task.
 
The task is defined with a return parameter, the display function simply
clears the return parameter. What is interesting is that the WF system
doesn't try to reexecute the task ona blank return parameter - as I'd hav=
e
thought - but keeps the task locked and somehow only reexecutes the metho=
d.
 
Ah, we learn every day.....
Cheers
Mike
 
Wever, Martijn wrote:
> Mike,
>
> I am assuming you are using a 'wait for event' in a parallel branch in
> your workflow.
>
> Have you tried adding a terminating event to the task?
>
> Regards,
>
> Martijn Wever
>
>
> -----Original Message-----
>> From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
> Michael Pokraka
> Sent: Friday, July 23, 2004 3:49 PM
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: Synchronization issues when canceling workflows
>
> Greetings all,
> On a 4.7/620 system we have events that cancel the workflow. The proble=
m
> is that if the events are triggered via a task in the workflow (e.g.
> changing a requisition release level) the task itself remains in the
> user's inbox (status STARTED) even though the top level workflow is
> cancelled.
>
> The error monitoring job usually comes along within 20 minutes and
> cleans up the task, but that doesn't always happen and is not really a
> solution.
> It appears that although transaction is complete, the event is raised,
> the task somehow remains locked and stays in a status STARTED even
> though the WF is cancelled.
>
> I suspect this is an OSS issue, but thought I'd check if anyone has see=
n
> this...
> Cheers
> Mike
>
>
> Our name has changed.  Please update your address book to the following
> format: "recipient at capgemini.com".
>
> This message contains information that may be privileged or confidentia=
l and
> is the property of the Capgemini Group. It is intended only for the per=
son
> to whom it is addressed. If you are not the intended recipient,  you ar=
e not
> authorized to read, print, retain, copy, disseminate,  distribute, or u=
se
> this message or any part thereof. If you receive this  message in error=
,
> please notify the sender immediately and delete all  copies of this mes=
sage.
>
>