<br><font size=2 face="sans-serif">Thanks. I did the something similar. However to identify source of approval I have to add custom method to the object. It accepts the WF id .</font>
<br>
<br><font size=2 face="sans-serif">Uday Malghan</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td>
<td><font size=1 face="sans-serif"><b>Paul Batey <paul.batey@intelligroup.com.au></b></font>
<br><font size=1 face="sans-serif">Sent by: SAP Workflow <Owner-SAP-WUG@MITVMA.MIT.EDU></font>
<p><font size=1 face="sans-serif">12/02/2004 09:34 PM</font>
<br><font size=1 face="sans-serif">Please respond to "SAP Workflow Users' Group"</font>
<br>
<td><font size=1 face="Arial"> </font>
<br><font size=1 face="sans-serif"> To: SAP-WUG@MITVMA.MIT.EDU</font>
<br><font size=1 face="sans-serif"> cc: </font>
<br><font size=1 face="sans-serif"> Subject: Re: Workitems are logically deleted</font></table>
<br>
<br>
<br><font size=2 face="Courier New">G'day,<br>
<br>
I would put the email step past the fork with a condition to send if approved. The fork should only contain the steps that would be redundant if the approval occurs outside of the workflow (ie the approval step).<br>
<br>
________________________________<br>
<br>
From: SAP Workflow on behalf of Uday Malghan<br>
Sent: Fri 3/12/2004 8:46 AM<br>
To: SAP-WUG@MITVMA.MIT.EDU<br>
Subject: Workitems are logically deleted<br>
<br>
<br>
<br>
HI Team,<br>
<br>
We have custom workflow for approving trip related expenses. Workflow is<br>
triggered whenever employee submits trip expense. I use Fork with two<br>
branches. First one for normal processing and second branch listens to<br>
Wait for Approval Event. I thought this will help me to complete workflow<br>
if trip is approved outside of workflow . In the normal approval process<br>
workflow is supposed to send e-mail notification to employee about the<br>
trip status.<br>
<br>
But what is happening that when the manager approves the trip via normal<br>
branch, Workflow is completed via 2nd branch instead of normal and all the<br>
post approval steps are with status "logically deleted". This happens on<br>
most of the Workflow and not all.<br>
<br>
Is their any way to distinguish the approval events created via workflow<br>
approvals from the approval outside of workflow?<br>
<br>
Any suggestions?<br>
<br>
Thanks,<br>
<br>
Uday Malghan<br>
</font>
<br>
<br>