Here I am attaching my process.

I have 2 swim lanes for 2 users. 1) manager 2) emplyoee

When I am trying to create a task for employee, I am getting an error like this.

If I create the task for manager with the same for it is workign fine.


Anybody help Highly apreciated. I need it real quick.










17:36:53,531 ERROR [ASSIGN] Assignment Fault: {http://schemas.xmlsoap.org/ws/2004/03/business-process/}selectionFailure,lineNo=600,faultExplanation=No
results for expression: {OXPath10Expression $dispersion1CreateTaskRequestMsg.root/xform:taskMetaData/xform:userProcessEndpoint}
17:42:31,890 ERROR [ASSIGN] Assignment Fault: {http://schemas.xmlsoap.org/ws/2004/03/business-process/}selectionFailure,lineNo=600,faultExplanation=No
results for expression: {OXPath10Expression $dispersion1CreateTaskRequestMsg.root/xform:taskMetaData/xform:userProcessEndpoint}
Warning: Running an XSLT 1.0 stylesheet with an XSLT 2.0 processor
Warning: Running an XSLT 1.0 stylesheet with an XSLT 2.0 processor

I found the bug.

When It is generated xpath fucntion in bpel, it is genrated wrong way


$dispersion1CreateTaskRequestMsg.root/xform:taskMetaData/xform:userProcessEndpoint}


it should be like this


$dispersion1CreateTaskRequestMsg.root/Disperison1:taskMetaData/Dispersion1:userProcessEndpoint}

Dear srikanth,

This problem is caused by Data validation. You have to be careful with data's behaviours (in/out/in-out)

when you are creating new task under different user you have to match the data behaviours validation.

I hope this will help you,

if you even could help with this I will reach you again

regards,
naresh

This is happening most of my forms. I did data validation. I looked at BPEL to find the problem. then i relaized it is a bug with this relase.

Is there any workaround for this.

I am having couple of bugs in xforms tooo....

I wnated to show some processes to our client. But I got strucked with these issues.

Dear Srikanth and fellow community users,

We have also encountered this bug and it has been fixed by our engineering team.

The fix will be part of the next community release.

Regards,

Jason

I have the same issue with 5.1

Is there a workaround in the mean time?
Where can I find previous version ?

Thanks