<?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 Re: workflow debugging in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/workflow-debugging/m-p/1639068#M284761</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Mohammed&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Try SWUS with a break-point in the source-code - it works. Has the task a method with dialog? If not, the user is not your dialoguser but your workflow-background-user. And therefore the breakpoint doesn't work.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the task is a long running one, then you can use SM50 transaction, select the process associated with the workflow user id. In the menu, follow the path Program/Session --&amp;gt; Program --&amp;gt; Debugging.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But if the code gets executed really quick, it will be hard to select the process associated with it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Another way you can do this is simply to make your task a dialog task for the purposes of debugging. Then you have the ability to start it at will - and you are listed as the user, so you will hit the breakpoints (whereas in background mode you will never hit the breakpoints you set due to the user being WF-BATCH). Once you've figured out the bug you can set the task to background again.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However - be aware - I've encountered some bugs that seem to disappear because the task is now in dialog mode - at that point putting an endless loop into the method assigned to the task is pretty much your only option for debugging.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please let me know if this helps&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 25 Nov 2006 17:43:46 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2006-11-25T17:43:46Z</dc:date>
    <item>
      <title>workflow debugging</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/workflow-debugging/m-p/1639067#M284760</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;please furnish the proceedure how to debug a workflow.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Rahman&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 25 Nov 2006 13:12:09 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/workflow-debugging/m-p/1639067#M284760</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-11-25T13:12:09Z</dc:date>
    </item>
    <item>
      <title>Re: workflow debugging</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/workflow-debugging/m-p/1639068#M284761</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Mohammed&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Try SWUS with a break-point in the source-code - it works. Has the task a method with dialog? If not, the user is not your dialoguser but your workflow-background-user. And therefore the breakpoint doesn't work.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the task is a long running one, then you can use SM50 transaction, select the process associated with the workflow user id. In the menu, follow the path Program/Session --&amp;gt; Program --&amp;gt; Debugging.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But if the code gets executed really quick, it will be hard to select the process associated with it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Another way you can do this is simply to make your task a dialog task for the purposes of debugging. Then you have the ability to start it at will - and you are listed as the user, so you will hit the breakpoints (whereas in background mode you will never hit the breakpoints you set due to the user being WF-BATCH). Once you've figured out the bug you can set the task to background again.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However - be aware - I've encountered some bugs that seem to disappear because the task is now in dialog mode - at that point putting an endless loop into the method assigned to the task is pretty much your only option for debugging.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please let me know if this helps&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 25 Nov 2006 17:43:46 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/workflow-debugging/m-p/1639068#M284761</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-11-25T17:43:46Z</dc:date>
    </item>
    <item>
      <title>Re: workflow debugging</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/workflow-debugging/m-p/1639069#M284762</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Mohammad&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Some more tips&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;u cant debug work flow directly.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Workflow Trace On/Off - SWU8&lt;/P&gt;&lt;P&gt;Display - SWU9&lt;/P&gt;&lt;P&gt;Delete - SWU10.&lt;/P&gt;&lt;P&gt;-&lt;/P&gt;&lt;HR originaltext="----------------------------------------------" /&gt;&lt;P&gt;Work Item Analysis - SWI1&lt;/P&gt;&lt;P&gt;Identifying workflow for the work Item :&lt;/P&gt;&lt;P&gt;-&lt;/P&gt;&lt;HR originaltext="------------------------------------------------------------" /&gt;&lt;P&gt;Tx : SWI1 - Enter the workiem id which has been identified in workflow log&lt;/P&gt;&lt;P&gt;The details consists of workflow of the workitem. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;WorkFlow Errors :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Workflow Not Started - Using Event Trace we can Identify&lt;/P&gt;&lt;P&gt;2. Started but No Proceeded - Wrong Object Keys&lt;/P&gt;&lt;P&gt;3. Problem in Work Item Execution&lt;/P&gt;&lt;P&gt;Dialog Work Item - Agent Determinaion Error ( Position,Role,User )&lt;/P&gt;&lt;P&gt;- Role Resolution Error&lt;/P&gt;&lt;P&gt;Reqd Element would no be &lt;/P&gt;&lt;P&gt;Set in Binding &lt;/P&gt;&lt;P&gt;Background Work Item - Make Foreground and Test once Sucessfull make it Back round&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 25 Nov 2006 17:44:22 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/workflow-debugging/m-p/1639069#M284762</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-11-25T17:44:22Z</dc:date>
    </item>
    <item>
      <title>Re: workflow debugging</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/workflow-debugging/m-p/1639070#M284763</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi &lt;/P&gt;&lt;P&gt;There are ways if you are interested to see the contents of the task containers (variables) in a worlflow.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After executing the workflow, &lt;/P&gt;&lt;P&gt;1. Go to transaction SWIA ( Process workitems). &lt;/P&gt;&lt;P&gt;2. Now click the execute button. It will display list of &lt;/P&gt;&lt;P&gt;workitems.&lt;/P&gt;&lt;P&gt;3. Select the appropriate workitem and click the "Display &lt;/P&gt;&lt;P&gt;work flow log" button.&lt;/P&gt;&lt;P&gt;4. "Workflow log" screen will appear&lt;/P&gt;&lt;P&gt;5. Press the button "List with technical details" button&lt;/P&gt;&lt;P&gt;6. "Workflow log (List with technical details)" screen &lt;/P&gt;&lt;P&gt;will appear.&lt;/P&gt;&lt;P&gt;7. Click "Show work item container" icon in the &lt;/P&gt;&lt;P&gt;displayed table ot details.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 25 Nov 2006 17:45:15 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/workflow-debugging/m-p/1639070#M284763</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-11-25T17:45:15Z</dc:date>
    </item>
    <item>
      <title>Re: workflow debugging</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/workflow-debugging/m-p/1639071#M284764</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;thanks...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 26 Nov 2006 09:57:24 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/workflow-debugging/m-p/1639071#M284764</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-11-26T09:57:24Z</dc:date>
    </item>
  </channel>
</rss>

