<br><font size=2 face="sans-serif">Hi!</font>
<br>
<br><font size=2 face="sans-serif">At first, Thanks Florin, Thanks Mike,
thats so simple it didn't come into my mind ;)</font>
<br><font size=2 face="sans-serif">Michael, the business background is:
</font>
<br><font size=2 face="sans-serif">When critical errors to an inspection
lot (QM) are raised (measured values out of range) than this workflow (in
standard: WS00200081) is started. Than an operator in our production is
informed about that and has to re-dose chemicals in our production line.
After a defined amount of time, unprocessed workflows are obsolete because
re-dosing could be more damaging than helpful (because maybe other workflows
of the same production line have been processed in the meantime). I know,
not the cleanest solution, but works for us ;)</font>
<br>
<br><font size=2 face="sans-serif">regards,</font>
<br><font size=2 face="sans-serif">chris</font>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>"Marten, Michael"
<michael.marten@philips.com></b> </font>
<br><font size=1 face="sans-serif">Gesendet von: sap-wug-bounces@mit.edu</font>
<p><font size=1 face="sans-serif">10.04.2008 13:51</font>
<table border>
<tr valign=top>
<td bgcolor=white>
<div align=center><font size=1 face="sans-serif">Bitte antworten an<br>
"SAP Workflow Users' Group" <sap-wug@mit.edu></font></div></table>
<br>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">An</font></div>
<td><font size=1 face="sans-serif">"SAP Workflow Users' Group"
<sap-wug@mit.edu></font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Kopie</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Thema</font></div>
<td><font size=1 face="sans-serif">AW: End Workflow after n-hours</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><tt><font size=2>Hello Chris,<br>
you wrote<br>
"I want a workflow to terminate itself after n hours because its<br>
obsolete then".<br>
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 ;-)<br>
<br>
I have never thought about that and no scenario is coming into my mind.<br>
<br>
Regards, Michael<br>
P.S. I assumed that one of the branches contain at least one dialog step.<br>
<br>
-----Ursprüngliche Nachricht-----<br>
Von: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] Im Auftrag
von Mike Pokraka<br>
Gesendet: 2008 Apr 10 13:28<br>
An: SAP Workflow Users' Group<br>
Betreff: Re: End Workflow after n-hours<br>
<br>
Use a wait step.<br>
This is simply a background task based on a custom WAIT method with no
code. Put a requested start deadline of n hours.<br>
After n hours, workflow will start the task, execute all it's nothingness
in a few milliseconds and terminate your fork.<br>
<br>
Of course being the simplest possible task, this is also a perfect example
to give OO classes a go :-)<br>
<br>
Cheers,<br>
Mike<br>
<br>
<br>
On Thu, April 10, 2008 11:11 am, Christian Wallner wrote:<br>
> Hi WUGers!<br>
><br>
> I have a question which I'm sure is easy to answer for some guys here:<br>
> I want a workflow to terminate itself after n hours because its<br>
> obsolete then. Basically the wf is quite simple, it consists of a<br>
> parallel section with 4 branches (1 out of 4 to complete). So my first<br>
> thought was a wait event in a 5th branch. But unfortunately I didn't<br>
> find out how to tell this step to terminate itself after wf creation
date+n hours.<br>
><br>
> Any ideas?<br>
><br>
> regards,<br>
> Chris<br>
><br>
> AT&S Austria Technologie & Systemtechnik AG Legal form | Rechtsform:<br>
> Aktiengesellschaft Registered office | Sitz: Fabriksgasse 13, 8700<br>
> Leoben, Austria Commercial Register Number | Firmenbuchnummer: FN<br>
> 55638 x, Landesgericht Leoben<br>
><br>
> This e-mail and any attachment may contain confidential and/or<br>
> privileged information. If you are not the intended recipient (or
have<br>
> received this e-mail in error) please notify the sender immediately<br>
> and destroy this e-mail. Any unauthorised copying, disclosure or<br>
> distribution of the material in this e-mail is strictly forbidden.<br>
> _______________________________________________<br>
> SAP-WUG mailing list<br>
> SAP-WUG@mit.edu<br>
> http://mailman.mit.edu/mailman/listinfo/sap-wug<br>
><br>
<br>
<br>
_______________________________________________<br>
SAP-WUG mailing list<br>
SAP-WUG@mit.edu<br>
http://mailman.mit.edu/mailman/listinfo/sap-wug<br>
<br>
_______________________________________________<br>
SAP-WUG mailing list<br>
SAP-WUG@mit.edu<br>
http://mailman.mit.edu/mailman/listinfo/sap-wug<br>
</font></tt>
<br><small><br><br>AT&S Austria Technologie & Systemtechnik AG<br>
Legal form | Rechtsform: Aktiengesellschaft<br>
Registered office | Sitz: Fabriksgasse 13, 8700 Leoben, Austria<br>
Commercial Register Number | Firmenbuchnummer: FN 55638 x, Landesgericht Leoben <br><br>
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.
</small>