Hi Akila, The b4pOutput variable contains only one boolean parameter in the message body and b42pInput variable contains several parameters such as cus, amount, region (string), region (int) in the message body. So you cannot directly transfer the b4pOutput variable into b42pInput variable. You can replace the message body in each other but this will give you an exception when invoking the 2nd humantask due to failure of initializing the humantask input variable.
In-order to solve the issue, assign the values to the b42pInput variable one by one. Since the b4pOutput only returns one parameter, you can set some hard coded default parameters to b42pInput variable. This way you can achieve the goal but, better solution is to have a ifElse check after the first humantask invoke and then if the first one returns "true" then do the 2nd humantask invoke, else skip the 2nd humantask invocation. Thank you & Best regards, *Amal Gunatilake* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware On Thu, Oct 9, 2014 at 5:46 PM, Akila Nimantha [IT/EKO/LOITS] < [email protected]> wrote: > > > Hi all, > > We have invoked two human tasks to a BPEL process and made some changes to > the wsdl file in order to insert two human tasks one after another. But > the second task is not initializing at the assign option and got the > following error. > > > > The from-spec of "<wsdl:message "CapexApprovalResponse">" is not > compatible with to-spec of "<xsd:complexType>" > > > > I have attached herewith my BPEL process and kindly assist us on this > regard. > > > > Regards, > > Akila > > This message (including any attachments) is intended only for the use of > the individual or entity to which it is addressed and may contain > information that is non-public, proprietary, privileged, confidential, and > exempt from disclosure under applicable law or may constitute as attorney > work product. If you are not the intended recipient, you are hereby > notified that any use, dissemination, distribution, or copying of this > communication is strictly prohibited. If you have received this > communication in error, notify us immediately by telephone and (i) destroy > this message if a facsimile or (ii) delete this message immediately if this > is an electronic communication. Thank you. > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
