Task Wait for event and deadline delay

[Mike Pokraka]

Hi Eric,
What I meant was not to use a deadline on the wait step at all, because -
as you've discovered - it doesn't work. So, instead of a deadline on the
wait step, use a requested start deadline on a step that simply executes
and does nothing:
(best viewed in Courier font)
        fork
      /       \
     |         |
     |         |
 [Wait]  [Empty step]   <--- this one has a requested start
     |         |
     |         |
      \       /
      end fork

Cheers
Mike

Caillet, Eric wrote:
> Hi all, :))
>
> my english is too bad so idon't know if  i well understand myself. I wrote
> a simple exemple, you can throw an eye :
>
> http://perso.wanadoo.fr/eric.caillet/workflow.htm
>
> Regards,
> Eric C.
>
>
>
> ________________________________
>
> De: sap-wug-bounces at mit.edu de la part de Mike Pokraka
> Date: jeu. 23/06/2005 14:08
> À: SAP Workflow Users' Group
> Objet : Re: RE : Task Wait for event and deadline delay
>
>
>
> Hi Eric,
> Create a dummy step that does nothing, and put it in a fork parallel to
> your wait for event:
>
> Branch A -> Wait for event
> Branch B -> Wait step (dummy method) with requested start of 2 days.
>
> After 2 days the step in branch B will execute, terminating the fork and
> killing the wait for event step.
>
> Cheers
> Mike
>
> Caillet, Eric wrote:
>>
>> Hi Mike,
>>
>> sorry i don't understand your answer : create a wait step in a parallel
>> branch, ok but what's about my deadline ?
>>
>> Regards,
>> Eric C.
>>
>> ________________________________
>>
>> De: sap-wug-bounces at mit.edu de la part de Mike Pokraka
>> Date: mar. 21/06/2005 17:14
>> À: SAP Workflow Users' Group
>> Objet : RE: Task Wait for event and deadline delay
>>
>>
>>
>> Hi Eric,
>> I'm not too sure but I think I tried that some time back with the same
>> result.
>> Your best bet is to use a wait step in a parallel branch.
>> Cheers
>> Mike
>>
>> Caillet, Eric wrote:
>>> 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.
>>>
>>>
>
>
> Mike Pokraka
> Senior Consultant
> Workflow Connections Ltd.
> Mobile: +44 (0)7786 910 855
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
>
>
> 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.
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>


Mike Pokraka
Senior Consultant
Workflow Connections Ltd.
Mobile: +44 (0)7786 910 855