Task Wait for event and deadline delay

Tue Jun 21 10:54:42 EDT 2005

Eric,

If I have understood you correctly...

Create a fork. In one branch put the wait for event. In the other branch put a task that does nothing but waits (CCPSUPPORT.NoOperation). Configure the fork so that when one of the branches is completed the fork is killed. That way, if either branch is executed (event is received or deadline expires - which ever happens first) your WF will continue. 

If due to the layout/design of your WF you can not put the two steps (Wait for event and Wait for deadline) in the same fork then use a Process Control step to eliminate 'the other' step when one is executed. For example, if the deadline expires then use a process control step to 'logically delete' the Wait for event. If the wait for event happens firs then use a process control step to logically delete the deadline step.  Please note that you may need to do several Process control steps if you need to kill the whole branch rather then just one step. A trick I use is to create a Fork in parallel with the branch that I want to kill. I then just kill the fork and it takes care of killing the whole branch. Much neater.

Regards,

Alon Raskin
e: araskin at 3i-consulting.com <mailto:araskin at 3i-consulting.com> 
p: +61 3 9625 2189 (Head Office)
f:  +61 3 8610 1239 
c:  +1 207 756 0370
w: http://www.3i-consulting.com

________________________________

From: sap-wug-bounces at mit.edu on behalf of Caillet, Eric
Sent: Tue 6/21/2005 10:40
To: SAP Workflow Users' Group
Subject: RE: Task Wait for event and deadline delay

Hi,

I agree with you and I did all that. Well I summarize what I did in my workflow example :

-          create a new BOR named ZTEST with one key field and one event : ChangeStatus ;

-          create a new workflow with a new element in container : ZELEMENT, a object type ZERCA ;

-          in the new workflow I create a new event "Wait for event" task with ZELEMENT like container element and ChangeStatus event. In the outcomes tab I've selected "Wait step terminated", "Latest end" and "Processing obsolete".

-          In the "Latest end" tab, Refer. Date/time is Work item creation + 2 minutes

Well, in my workflow I've one task and 3 steps (Event arrived, Obsolete, Deadline). I launch my workflow and when the deadline is arrived, workflow isn't stopped, in the protocol workflow, at the wait event line I see Deadline reached, that's all.

Regards,

Eric C.

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Kjetil Kilhavn
Sent: mardi 21 juin 2005 14:37
To: SAP Workflow Users' Group
Subject: RE: Task Wait for event and deadline delay

Remember, in addition to defining the deadline and naming the outcome you must activate the outcome (Outcomes tab). I assume you have done that since you say you can observe the deadline being reached. To get the "Processing obsolete" outcome you must activate it and add a process control step to the modelled deadline handling branch (e.g. "Latest end reached!"). The process control step is used to obsolete the step that has reached its deadline (or another step if you choose to). Just add the step and you'll see how it is done.

-- 

Kjetil Kilhavn, Statoil KTJ IT BKS

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Caillet, Eric
Sent: 21. juni 2005 14:09
To: SAP Workflow Users' Group
Subject: RE : Task Wait for event and deadline delay

Dear Jocelyn,

thanks for your answer.

Well, in my business scenario i'm waiting a event, if the event arrive in the limit of work item creation + 2 days i take a action and if the event don't arrive at the limit i want to take a another action (for exemple, notification email).

What i don't understand this is why SAP put on the task deadline informations ? when i look the protocol's worklow and particulary the waiting a event task, deadline is arrived but the event is always in progress... it don't stop ?

Regards,

Eric C.

________________________________

De: sap-wug-bounces at mit.edu de la part de Dart, Jocelyn
Date: mar. 21/06/2005 05:03
À: SAP Workflow Users' Group
Objet : RE: Task Wait for event and deadline delay

Eric, 

It's not generally a good idea to put deadlines directly on terminating events such as "wait for event". 

I'm not clear on what you are trying to achieve in your business scenario.  Do you not want to handle the event at all if it occurs within 2 days of work item creation? Or do you want to take action at work item + 2 days regardless of whether the event has arrived or not?

Regards, 
Jocelyn Dart 
Senior Consultant 
SAP Australia Pty Ltd. 
Level 1/168 Walker St. 
North Sydney 
NSW, 2060 
Australia 
T   +61 412 390 267 
M   + 61 412 390 267 
E   jocelyn.dart at sap.com 
http://www.sap.com <http://www.sap.com/>  

The information contained in or attached to this electronic transmission is confidential and may be legally privileged. It is intended only for the person or entity to which it is addressed. If you are not the intended recipient, you are hereby notified that any distribution, copying, review, retransmission, dissemination or other use of this electronic transmission or the information contained in it is strictly prohibited. If you have received this electronic transmission in error, please immediately contact the sender to arrange for the return of the original documents. 

Electronic transmission cannot be guaranteed to be secure and accordingly, the sender does not accept liability for any such data corruption, interception, unauthorized amendment, viruses, delays or the consequences thereof.

Any views expressed in this electronic transmission are those of the individual sender, except where the message states otherwise and the sender is authorized to state them to be the views of SAP AG or any of its subsidiaries. SAP AG, its subsidiaries, and their directors, officers and employees make no representation nor accept any liability for the accuracy or completeness of the views or information contained herein. Please be aware that the furnishing of any pricing information/ business proposal herein is indicative only, is subject to change and shall not be construed as an offer or as constituting a binding agreement on the part of SAP AG or any of its subsidiaries to enter into any relationship, unless otherwise expressly stated. 

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Caillet, Eric
Sent: Tuesday, 21 June 2005 12:55 AM
To: SAP Workflow Users' Group
Subject: Task Wait for event and deadline delay

Hi all,

i want that my workflow awaits an event so i've used task "Wait for event" and i want that this event is to subjected to a time constraint so, in my task i put information delay : "work item creation" + 2 days. Ok. Now, when the deadline is arrived, in the workflow's protocol i can watch that the deadline is arrived but workflow don't connect to other connection like obsolete or deadline.

Can i do that ? If not how can i circumvent this ?

Thanks so much.

Eric C.

-------------------------------------------------------------------
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.

This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/ms-tnef
Size: 17299 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20050621/e50bbd23/attachment.bin