<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
        {font-family:"MS Mincho";
        panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
        {font-family:"\@MS Mincho";
        panose-1:2 2 6 9 4 2 5 8 3 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman";}
a:link, span.MsoHyperlink
        {color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {color:purple;
        text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Courier New";}
@page Section1
        {size:8.5in 11.0in;
        margin:1.0in 32.35pt 1.0in 32.35pt;}
div.Section1
        {page:Section1;}
-->
</style>
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoPlainText><font size=3 face="Courier New"><span style='font-size:
12.0pt'>Hello All,<o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face="Courier New"><span style='font-size:
12.0pt'>I have the requirement to initiate a workflow from the population of an
Adobe Form via WebDynpro. We've been able to trigger the workflow just fine,
however, the PDF attachment (the adobe form) will not open. The message says
that the attachment is corrupted. I found a whitepaper on SDN from R.Reddy that
talks about this, however, when following his process it still does not work
for us. <o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face="Courier New"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoPlainText><font size=3 face="Courier New"><span style='font-size:
12.0pt'>Has anyone gone through this before? Are there snags in the XSTRING to
BINARY then binary back to xstring conversion that we should watch out for? Again
the PDF needs to be attached via batch mode. All suggestions are appreciated.<o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face="Courier New"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoPlainText><font size=3 face="Courier New"><span style='font-size:
12.0pt'>George Knoske<o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face="Courier New"><span style='font-size:
12.0pt'>Business Analyst Technical <o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face="Courier New"><span style='font-size:
12.0pt'>Kao Brands Company<o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face="Courier New"><span style='font-size:
12.0pt'>Cincinnati, OH 45214<o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face="Courier New"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
</div>
</body>
</html>