<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1505" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Tahoma">
<DIV>"Set 'Latest End' DM & enable 'Processing obsolete' for an outcome"</DIV>
<DIV>Interesting! And raises some more questions for me now that I looked at it. </DIV>
<DIV>We don't use Deadline processing much so please bare with me. We have enough </DIV>
<DIV>problems with performance without throwing thousands of batch progs at the system </DIV>
<DIV>every 20 minutes. </DIV>
<DIV> </DIV>
<DIV>When testing in development with very low Requested Start in task and </DIV>
<DIV>low RSWWDHEX settings (1 minute and 3 minutes respectively), I noticed </DIV>
<DIV>some interesting issues. </DIV>
<DIV>Just in dev. Don't run these settings in prod! Performance thing. (Unless you like getting Tarred and Feathered!)</DIV>
<DIV> </DIV>
<DIV>1. Locking issues. </DIV>
<DIV>No doubt due to the RSWWDHEX running multiple times with above settings. </DIV>
<DIV>When this happens my tasks sometimes hang. </DIV>
<DIV>So, next time RSWWDHEX runs it sees nothing to do and the task is just stuck until manually set. </DIV>
<DIV>Sound correct?</DIV>
<DIV> </DIV>
<DIV>2. Table SWDSSTEPS.</DIV>
<DIV>When, what, and how do these entries get cleared out of the table? </DIV>
<DIV>I noticed over 9,000 entries in dev and I know I don't have _anything_ in waiting.</DIV>
<DIV>All entries are zeros for time/date. </DIV>
<DIV> </DIV>
<DIV>3. Will "Set 'Latest End' DM & enable 'Processing obsolete' for an outcome" pickup </DIV>
<DIV>these tasks and complete the step if for any reason the RSWWDHEX misses the deadline?</DIV>
<DIV>And, then will they get cleared if it hangs on the Requested Start? </DIV>
<DIV> </DIV>
<DIV>4. How do I clear old timers for any task / WF that I no longer want to monitor? </DIV>
<DIV>Example, old WF versions that we not longer want to use Deadlines. </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>Thanks!</DIV>
<DIV>4.6c</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV><BR> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>Rick Sample<BR>SAP Workflow Analyst/Developer<BR>Graybar, Inc.<BR>11885 Lackland Rd.<BR>63146-4208<BR>314.573.5822<BR><A href="mailto:Rick.Sample@GBE.com">Rick.Sample@GBE.com</A></DIV>
<DIV><BR>>>> Jeff@Business-Workflow.com 6/22/2005 12:02 >>><BR>Sushil,<BR><BR>You could use the Modeled option on your 'Latest End' <BR>DM & enable 'Processing obsolete' for an outcome. Then <BR>place the mail step after the DM leg & then a 'Process <BR>Control' Step that 'Sets the work item to Obsolete' using <BR>that original DM Step as the 'WF Step' entry. Let me know <BR>if you have any problems & I can show you some screen <BR>shots.<BR><BR>Jeff Rappaport<BR><U><A href="http://www.business-workflow.com/">www.Business-Workflow.com</A></U> <BR><BR><BR>---- Original message ----<BR>>Date: Wed, 22 Jun 2005 10:25:35 -0500<BR>>From: "Sushil Guragain" <<U> <A href="mailto:sguragain@interpublic.com">sguragain@interpublic.com</A></U> ><BR>>Subject: deadline monitoring loop<BR>>To: "SAP Workflow Users' Group" <<U> <A href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</A></U> ><BR>><BR>> Hello WF Gurus,<BR>> <BR>> I am trying to create a loop on deadline monitoring<BR>> so that it will keep sending email until the user<BR>> takes an action. I am planning to send email every<BR>> 24 hours until it is approved or declined. Is there<BR>> a standard way to get this activated? I tried using<BR>> deadline monitoring with 24 hours and found that it<BR>> sends the notification once and that is it. Would it<BR>> work if I put that in a loop? If so what do I check<BR>> against to see if the work item is complete?<BR>> <BR>> Thank you for your suggestions in advance!<BR>> <BR>> Sushil<BR>><BR>> This message contains information which may be <BR>confidential and privileged.<BR>> Unless you are the intended recipient (or authorized to <BR>receive this message<BR>> for the intended recipient), you may not use, copy, <BR>disseminate or disclose to<BR>> anyone the message or any information contained in the <BR>message. If you have<BR>> received the message in error, please advise the sender <BR>by reply e-mail, and<BR>> delete the message. Thank you very much.<BR>> (A)<BR>>________________<BR>>_______________________________________________<BR>>SAP-WUG mailing list<BR>><U> <A href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</A></U> <BR>><U> <A href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</A></U> <BR>Jeffrey A. Rappaport<BR>Business Workflow, LLC<BR>voice: (732)355-0123<BR>fax: (509)757-4144<BR>email: <U><A href="mailto:Jeff@Business-Workflow.com">Jeff@Business-Workflow.com</A></U> <BR>web: <U><A href="http://www.business-workflow.com/">www.Business-Workflow.com</A></U> <BR>_______________________________________________<BR>SAP-WUG mailing list<BR><U><A href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</A></U> <BR><U><A href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</A></U> <BR><BR></DIV></BODY></HTML>