What can be preventing OnTaskChanged from triggering with custom InfoPath task forms in the workflow?

Question

Why could this be happening: VS Workflow with custom InfoPath Task Forms does not trigger OnTaskChanged when form is submitted with data (so clearly changed). Funny thing is that the same workflow works on my local machine SharePoint, but not on the production server.

What could I check that could be preventing OnTaskChanged event from triggering?

For information, my InfoPath forms environment is done in similar way to how it is described here: http://www.codeproject.com/Articles/195348/SharePoint-2010-State-Machine-Workflows-with-Custo.

With only exception that I also had to set this:

Set the Feature Receiver (under workflow properties in VS Solution Explorer) Assembly and Class Name properties of the module Project Item to "Microsoft.Office.InfoPath.Server, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" and "Microsoft.Office.InfoPath.Server.Administration.XsnFeatureReceiver", respectively.

If someone has any suggestions about why OnTaskChanged may not be triggering when adding InfoPath form functionality, please post a reply about it here! Thank you!

Answer 1

Finally found, through ULS logs, what it was.

In the workflow task list I had few custom fields (from the time before we started using InfoPath forms). Some fields were marked as required and were not present in InfoPath form so it given a warning in ULS logs "Form databind failed" and did not go on to trigger OnTaskChanged event receiver.

Good thing there are ULS logs, as otherwise it did not give any kind of error message or notification, just closed the form successfully without passing data anywhere.

Answer 2

i got the solution but i don't know is the correct way or not. the same issue is exists in my QA server also at one of approval level.

I spent more time but no luck. finally i change the form library, create a new one . wow.. now its work in QA. i am surprise why this happen.

but is not the correct way in client location to solve the issue.

Please tell me how to solve this issue.

thanks in advance,

Nagendrarao.