Recently I stumbled upon an issue in JDeveloper where 'execData' element under the 'Data Associations' of user task activity would show an 'error'. This means that none of the process runtime variables available within this element could be used within the process.
On closer observation, I noticed that there were warnings when JDeveloper is booted as shown below;
However, I was not using any MDS connections in my BPM process. Issue was that if there is any open project in JDeveloper which uses MDS and if it is not the first project to load while JDeveloper starts, other projects are unable to load the execData information.
Solution is to either close the BPM project that uses MDS connection or ensure that it is the first project to load when JDeveloper loads. Now, there would be no warnings during JDeveloper boot and execData elements are accessible within user tasks.
On closer observation, I noticed that there were warnings when JDeveloper is booted as shown below;
"oramds" protocol support not available because no application was associated with IDE context.
Unable to open an input stream for ORAMDS URL "/soa/shared/workflow/WorkflowTask.xsd".
"oramds" protocol support not available because no application was associated with IDE context.
Unable to open an input stream for ORAMDS URL "/soa/shared/workflow/WorkflowCommon.xsd".
"oramds" protocol support not available because no application was associated with IDE context.
Unable to open an input stream for ORAMDS URL "/soa/shared/workflow/TaskEvidenceService.xsd".
"oramds" protocol support not available because no application was associated with IDE context.
Unable to open an input stream for ORAMDS URL "/soa/shared/workflow/TaskEvidenceService.xsd".
However, I was not using any MDS connections in my BPM process. Issue was that if there is any open project in JDeveloper which uses MDS and if it is not the first project to load while JDeveloper starts, other projects are unable to load the execData information.
Solution is to either close the BPM project that uses MDS connection or ensure that it is the first project to load when JDeveloper loads. Now, there would be no warnings during JDeveloper boot and execData elements are accessible within user tasks.
Thank you!!! It helped me.
ReplyDelete