SelectionFailure bug in BPM 11g

Found an issue with BPM where you try and assign values from one data object to another using only some attributes and not all attributes of the complex type. This resulted in the BPM process going in suspended state but it would still display the status as Running on the Process instances tab. Only if you click on the process details and see the activities you will see that the activity has been suspended.

I resolved the problem by changing the data associations from using simple assignment to using XSLT instead. However I had to be careful to make sure old values were not lost – since XSLT replaces the entire XML in the target xsd.