AW: Workflows starting for deleted objects

[Schmidinger, Heinz (Unaxis IT BZ)]

the create object handle is the problem, so I thought to use an own =
method
instnceless defined which is not trying to create an object which is =
only
giving back a paramter.
 
-----Urspr=FCngliche Nachricht-----
Von: Michael Pokraka [mailto:workflow at quirky.me.uk]
Gesendet am: Montag, 19. Mai 2003 14:41
An: SAP-WUG at MITVMA.MIT.EDU
Betreff: Re: Workflows starting for deleted objects
 
Ahh, but that is exactly what LIKP.EXISTENCECHECK doe. Or at least it's
supposed to do.=20
But... as far as I can figure, since it has a key, it must exist, =
therefore
workflow instantiates the object (or at least it tries to) before =
executiong
the method. In the trace it fails with 'Object handle for object cannot =
be
created'.
 
Thanks for the input,=20
Cheers
Mike
 
On Mon, May 19, 2003 at 01:16:10PM +0200, Schmidinger, Heinz (Unaxis IT =
BZ)
wrote:
> Hi Mike,
>=20
> just an idee:
>=20
> cretae an own instanceless method just reading the table if row =
exists and
> return a parameter (not)exits.
>=20
> regards
>=20
> Heinz
>=20
> -----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
>=20
> Hi all,
> Another question to ponder:
>=20
> 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!).
>=20
> Any ideas would be welcome...
> Thank
> Mike