Getting an error when tried to access task form from worklist app

Question

Hi All,
I am using 10.1.3.4 BPEL PM. I have created a bpel process with a human task.
From the worklist application, when the approver clicks on: Task Id (ideally it should open task form).
In my case, I am getting an error:
Error while inoking URL to display the content. Error while invoking URL. http://bluejays.appsassociates.com:7780/default/EditPayloadPOC1/v2009_05_21__82618/EditPayloadPOC1/EditPayloadPOC1.jsp Check the underlying exception and correct the error. Contact oracle support if error is not fixable..
If you need more information, please check with your administrator with the following exception-identifier: "2009/05/21_12:16:43:777_oc4jadmin"
It works fine in SOA suite 10.1.3.1. and does not work in BPEL PM 10.1.3.4
The only difference is I deployed in 10.1.3.1 using Ant script of bpel project and in 10.1.3.4 I deployed using the BPEL Console itself by browsing the project jar(Since I am getting error when tried to deploy it using Ant).
Is it a known bug or am I making anything wrong. Tried with both Autogeneration and Custom form
I followed: http://download.oracle.com/docs/cd/E11036_01/integrate.1013/b28981/workflow.htm#BABCBAEI
Thanks
Sakrishna Panuganti

Answer 1

Hi does your bpel process has more than one human tasks, e.g., HumanTask1, HumanTask2, HumanTask3...then pl. check and manually fix this below ...e.g.,
check for all of the human tasks workflow contexts tasks forms for dynamic pointers for
domain_id, process_id, process_version.
edit public_html/HumanTask1/form/ear/META-INF/application.xml
<web-uri>workflowform.war</web-uri>
<conteit-root>/${domain_id}/${process_id}/${process_revision}/HumanTask1</context-root>
edit public_html/HumanTask2/form/ear/META-INF/application.xml
<web-uri>workflowform.war</web-uri>
<conteit-root>/${domain_id}/${process_id}/${process_revision}/HumanTask2</context-root>
edit vi public_html/HumanTask3/form/ear/META-INF/application.xml
<web-uri>workflowform.war</web-uri>
<conteit-root>/${domain_id}/${process_id}/${process_revision}/HumanTask3</context-root>
and deploy the process again via jdeveloper or preferably via ant script and try, it worked just fine for us.