Anyone using the new 610/620 terminating events?

[Michael Pokraka]

Hi Jocelyn,
Thanks for the input, yes it does work well - too well in this case. I've
logged it with OSS, tried the block correction as well - never known that
to be of use and didn't do anything in this case.
In case anyone's interested I've got a bit more detail:
 
Seems that completing/cancelling a workflow will cancel instance linkages
with a receiver type 'EVENTITEM'. These header events however have their
own receiver types, such as WORKFLOW_RESTART_WORKFLOW. These do not get
removed from the instance linkage upon WF completion. This means a dead
workflow still receives the event and in the case of a restart event it
gets resurrected and reappears anew, and in true zombie fashion they keep
multiplying at each event.
 
Cheers
Mike
 
 
Dart, Jocelyn wrote:
> Hi Michael,
> I've used the term event for reassessing agent rules - which works a
> treat!
> But haven't tried the others yet. I have had some issues in SRM on 6.20
> with
> workflows not completing correctly however so it may be related.
> Try a "block correction" in your workflow and see if that improves the
> situation.
> If not, suggest you check what basis/WAS patch level you are on and the=
n
> report it in to OSS.
> 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: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
> Michael Pokraka
> Sent: Wednesday,31 December 2003 12:54 AM
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: Anyone using the new 610/620 terminating events?
>
>
> Hi all,
> Hope this doesn't get completely drowned in all the list traffic...
> Is anyone out there actually using the new version (4.7/620/610)
> header-level events for terminatig/restarting workflows etc?
>
> We're trying to make use of this nifty new feature but all is not as it
> should be: For starters, cancelling a workflow doesn't delete the insta=
nce
> linkage. This has the following interesting result when using the 'Canc=
el
> and restart workflow' function:
>
> Flow 1 receives a CHANGED event.
> It gets cancelled and Flow 2 is started.
> 2 instance linkages still remain active.
> Another CHANGED event 'cancels' both flows and starts 2 more.
> Another one 'cancels' these 4 flows and starts another 4. (by now we ha=
ve
> 4 CANCELLED and 4 STARTED flows).
> ...and so on, resulting in 8, 16, 32, 64... workflows. Management
> sometimes like approving things - gives them a sense of power, but
> methinks this might be overdoing things a bit.
>
> Cancelling the flow manually has the same result - the linkage remains.
> Haven't found anything on OSS, but thought I'd post here before raising=
 a
> note.
>
> Anyone seen this? There are a few other oddities by the looks of things=
,
> but at this stage I still need to investigate some more...
>
> Cheers & hope you had a happy Christmas/Holiday/Mr.Hankey celebration a=
nd
> have an excellent New Year.
> Mike
>
>