<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Workflow deadline in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/workflow-deadline/m-p/2911667#M685154</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;   In my workflow i want to make one workitem obosolete if the workitem is not processed for 1 day can anybody tell  how to make it as osolete. were to to set the number of day or hours or minutes?how to to solve this?&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;srinivas&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 24 Oct 2007 06:51:52 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-10-24T06:51:52Z</dc:date>
    <item>
      <title>Workflow deadline</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/workflow-deadline/m-p/2911667#M685154</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;   In my workflow i want to make one workitem obosolete if the workitem is not processed for 1 day can anybody tell  how to make it as osolete. were to to set the number of day or hours or minutes?how to to solve this?&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;srinivas&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 24 Oct 2007 06:51:52 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/workflow-deadline/m-p/2911667#M685154</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-10-24T06:51:52Z</dc:date>
    </item>
    <item>
      <title>Re: Workflow deadline</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/workflow-deadline/m-p/2911668#M685155</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check the following links:&lt;/P&gt;&lt;P&gt;&lt;A href="http://sap-img.com/workflow/sap-workflow.htm" target="test_blank"&gt;http://sap-img.com/workflow/sap-workflow.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapbrainsonline.com/TUTORIALS/TECHNICAL/WORKFLOW_tutorial.html" target="test_blank"&gt;http://www.sapbrainsonline.com/TUTORIALS/TECHNICAL/WORKFLOW_tutorial.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://sapmaterial.com/workflow.html" target="test_blank"&gt;http://sapmaterial.com/workflow.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Bhaskar&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 24 Oct 2007 06:57:43 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/workflow-deadline/m-p/2911668#M685155</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-10-24T06:57:43Z</dc:date>
    </item>
    <item>
      <title>Re: Workflow deadline</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/workflow-deadline/m-p/2911669#M685156</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;use the modeled deadline and make the earlier step as obsolete using the step "Process control".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For using modeled deadline, check this: &lt;A href="http://saptechnical.com/Tutorials/Workflow/RecursiveMails/Scenario.htm" target="test_blank"&gt;http://saptechnical.com/Tutorials/Workflow/RecursiveMails/Scenario.htm&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 24 Oct 2007 07:43:57 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/workflow-deadline/m-p/2911669#M685156</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-10-24T07:43:57Z</dc:date>
    </item>
    <item>
      <title>Re: Workflow deadline</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/workflow-deadline/m-p/2911670#M685157</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi&lt;/P&gt;&lt;P&gt;good&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You have to define an obsolete path so that the workflow system knows which way to go when the step is made obsolete. At first glance this may seem unnecessary because most steps only have one outcome but it does allow a lot of flexibility.&lt;/P&gt;&lt;P&gt;It allows you to skip several successor steps in one go or define additional processing to take into account that a step has not been performed.&lt;/P&gt;&lt;P&gt;It also takes account of steps which have several outcomes. For example if a decision has two outcomes (approve/reject) you can let the obsolete path follow either one of the outcomes (e.g. accept).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;reward point if helpful,.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;P&gt;mrutyun^&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 24 Oct 2007 07:55:15 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/workflow-deadline/m-p/2911670#M685157</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-10-24T07:55:15Z</dc:date>
    </item>
  </channel>
</rss>

