Synchronization issues when canceling workflows

Wever, Martijn martijn.wever at capgemini.com
Sat Jul 24 14:31:43 EDT 2004


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 problem
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 seen
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 confidential=
 and is the property of the Capgemini Group. It is intended only for the=
 person to whom it is addressed. If you are not the intended recipient, =
 you are not authorized to read, print, retain, copy, disseminate, =
 distribute, or use this message or any part thereof. If you receive this =
 message in error, please notify the sender immediately and delete all =
 copies of this message.
 


More information about the SAP-WUG mailing list