- Mark as New
- Follow
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report
"1. While testing the form and process using Workspace, I had created an xfaForm variable that would be the input from the first activity that invokes the process using Workspace. Now when I am trying to acheive the same with email enpoint the input is no longer an xfaForm right?"
Right.
"2. I noticed in previous discussions that there was a reference to creating a document variable and assigning that to the document input. While submitting the form to the email address used by the endpoint, should I configure it to send the attachment as PDF or as XDP? i.e. should the document variable be set to a PDF or a XDP file?"
I doesn't really matter. The document variable can contain pretty much anything. It depends what you want to do. If you're just interested in the data, then just send the XDP. It easier to inspect the data and manipulate it since it' just XML.
If you submit the entire PDF, the email will be bigger, but you won't have to recreate the PDF server side. You will have to extract the data if you want to get to it. You also need the entire PDF if you're planning on using digital signature.
"3. The Input Parameter Mappings have two entries:
a. MyFormDocument - What should this be set to depending on if I have to attach a PDF or a XDP file as an input as it seems to be a required field?. Curently I have it set to Variable - "*'*"
b. document - How is it different from the MyFormDocument input parameter and what should it be set to?"
Is MyFormDocument an input DocumentForm variable so you can use Workspace to initiate? I wouldn't suggest to use a Task Manager (Workspace) and email endpoint on the same process for that very reason. You can't set the Document Form variable properly from an email endpoint.
What you can do is create a separate process that has only one input document variable. Create the email endpoint on that process. Set the input document to variable -> *.*
Then call your Workspace process as a subprocess from that new process. That way you can use a setValue and set the Document Form input variable expected by your Workspace process.
Jasmin