Terminating event triggered before workitem created

[Dart, Jocelyn]

Hi Robin,
Why not just put a fork in so that one side does your current steps
and the other waits for the event.
If you need the background steps to be done regardless then you could always
use a container operation to set a flag after the event that tells you the
foreground step is no longer needed.
 
Easier in 6.10 and above with work item pre-conditions but the above will
work for both 4.0B and 4.6C.
Regards,
        Jocelyn Dart
Consultant (SRM, EBP, Workflow)
and co-author of the book
"Practical Workflow for SAP"
SAP Australia
email: jocelyn.dart at sap.com
phone: +61 412 390 267
fax:   +61 2 9935 4880
 
 
 
 
 
-----Original Message-----
From: Robin Sahasranam [mailto:Rsahasranam at worldbank.org]
Sent: Tuesday, 17 December 2002 7:15 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Terminating event triggered before workitem created
 
 
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