How to handle events out of sequence???

[Michael Pokraka]

Hi Stephan,
I intended to use the 'EXISTENCECHECK' method, and to read change
documents. Reading the event log is an excellent idea though. The only
hitch is that the event log must be permanently switched on. No problem
with the system I'm currently working on though.
This does address one of my concerns with reading change documents -
performance (especially as this tenmds to only be a problem at peak
loads!).
Thanks
Mike
 
On Mon, Feb 24, 2003 at 05:57:13PM +0100, Becker Stephan (extern) wrote:
> Why don't you build a first step into your workflow that checks whether the document still exists (easy, a simple select will do) or has had changes in the meantime (read the event log)?
>
> Hth,
> Stephan
>
>
>
> -----Original Message-----
>> From: Michael Pokraka [mailto:workflow at quirky.me.uk]
> Sent: Montag, 24. Februar 2003 17:42
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: How to handle events out of sequence???
>
> Hi all,
> I have a minor dilemma which has been vexing me for a while:
> We use the event queue for handling some high-volume workflows. Now, the
> same workflows also have waitfor CHANGED and DELETED steps. (4.6c system
> by the way)
>
> The problem is that at peak times it can take 5 minutes for the workflow
> to run, by this time users have sometimes already edited the relevant
> documents (or even deleted them).
> This results in e.g. a doc is created, user changes it 2 min later -
> CHANGED event is raised, and a few minutes later the CREATED event comes
> out of the queue and starts the WF which doesn't see any 'past' events
> in it's wait steps.
> Also, I can't seem to find a way to send instance linkages to the event
> queue which may help, but is by no means guaranteed to eliminate the
> problem.
>
> Apart from reading change documents and calling EXISTENCECHECK methods,
> does anyone have any ideas on handling these type of synchronization
> issues?
>
> As usual, any input greatly appreciated.
> Cheers
> Mike