<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.16757" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=822320101-13012009><FONT face=Arial
color=#0000ff size=2>That's fine... so long as you have thought it
through. Makes it more complicated for you though. Good luck!
Jocelyn</FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> sap-wug-bounces@mit.edu
[mailto:sap-wug-bounces@mit.edu] <B>On Behalf Of </B>Cristiana
D'Agosto<BR><B>Sent:</B> Tuesday, 13 January 2009 11:52 AM<BR><B>To:</B> SAP
Workflow Users' Group<BR><B>Subject:</B> [LIKELY JUNK]RE:RE:Workflow and PDF
attachments<BR></FONT><BR></DIV>
<DIV></DIV><BR><FONT face=sans-serif size=2>Thanks Jocelyn.</FONT> <BR><BR><FONT
face=sans-serif size=2>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 face=sans-serif size=2>Hard decision!</FONT> <BR><BR><FONT
face=sans-serif size=2>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%">
<TBODY>
<TR vAlign=top>
<TD width="40%"><FONT face=sans-serif size=1><B>"Dart, Jocelyn"
<jocelyn.dart@sap.com></B> </FONT><BR><FONT face=sans-serif
size=1>Sent by: sap-wug-bounces@mit.edu</FONT>
<P><FONT face=sans-serif size=1>13/01/2009 11:43 AM</FONT>
<TABLE border=1>
<TBODY>
<TR vAlign=top>
<TD bgColor=white>
<DIV align=center><FONT face=sans-serif size=1>Please respond
to<BR>"SAP Workflow Users' Group"
<sap-wug@mit.edu></FONT></DIV></TR></TBODY></TABLE><BR></P>
<TD width="59%">
<TABLE width="100%">
<TBODY>
<TR vAlign=top>
<TD>
<DIV align=right><FONT face=sans-serif size=1>To</FONT></DIV>
<TD><FONT face=sans-serif size=1>"SAP Workflow Users' Group"
<sap-wug@mit.edu></FONT>
<TR vAlign=top>
<TD>
<DIV align=right><FONT face=sans-serif size=1>cc</FONT></DIV>
<TD>
<TR vAlign=top>
<TD>
<DIV align=right><FONT face=sans-serif size=1>Subject</FONT></DIV>
<TD><FONT face=sans-serif size=1>RE: [LIKELY JUNK]RE:Workflow and
PDF attachments</FONT></TR></TBODY></TABLE><BR>
<TABLE>
<TBODY>
<TR vAlign=top>
<TD>
<TD></TR></TBODY></TABLE><BR></TR></TBODY></TABLE><BR><BR><BR><FONT face=Arial
color=blue size=2>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 face=Arial color=blue
size=2>Regards,</FONT> <BR><FONT face=Arial color=blue size=2>Jocelyn
</FONT><BR><BR>
<HR>
<FONT face=Tahoma size=2><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 face=sans-serif
size=2><BR>Hi Jocelyn,</FONT><FONT size=3> <BR></FONT><FONT face=sans-serif
size=2><BR>that's good information, thanks.</FONT><FONT size=3> <BR></FONT><FONT
face=sans-serif size=2><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 face=sans-serif
size=2><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%">
<TBODY>
<TR vAlign=top>
<TD width="46%"><FONT face=sans-serif size=1><B>"Dart, Jocelyn"
<jocelyn.dart@sap.com></B> <BR>Sent by:
sap-wug-bounces@mit.edu</FONT><FONT size=3> </FONT>
<P><FONT face=sans-serif size=1>13/01/2009 10:37 AM</FONT><FONT size=3>
</FONT><BR>
<TABLE width="100%" border=4>
<TBODY>
<TR vAlign=top>
<TD width="100%" bgColor=white>
<DIV align=center><FONT face=sans-serif size=1>Please respond
to<BR>"SAP Workflow Users' Group"
<sap-wug@mit.edu></FONT></DIV></TR></TBODY></TABLE>
<P></P>
<TD width="53%"><BR>
<TABLE width="100%">
<TBODY>
<TR vAlign=top>
<TD width="13%">
<DIV align=right><FONT face=sans-serif size=1>To</FONT></DIV>
<TD width="86%"><FONT face=sans-serif size=1>"SAP Workflow Users'
Group" <sap-wug@mit.edu></FONT><FONT size=3> </FONT>
<TR vAlign=top>
<TD>
<DIV align=right><FONT face=sans-serif size=1>cc</FONT></DIV>
<TD>
<TR vAlign=top>
<TD>
<DIV align=right><FONT face=sans-serif size=1>Subject</FONT></DIV>
<TD><FONT face=sans-serif size=1>RE: [LIKELY JUNK]Workflow and PDF
attachments</FONT></TR></TBODY></TABLE><BR><BR>
<TABLE width="100%">
<TBODY>
<TR vAlign=top>
<TD width="50%">
<TD width="50%"></TR></TBODY></TABLE><BR></TR></TBODY></TABLE><BR><FONT
size=3><BR><BR></FONT><FONT face=Arial color=blue size=2><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
face=Arial color=blue size=2><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 face=Arial color=blue size=2><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
face=Arial color=blue size=2><BR>Jocelyn</FONT><FONT size=3> <BR><BR></FONT>
<HR>
<FONT face=Tahoma size=2><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 face=Arial size=2><BR>Hi
All,</FONT><FONT size=3> <BR> </FONT><FONT face=Arial size=2><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 face=Arial
size=2><BR>Just to elaborate the scenario, we are using Web dypnro for ABAP to
host Interactive form .</FONT><FONT size=3> </FONT><FONT face=Arial
size=2><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 face=Arial
size=2><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 face=Arial size=2><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 face=Arial
size=2><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 face=Arial size=2><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 face=Arial
size=2><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 face=Arial size=2><BR>Any
inputs are appreciated.</FONT><FONT size=3> </FONT><FONT face=Arial
size=2><BR>Thanks in advance.</FONT><FONT size=3> <BR> </FONT><FONT
face=Arial size=2><BR>Regards</FONT><FONT size=3> </FONT><FONT face=Arial
size=2><BR>Akshay Bhagwat</FONT><FONT size=3> </FONT>
<P><FONT face="Palatino Linotype" color=#008000 size=2><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 face=Arial
size=2>_______________________________________________<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></P></BODY></HTML>