Avatar

Level 2

Jasmin,

Thanks for your response. Yes, MyFormDocument is the variable (xfaform) that I have set as the input for the process when I was using workspace to test my process. I have updated the MyFormDocument variable to no longer have it as an input and now have a document variable that holds the input passed in by the email endpoint. When I try to submit the filled out PDF form to the email endpoint, the process is invoked but the form data that was filled while submitting the form to the email endpoint is not carried to the assigned user task. I am guessing it is because the xfaform variable is still bound by the form template that I had configured it for and therefore starts of with that empty form template rather than with the data that was submitted to the email end point. How do we get the data from the PDF that was submitted to the email endpoint into the xfaform variable that would get set if we use Workspace?

Since trying to pass the data to the xfaform wasnt working when I was doing it within the same process, I tried your suggestion to create a separate process that would have the email endpoint and would take the PDF as an input and assign it to the document variable. And I am also invoking my orginial process from within this new process and setting the MyFormDocument (xfaform) input variable to the document variable that was set earlier from the email endpoint. Now did I follow your suggestion correctly? because I sitll get the "Cannot coerce object" error in the server log when I try to set the document variable as an input to invoking the process that expects an xfaform variable. Let me know if I did anything wrong here?

I was under the assumption that it was required to have an xfaform variable within the process to bind it against the form. Is my assumption correct or can we use store the data within the document variable and retrieve from it? What is the typical approach for storing the form data within a process?

Thanks,
Varma