Thanks Jasmine, I got a reply by Dave Venance suggesting I should change it to short-lived process,
it is working now after changing it to short-lived process and creating the Data Connection, I saw only 1 operation, which is "invoke" and I got to see the populated output1 in the form.
Well I thought of it a little, "What if the process is really long lived, and it is routed to an end user?"
then I was saying to myself "it makes sense, I can't get a response in the form except if the process is short-lived"
Now this small process was just for testing the whole thing, lets talk long-lived process a bit, I can invoke a long-lived process as I told you before from the "invoke_Async" operation, I will get over the fact that I don't know what is the "invoke", "invoke_Result" operations are for.
Lets just say I can invoke a long lived process from the operation "invoke_Async" and I can pass inputs to the service through the "invoke Async Request", This is going to be a bit long, I can deal with simple types in the "invoke_Async Request" like "int, string, float, etc..." but what if I want the user to submit the form as a whole to me in a variable like "document, xml with schema, xfaForm, etc..."?.
I can make a work around this, and I can use the setValue operation in the Workbench to map the simple input variables one by one to the corresponding path in the xfaForm variable like for example
Location: /process_data/exp_review/object/data/xdp/datasets/data/Expense/UserInfo/txtEmployeeName
Expression: /process_data/@txtEmployeeName
and on the other hand in the Designer I can bind each field on the form with its corresponding field from the Data Connection request.
This is the work around, but I want the user to submit a variable of type "xfaForm", like for example I want it to look like this
Location: /process_data/exp_review/object/data/xdp/datasets/data
Expression: /process_data/exp_report/object/data/xdp/datasets/data/Expense
Now when I tried to use this complex types as input variables in the Workbench, then I made a Data Connection to the exposed web service I saw many fields in the "request" that I don't understand, actually I didn't understand any of them.
For example when the input type was "document" the "request" had this fields
-"contentType", "attachementID", "binaryData", "remoteURL" and all of them are of type text fields.
Another example that I thought it might be the solution is submitting the data on the form as XML, so I created an XML variable on the Workbench called "xml" and I marked it as input and I set the XSD reference to my schema, now when I created the data connection on the Designer I found only 2 fields on the request inside a subform named "xml" which was "document" & "element" of type text fields!!
Another example, when the input type was "xfaForm" the "request" had this fields
-"data", "description", "name" and "templateURL" of type text fields and "renderOnce" of type checkBox
-it also has 3 subforms
1st subform: "dataAsDocument" containing "contentType", "attachementID", "binaryData", "remoteURL"
2nd subform: "renderServiceCall" containing 3 tables "inputParamterMappings", "outputParamateMappings" and "outputParamaterMappings"; each of the 3 tables has 1 row containing "key" and "value" of type text fields; the "renderServiceCall" table also has 2 text fields "operationName" and "serviceID"
3rd: "submitServiceCall" having the same tables and fields as "renderServiceCall"
How can I use such a variable of type xfaForm or xml, in the workbench I gave it the template url and the schema, but when I use the exposed web service in the Designer, I find out that the request has this fields I just mentioned.