<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'>
<br>Hello,<br><br>You don't really have to include the HREF tag. Just include the URL like http://url. When testing in SOST it may not show as a clickable link, however, when forwarded to Outlook it will be as Outlook will take care of that automatically. I also think there is a limit on the URL length but i'm not sure how many characters exactly. It should work fine with short URLs.<br><br>Hope this helps.<br>Ali<br><br><br>> From: sap-wug-request@mit.edu<br>> Subject: SAP-WUG Digest, Vol 73, Issue 12<br>> To: sap-wug@mit.edu<br>> Date: Thu, 23 Dec 2010 06:48:29 -0500<br>> <br>> Send SAP-WUG mailing list submissions to<br>> sap-wug@mit.edu<br>> <br>> To subscribe or unsubscribe via the World Wide Web, visit<br>> http://mailman.mit.edu/mailman/listinfo/sap-wug<br>> or, via email, send a message with subject or body 'help' to<br>> sap-wug-request@mit.edu<br>> <br>> You can reach the person managing the list at<br>> sap-wug-owner@mit.edu<br>> <br>> When replying, please edit your Subject line so it is more specific<br>> than "Re: Contents of SAP-WUG digest..."<br>> <br>> <br>> Today's Topics:<br>> <br>> 1. URL in Email Task (Lalitha Sankaran)<br>> 2. SAP_WAPI_WORKITEMS_TO_OBJECT returning same WF ID for<br>> different object keys (Manish Khanna)<br>> <br>> <br>> ----------------------------------------------------------------------<br>> <br>> Message: 1<br>> Date: Thu, 23 Dec 2010 03:19:07 -0500<br>> From: Lalitha Sankaran <lalisan@gmail.com><br>> Subject: URL in Email Task<br>> To: "SAP Workflow Users' Group" <sap-wug@mit.edu><br>> Message-ID:<br>> <AANLkTi=Ro+6YcGW6C_2O5B6GrL+GcjzA4AaFFjoj6XH1@mail.gmail.com><br>> Content-Type: text/plain; charset=ISO-8859-1<br>> <br>> Hi,<br>> <br>> We are looking to include a URL link in an email Task.<br>> So that the user is able to click on "Click here" and it will take<br>> them to the URL.<br>> <br>> We have tried<br>> <A HREF=&ZURL1&>Click Here</A> to record your time.<br>> <br>> where ZURL1 is a container element and contains the URL for the website.<br>> <br>> When looking at the email content in SOST , we are able to see it the<br>> way we want it,<br>> <br>> By the WF log displays it as is (just as it is in the task definition,<br>> with the code)<br>> <br>> not sure why the discrepency........<br>> <br>> Appreciate any input on this,<br>> <br>> Thanks<br>> Lalitha Sankaran<br>> <br>> <br>> ------------------------------<br>> <br>> Message: 2<br>> Date: Thu, 23 Dec 2010 17:18:18 +0530<br>> From: Manish Khanna <mkhanna@sapient.com><br>> Subject: SAP_WAPI_WORKITEMS_TO_OBJECT returning same WF ID for<br>> different object keys<br>> To: "sap-wug@mit.edu" <sap-wug@MIT.EDU><br>> Message-ID:<br>> <9F307AC6AA617F45B8848821D7D829462412CBFD6D@DELMAIL.sapient.com><br>> Content-Type: text/plain; charset="us-ascii"<br>> <br>> Hi,<br>> <br>> In our production scenario, there are 2 related contracts (ISUCONTRCT) for a contract account. For certain requirement I need to check if 2nd contract has its workflow triggered or not. If not then I'll have to manually trigger it.<br>> <br>> To achieve this, the first obvious step is to look for active workitems first contract. However when run in background, SAP_WAPI_WORKITEMS_TO_OBJECT is ignoring the object key and returning a different WI_ID. Not only that even if I use GOS from the main tcode for the business document - ES22, strangely it too gives incorrect results.<br>> <br>> Please see the screenshots.<br>> WF instance 722013 started for Contract 16954 only.<br>> [cid:image001.jpg@01CBA2C5.643DCD60]<br>> [cid:image003.jpg@01CBA2C5.643DCD60]<br>> <br>> ES22 - GOS<br>> Contract 16954<br>> [cid:image004.jpg@01CBA2C5.643DCD60]<br>> <br>> Contract 16955<br>> [cid:image008.jpg@01CBA2C5.643DCD60]<br>> <br>> As you can see it is giving incorrect results. Both are showing same WF instance for different object keys. This is very confusing. Any help on this.<br>> <br>> Thanks<br>> Manish<br>> -------------- next part --------------<br>> An HTML attachment was scrubbed...<br>> URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20101223/be156fce/attachment.htm<br>> -------------- next part --------------<br>> A non-text attachment was scrubbed...<br>> Name: image001.jpg<br>> Type: image/jpeg<br>> Size: 6605 bytes<br>> Desc: image001.jpg<br>> Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20101223/be156fce/image001.jpg<br>> -------------- next part --------------<br>> A non-text attachment was scrubbed...<br>> Name: image003.jpg<br>> Type: image/jpeg<br>> Size: 4682 bytes<br>> Desc: image003.jpg<br>> Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20101223/be156fce/image003.jpg<br>> -------------- next part --------------<br>> A non-text attachment was scrubbed...<br>> Name: image004.jpg<br>> Type: image/jpeg<br>> Size: 15117 bytes<br>> Desc: image004.jpg<br>> Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20101223/be156fce/image004.jpg<br>> -------------- next part --------------<br>> A non-text attachment was scrubbed...<br>> Name: image008.jpg<br>> Type: image/jpeg<br>> Size: 14615 bytes<br>> Desc: image008.jpg<br>> Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20101223/be156fce/image008.jpg<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>> End of SAP-WUG Digest, Vol 73, Issue 12<br>> ***************************************<br> </body>
</html>