Terminating event triggered before workitem created

[Soady, Phil]

Hi Robin,
 
Check the archives for this one.
Ideas to work with :
forcing update with wait.  (ie Commit Work and Wait instead of just commit work.)
 
Using the event queue, (but remember even with the batch job set to 5 mins,
it is still possible, it is about to run).
 
One can even using your own table, to record the status of PO and workflows
to know how to react to an event in extreme cases.
 
A dummy catch event workflow, can then issue an event itself with earliest start 1 min.
 
Using earliest start on subsequent steps in original wflow is also a ploy.
 
The other approach, is to look at the design of the PO Workflows again considering ALL
events and when they occur. You know big picture stuff.... Design....
 
Perhaps the currently running Wflow can be let finish since a new workflow can start...
 
There is normally a solution there somewhere,
 
hth
Phil
 
 
Phil Soady
Senior Consultant
Business Technologies
SAP Australia
* : 0412 213 079
* : phil.soady at sap.com
 
 
 
 
 
-----Original Message-----
From: Michael Pokraka [mailto:workflow at quirky.me.uk]
Sent: Wednesday, 18 December 2002 12:32 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Terminating event triggered before workitem created
 
 
I've actually been meaning to try this one myself: See if you can change an instance linkage to use the event queue. This would introduce a delay in the process. Another alternative is to add a dummy step in the terminating branch, with a 'requested start time' of +5min or whatever. So it would then
receive the event, go to the next step, wait 5 min and then only complete the WF. HTH Cheers Mike
 
 
On Mon, Dec 16, 2002 at 03:15:01PM -0500, Robin Sahasranam wrote:
> Hello WF experts,
>
> We have some instances where the workitems to release a purchase order
> remain in the agents Inbox even after the PO is released. The workitem
> has a terminating event which is triggered even before the workitem is
> created for the agent. There is a delay of a few seconds, before the
> workitem is created as there are two background steps which run prior
> to the foreground task. In some cases where the users are in a hurry,
> they do a U1 release of the PO (which  start the
> workflow)  and M1 release (the trminating event) immediately within a couple of
> seconds, before the task is created in the box. As the task is created after the
> terminating event is triggered, it remains in the Inbox. The agent later
> executes the task and gets error that release is not required. The Workflow
> Administrator then has to delete the task from the Inbox, besides having to
> respond to trouble tickets, explain the problem etc.
>
> Is there a way to introduce a delay in the triggering of the
> terminating event, or other mechanism so that the task will be
> logically deleted automatically? We are currently on 4.0b, but I have
> also seen this problem on our 4.6c system to which we will migrate
> soon.
>
> Thank you for your assistance.
>
> Robin Sahasranam
> World Bank