AW: Workflows starting for deleted objects

[Schmidinger, Heinz (Unaxis IT BZ)]

Hi Mike,
 
just an idee:
 
cretae an own instanceless method just reading the table if row exists =
and
return a parameter (not)exits.
 
regards
 
Heinz
 
-----Urspr=FCngliche Nachricht-----
Von: Michael Pokraka [mailto:workflow at quirky.me.uk]
Gesendet am: Montag, 19. Mai 2003 13:02
An: SAP-WUG at MITVMA.MIT.EDU
Betreff: Workflows starting for deleted objects
 
Hi all,
Another question to ponder:
 
Users often create deliveries and delete them straight afterwards (I'm =
too
scared to ask why - but I assume it's when they mess things up and want =
to
start again).
Now, we have workflows that start after a LIKP.CREATED event, using the
event queue. The Queue introduces a delay, and hence we have workflows =
which
fail straight away (object doesn't exist). Adding a task based on
LIKP.EXISTENCECHECK also fails, it appears to be that it falls over =
when
instantiating the object in order to check it's existence... (duh!).
 
Any ideas would be welcome...
Thank
Mike