[LIKELY JUNK]RE: [LIKELY JUNK]Workflow and PDF attachments

[Dart, Jocelyn]

Hi Akshay, 
Well if you are already storing your PDFSource data in a custom table
then surely you would just:
1. Add a key to the custom table
2. Send the key to workflow 
3. Have workflow call the ABAP WD program passing the key
4. Using the key look up the table and import the pdfsource in your ABAP
WD program and display it.
5. When the user updates the form with the digital signature, reimport
it and update your custom table. 
6. You could use your ABAP WD program to read data from the form to pass
to the workflow container, as well as reading the PDF in full, before
closing.
(After all workflow probably doesn't need all the details of the digital
signature - mostly it needs to know if it was signed at all.)
This would provide data for subsequent steps in workflow, rather than
having to create an attachment or try and get the workflow to parse the
file in background.  
Similarly if you were sending the form offline via email or uploading a
returned from via email you would need the key as well as the PDF. 
 
The approach would be much the same regardless of what storage area you
use.  
 
The point is to get away from thinking of workflow as the carrier of the
document. Rather workflow handles the communication needed to complete
the process.  It's the ABAP WD program that accesses the PDF document.
So all you need is for the workflow and the ABAP WD to agree on some way
of uniquely identifing a document. 
 
Please look at the Adobe tutorials on SDN.
 
Regards,
Jocelyn 

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of akshay.bhagwat at wipro.com
Sent: Tuesday, 13 January 2009 12:57 PM
To: sap-wug at mit.edu
Subject: [LIKELY JUNK]RE: [LIKELY JUNK]Workflow and PDF attachments


Hi Jocelyn,
 
Thanks for the inputs.
But I am not able to visualize how can I use the retrieved data?
e.g. In my case As this is custom application, we had created a custom
table and stored the data from PDFsource of context in custom table as
Xstring. However, problem is how to use this data for displaying again
as PDF?
Another issue is how to reproduce the digital signatures from this data?
Even though it's stored inside XSTRING  ,,,
So I thought of using the form getting manually saved on Front end when
use digitally signs it.
Then create attachment of it - then use it for further purpose inside
workflow.
 
Now the issue was how to create attachment in background step of
workflow.
 
Please suggest.
 
 
 
Regards

Akshay Bhagwat

 

Akshay Bhagwat, Senior Specialist |  SAP Practice, Wipro Technologies |
O: +91-20-22933700 Ext 3608 | M: +91-9881471909 | Email:
akshay.bhagwat at wipro.com <mailto:akshay.bhagwat at wipro.com>  | Web:
www.wipro.com <blocked::http://www.wipro.com/>  

P Please do not print this email unless it is absolutely necessary.
Spread environmental awareness.

 

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Dart, Jocelyn
Sent: Monday, January 12, 2009 6:37 PM
To: SAP Workflow Users' Group
Subject: RE: [LIKELY JUNK]Workflow and PDF attachments


Hi Akshay, 
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.  
 
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.  
 
You might also want to look at the many Adobe tutorials on SDN.  There
are various approaches to handling incoming PDF forms. 
Regards,
Jocelyn

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of akshay.bhagwat at wipro.com
Sent: Saturday, 10 January 2009 12:55 PM
To: sap-wug at mit.edu
Subject: [LIKELY JUNK]Workflow and PDF attachments


Hi All,
 
I know this topic is discussed a lot, still posting the questions as I
am not able to achieve the requirement.
 
Just to elaborate the scenario, we are using Web dypnro for ABAP to host
Interactive form .
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.
 
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.
 
Now the issue is: 
How this form in Webdynpro is to be saved as PDF file automatically and
then send as an attachment in workflow?
 
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.
2. Same is the issue If I use background step for creating SOFM document
so that it can be used as an attachment.
 
Can any body please suggest what approach can be taken so that from
webdynpro , attachment can be created and passed to workflow seamlessly?
 
Any inputs are appreciated.
Thanks in advance.
 
Regards

Akshay Bhagwat

 

Please do not print this email unless it is absolutely necessary. 

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. 

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. 

www.wipro.com 

Please do not print this email unless it is absolutely necessary. 

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. 

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. 

www.wipro.com 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20090113/d36f5cfd/attachment.htm