<br><font size=2 face="sans-serif">Thanks Jocelyn.</font>
<br>
<br><font size=2 face="sans-serif">I was thinking that passing the PDF
form as an attachment to the email would be a better approach...We have
several workflows where we need to send an email with the content of the
form (or the form as an attachment). If we decide to send just the
'content', if there is any changes to any of the forms, then we also will
always need to remember to update the SendMail step with the new data added
to the form. Also, as we are using several workflows with Forms, I thought
it would be 'easier' (from an implementation point of view) to send the
form as an attachment.</font>
<br>
<br><font size=2 face="sans-serif">Hard decision!</font>
<br>
<br><font size=2 face="sans-serif">Thanks again for your input,<br>
<br>
Cristiana<br>
_________________________________<br>
Cristiana d'Agosto<br>
IBM Global Business Services<br>
Mobile: +61 417 927 224<br>
cristiana.dagosto@au1.ibm.com</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>"Dart, Jocelyn"
<jocelyn.dart@sap.com></b> </font>
<br><font size=1 face="sans-serif">Sent by: sap-wug-bounces@mit.edu</font>
<p><font size=1 face="sans-serif">13/01/2009 11:43 AM</font>
<table border>
<tr valign=top>
<td bgcolor=white>
<div align=center><font size=1 face="sans-serif">Please respond to<br>
"SAP Workflow Users' Group" <sap-wug@mit.edu></font></div></table>
<br>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">"SAP Workflow Users' Group"
<sap-wug@mit.edu></font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">RE: [LIKELY JUNK]RE:Workflow and PDF
attachments</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2 color=blue face="Arial">Well Cristiana, Best practice
depends on a lot of factors. But I would suggest that usually we
pass the data rather than the form - it's the data that's important and
should be used to drive the workflow. Also the data takes up less
space than the form. >From what I see of your scenario you mainly
need the form as evidence of a digital signature. So you need to
keep a copy of the digitally signed form for audit purposes, but you may
be able to work with just the data for the rest of the process? Think
about it and talk it through with your business process owners. </font>
<br><font size=3> </font>
<br><font size=2 color=blue face="Arial">Regards,</font>
<br><font size=2 color=blue face="Arial">Jocelyn </font>
<br>
<br>
<hr><font size=2 face="Tahoma"><b>From:</b> sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu]
<b>On Behalf Of </b>Cristiana D'Agosto<b><br>
Sent:</b> Tuesday, 13 January 2009 11:09 AM<b><br>
To:</b> SAP Workflow Users' Group<b><br>
Subject:</b> [LIKELY JUNK]RE:Workflow and PDF attachments</font><font size=3><br>
</font>
<br><font size=2 face="sans-serif"><br>
Hi Jocelyn,</font><font size=3> <br>
</font><font size=2 face="sans-serif"><br>
that's good information, thanks.</font><font size=3> <br>
</font><font size=2 face="sans-serif"><br>
What is the best practice when you need to send the 'content' of the form
as an email? Is it best practice to somehow send the PDF as an attachment
to an email? I know we can import all the fields into the workflow and
then use the fields in the email step. Just wondering what is best practice
and any tips!</font><font size=3> <br>
</font><font size=2 face="sans-serif"><br>
Much thanks and regards,<br>
<br>
Cristiana<br>
_________________________________<br>
Cristiana d'Agosto<br>
IBM Global Business Services<br>
Mobile: +61 417 927 224<br>
cristiana.dagosto@au1.ibm.com</font><font size=3> <br>
<br>
</font>
<table width=100%>
<tr valign=top>
<td width=46%><font size=1 face="sans-serif"><b>"Dart, Jocelyn"
<jocelyn.dart@sap.com></b> <br>
Sent by: sap-wug-bounces@mit.edu</font><font size=3> </font>
<p><font size=1 face="sans-serif">13/01/2009 10:37 AM</font><font size=3>
</font>
<br>
<table border=4 width=100%>
<tr valign=top>
<td width=100% bgcolor=white>
<div align=center><font size=1 face="sans-serif">Please respond to<br>
"SAP Workflow Users' Group" <sap-wug@mit.edu></font></div></table>
<p>
<td width=53%>
<br>
<table width=100%>
<tr valign=top>
<td width=13%>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td width=86%><font size=1 face="sans-serif">"SAP Workflow Users'
Group" <sap-wug@mit.edu></font><font size=3> </font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">RE: [LIKELY JUNK]Workflow and PDF attachments</font></table>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=50%>
<td width=50%></table>
<br></table>
<br><font size=3><br>
<br>
</font><font size=2 color=blue face="Arial"><br>
Hi Akshay, <br>
Ok well if that is the scenario you might want to approach the problem
in a different way. Rather than pass attachments around, which is
always a pain when you have to convert between different formats, why not
just pass a reference number ? i.e. assign some sort of id to the
form. Your actual binary data representing the current known
form would be stored somewhere in SAP. Some applications such as
SAP HCM Workforce Process Management have used Records Management (transaction
SCASE) to store the binary/XML data of the form and then assign a GUID
as the reference that is passed throughout the workflow. Then your
ABAP WD application uses the reference to read/update the pdf. It's
not particularly important where you store it from workflow's point of
view - so long as you can use your form id to find the form data. </font><font size=3>
<br>
</font><font size=2 color=blue face="Arial"><br>
Trying to use SOFM - which is really only intended for creating and displaying
attachments - will be very restrictive. Also passing around a large
attachment in the workflow is likely to have other implications - e.g.
sizing issues. </font><font size=3> <br>
</font><font size=2 color=blue face="Arial"><br>
You might also want to look at the many Adobe tutorials on SDN. There
are various approaches to handling incoming PDF forms. <br>
Regards,</font><font size=3> </font><font size=2 color=blue face="Arial"><br>
Jocelyn</font><font size=3> <br>
<br>
</font>
<hr><font size=2 face="Tahoma"><b>From:</b> sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu]
<b>On Behalf Of </b>akshay.bhagwat@wipro.com<b><br>
Sent:</b> Saturday, 10 January 2009 12:55 PM<b><br>
To:</b> sap-wug@mit.edu<b><br>
Subject:</b> [LIKELY JUNK]Workflow and PDF attachments</font><font size=3><br>
</font><font size=2 face="Arial"><br>
Hi All,</font><font size=3> <br>
</font><font size=2 face="Arial"><br>
I know this topic is discussed a lot, still posting the questions as I
am not able to achieve the requirement.</font><font size=3> <br>
</font><font size=2 face="Arial"><br>
Just to elaborate the scenario, we are using Web dypnro for ABAP to host
Interactive form .</font><font size=3> </font><font size=2 face="Arial"><br>
This Form in turn triggers the workflow, as this form is to be approved
using workflow process. i.e. UWL will be used to launch the form when executing
the work items.</font><font size=3> <br>
</font><font size=2 face="Arial"><br>
As the form includes Digital signatures, we are not able to read the same
from contexts (e.g. using UWLs dynamic parameters such as WI_ID.) So we
have decided to use attachments i.e. send this form as an attachment inside
workflow, since saved PDF file has all the data intact.</font><font size=3>
<br>
</font><font size=2 face="Arial"><br>
Now the issue is: <br>
How this form in Webdynpro is to be saved as PDF file automatically and
then send as an attachment in workflow?</font><font size=3> <br>
</font><font size=2 face="Arial"><br>
1. I have tried using SAP Office function modules such as SO_OBJECT_UPLOAD
to create PDF files in SOFM object. However the problem is these FM s can
not be used from Webdynpro as Front end services are unavailable.</font><font size=3>
</font><font size=2 face="Arial"><br>
2. Same is the issue If I use background step for creating SOFM document
so that it can be used as an attachment.</font><font size=3> <br>
</font><font size=2 face="Arial"><br>
Can any body please suggest what approach can be taken so that from webdynpro
, attachment can be created and passed to workflow seamlessly?</font><font size=3>
<br>
</font><font size=2 face="Arial"><br>
Any inputs are appreciated.</font><font size=3> </font><font size=2 face="Arial"><br>
Thanks in advance.</font><font size=3> <br>
</font><font size=2 face="Arial"><br>
Regards</font><font size=3> </font><font size=2 face="Arial"><br>
Akshay Bhagwat</font><font size=3> </font>
<p><font size=2 color=#008000 face="Palatino Linotype"><b>Please do not
print this email unless it is absolutely necessary. </b></font>
<p><font size=3>The information contained in this electronic message and
any attachments to this message are intended for the exclusive use of the
addressee(s) and may contain proprietary, confidential or privileged information.
If you are not the intended recipient, you should not disseminate, distribute
or copy this e-mail. Please notify the sender immediately and destroy all
copies of this message and any attachments. </font>
<p><font size=3>WARNING: Computer viruses can be transmitted via email.
The recipient should check this email and any attachments for the presence
of viruses. The company accepts no liability for any damage caused by any
virus transmitted by this email. </font>
<p><font size=3>www.wipro.com </font><font size=2 face="Arial">_______________________________________________<br>
SAP-WUG mailing list<br>
SAP-WUG@mit.edu<br>
http://mailman.mit.edu/mailman/listinfo/sap-wug_______________________________________________<br>
SAP-WUG mailing list<br>
SAP-WUG@mit.edu<br>
http://mailman.mit.edu/mailman/listinfo/sap-wug<br>
</font>
<p>