Stop deadline handling during runtime

[Becker Stephan (extern)]

Frank,
 
thinking about this a bit more, I would still advocate not to try to
surgically alter the inner workings of the workflow engine, which would, I
assume, give you problems no end, and cost you a lot of time to boot.
 
I could imagine this the following way: The first step in the modelled
deadline step checks if it is one of those exceptions, and if it is so, you
set a flag which you test in the branch that follows the event "workitem
obsolete" of your main workitem. Then, you can lopp around to the original
item again. The user would not see anything, apart from the fact that the
workitem disappears and re-appears in a "clean" state directly thereafter.
That should allow you to model the behaviour you like.
 
Might this work?
 
Regards,
Stephan
 
 
-----Original Message-----
From: Frank Reichenbach [mailto:frankreichenbach at dontgotmail.com]
Sent: Donnerstag, 10. Januar 2002 10:35
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Stop deadline handling during runtime
 
 
Hi Stephan,
I do have a modelled deadline using container elements and setting the
workitem obsolete in case a container element is set.
The problem is that I need to build a processs that has the possibility of
stoping the deadline monitoring of a specific workitem, then do some changes
on it (change its container or execute it or forward it to a different user)
and under some circumstances reactivte the deadline handling for that WI
again.
I found FM SWW_WI_DEADLINES_CHANGE but I am not really able to handle it
properly. Plus I am not sure if it could be used once the deadline has been
reached to set a new latest-end deadline.
I would be very thanksful, if I could do it using just the workflow itself
but in this case I doubt that it can be done.
But thanks for your reply anyway!
 
Regards,
 
Frank
 
 
--- "Becker Stephan (extern)" <Stephan.Becker.ext at mchw.siemens.de> wrote:
>Frank,
>
>why not model the processing in the workflow as a modelled deadline? You
>should be able to control the behaviour of the system to the degree you
>need.
>Surely that must be easier and cleaner than trying to twist the arm of the
>workflow engine, which I would think would be very painful and risky..
>
>Stephan
>
>-----Original Message-----
>From: Frank Reichenbach [mailto:frankreichenbach at dontgotmail.com]
>Sent: Mittwoch, 9. Januar 2002 18:49
>To: SAP-WUG at MITVMA.MIT.EDU
>Subject: Stop deadline handling during runtime
>
>
>Hi everyone,
>   I've created a workflow that includes a step with a "latest end"
>deadline. During runtime I'm would like to use an external abap program to
>prevent the WFMS from reacting - creating a deadline WI/going into the
>deadline handling part of the workflow- even if the deadline is reached.
>E.g. call some FM etc. passing in the WI_ID that makes the WFMS simply
>ignore the deadline. In addition to this I would need a FM that does the
>opposite: after preventing the deadline monitoring for a certain WI, I
would
>like to reactivate it using an external abap.
>Any suggestions are very welcome!
>
>Regards,
>
>Frank
>
>_____________________________________________________________
>===========================
>Kick start your hits today with www.SearchGalore.com! Be in the #1 spot for
>as little as one cent.
>===========================
>Get YOUR FREE email address today! http://www.dontgotmail.com
>"Don't Got Mail!"
 
_____________________________________________________________
===========================
Kick start your hits today with www.SearchGalore.com! Be in the #1 spot for
as little as one cent.
===========================
Get YOUR FREE email address today! http://www.dontgotmail.com
"Don't Got Mail!"