AW: End Workflow after n-hours

[Mike Pokraka]

There are many scenarios that fit the bill and I use it a lot.

The most common is some noncritical task or a notification that you don't
want to have hanging around until 2080.

Or a process that is a 'nice to have'. "Please review details for new
customer". After 30 days it's safe to assume this task has become
irrelevant because either orders have already been shipped or the customer
has been created again or isn't interested anymore because of waiting so
long.

Far too many systems have open workflows from 2006 and the likes.
Basically it's also good practice to ensure your workflows complete. In
the last example I use a process control step to actually set it to
cancelled. This makes it easy to report on later to identify possible
process issues.

Cheers,
Mike


On Thu, April 10, 2008 12:51 pm, Marten, Michael wrote:
> Hello Chris,
> you wrote
> "I want a workflow to terminate itself after n hours because its
>  obsolete then".
> It would be interesting to hear the business background why at least one
> dialog step (or more than one in the branch) is obsolete/must be logically
> deleted - simply because a time period is over ;-)
>
> I have never thought about that and no scenario is coming into my mind.
>
> Regards, Michael
> P.S. I assumed that one of the branches contain at least one dialog step.
>
> -----Ursprüngliche Nachricht-----
> Von: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] Im Auftrag
> von Mike Pokraka
> Gesendet: 2008 Apr 10 13:28
> An: SAP Workflow Users' Group
> Betreff: Re: End Workflow after n-hours
>
> Use a wait step.
> This is simply a background task based on a custom WAIT method with no
> code. Put a requested start deadline of n hours.
> After n hours, workflow will start the task, execute all it's nothingness
> in a few milliseconds and terminate your fork.
>
> Of course being the simplest possible task, this is also a perfect example
> to give OO classes a go :-)
>
> Cheers,
> Mike
>
>
> On Thu, April 10, 2008 11:11 am, Christian Wallner wrote:
>> Hi WUGers!
>>
>> I have a question which I'm sure is easy to answer for some guys here:
>> I want a workflow to terminate itself after n hours because its
>> obsolete then. Basically the wf is quite simple, it consists of a
>> parallel section with 4 branches (1 out of 4 to complete). So my first
>> thought was a wait event in a 5th branch. But unfortunately I didn't
>> find out how to tell this step to terminate itself after wf creation
>> date+n hours.
>>
>> Any ideas?
>>
>> regards,
>> Chris
>>
>> AT&S Austria Technologie & Systemtechnik AG Legal form | Rechtsform:
>> Aktiengesellschaft Registered office | Sitz: Fabriksgasse 13, 8700
>> Leoben, Austria Commercial Register Number | Firmenbuchnummer: FN
>> 55638 x, Landesgericht Leoben
>>
>> This e-mail and any attachment may contain confidential and/or
>> privileged information. If you are not the intended recipient (or have
>> received this e-mail in error) please notify the sender immediately
>> and destroy this e-mail. Any unauthorised copying, disclosure or
>> distribution of the material in this e-mail is strictly forbidden.
>> _______________________________________________
>> SAP-WUG mailing list
>> SAP-WUG at mit.edu
>> http://mailman.mit.edu/mailman/listinfo/sap-wug
>>
>
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>