Terminating event does not cancel task (46C)

[Kjetil Kilhavn]

And suddenly they would also like a notification letter to the employee
when all plan activities have been reviewed :-)
I think they could have managed without it though...
--
Kjetil Kilhavn
 
 
 
 
 
                    "Dart, Jocelyn"
                    <jocelyn.dart at sap.co        To:     SAP-WUG at MITVMA.MIT.EDU
                    m>                          cc:     (bcc: Kjetil Kilhavn)
                    Sent by: SAP                Subject:     Re: Terminating event does not cancel task (46C)
                    Workflow
                    <Owner-SAP-WUG at MITVM
                    A.MIT.EDU>
 
 
                    02.04.2003 11:36
                    Please respond to
                    "SAP Workflow Users'
                    Group"
 
 
 
 
 
 
Yes solution is as Phil says but process control step is unnecessary if
fork is set to
"only one path of two is needed for fork to end".
 
There are discussions in the book on correct use of subflows for wait for
events which
is a similar scenario.
 
Even if you have only a one-step workflow its nearly always better to set
up a workflow
template so that you can easily add extra functionality.  There are a
number of things
it is awkward at best to do at task level and this is just one of those
scenarios.
 
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: Soady, Phil
Sent: Wednesday, 2 April 2003 5:11 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Terminating event does not cancel task (46C)
 
 
Try a small workflow instead of as task.
 
The task does what it should, except without the events.
 
The wf has triggering event.
The wf also has a fork parallel.
 
In the wait part of fork, wait for the event that should stop it.
When the wait event happens, in the follow step,
put a process control type 2.  KILL the wf.
 
Should get by the WI being committed. Since the WF is in status in process.
 
I didn't test this. But would expect it to work.
hope it does ;-)
 
Good luck
 
Phil Soady
Senior Consultant
Business Technologies
SAP Australia
* : 0412 213 079
* : phil.soady at sap.com
 
 
 
 
 
-----Original Message-----
From: Kjetil Kilhavn [mailto:kjetilk at statoil.com]
Sent: Wednesday, April 02, 2003 4:51 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Terminating event does not cancel task (46C)
 
 
I have created a task (TS) for approval of individual development plans -
career planning is close to the truth. The object is home-made with events
planChanged and itemSubmitted (for approval). The task has triggering and
terminating events, and the 'Confirm end of processing' flag has been set.
The method (and thus the task) is synchronous. The events are published by
a program that runs nightly.
 
The task responds nicely to the triggering event, creating a new work item
that lands in the managers workflow inbox. Unfortunately, the terminating
event does not function quite as perfectly. If the work item has status
Committed (i.e. executed without confirming end of processing) the log
shows
that the event was received, but the work item is not cancelled. If the
work item is in status Ready the log shows that the terminating event was
received and the work item is set in status Committed.
 
Thus the manager will receive a second work item if the plan is changed
again (new item submitted for approval) before the manager completed
handling the previously received work item. This was not what I had in mind
when I defined that terminating event.
 
No OSS notes seem to apply (at least not when searching with key words
terminating and event).
 
Does anyone know if the combination of 'Confirm end of processing' and a
terminating event impossible? I've looked in The Book without finding
anything. By impossible I mean useless, as there is no point in having a
terminating event unless it actually causes termination to happen.
Requiring an end
of processing confimation after a terminating event has been received makes
no sense.
 
I was hoping that for once I would be able to simply use a single task....
--
Kjetil Kilhavn
 
-------------------------------------------------------------------
The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorised use, dissemination of the
information or copying of this message is prohibited. If you are not the
addressee, please notify the sender immediately by return e-mail and delete
this
message. Thank you.
 
 
 
 
 
-------------------------------------------------------------------
The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorised use, dissemination of the
information or copying of this message is prohibited. If you are not the
addressee, please notify the sender immediately by return e-mail and delete
this message.
Thank you.