ParallelFun

The InfoPath 2010 web enabled task forms are served by nintex under /_layouts/NintexWorkflow/WrkTaskIP.aspx. The nomal infopath form is served via /_layouts/WrkTaskIP.aspx the /layouts folder is a directory shared by all web applications locaed under the 14 Hive at c:\program files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\LAYOUTS\. This page inherits from Nintex.Workflow.ApplicationPages.WrkTaskIPPage which is not part of SharePoint. The re-interpretation by the Nintex of InfoPath forms has consequently caused formatting rules to become an unsupported feature. Should I create normal SharePoint workflows with standard InfoPath forms the same form and rules will be functional (tested). If you require Nintex Workflow and conditional formatting support you may wish to consider upgrading to the November 2012 release of Nintex forms which "supports" conditional formatting in the future, albiet this support has arrived somewhat late for those of us implement...

A brief post to capture the fact that you may get ambigous exception using the update multiple item activity. Setting fields to current list item fields which have no value. Or setting no value on the field will effectively throw a null reference exception. I wanted to create a single activity to set all the fields to the parent item fields but this failed as the step continues to throw null reference exceptions. If the user inputs no value into the field this can also trigger the exception, even if the field is an optional field. The trick is to only set fields you have recieved data for.