1. Nintex Xsn Builder Nintex Xsn Builder doesn't allow task InfoPath forms to be customized within the realm of what InfoPath is capable of. E.g. Nintex expects the order of the fields in the InfoPath form to match that of the underlying task content type which is completely impractical . It also expects the fields to be within its own cell in a table. On publishing the workflow, the XSN builder overwrites the InfoPath form and enforces these rules thereby deleting the rules built on the fields and changing the order.

This can be updated to ensure that the XsnBuilder creates a new InfoPath form with the default view when it doesn't exist, but doesn't overwrite a customized form containing rules and formatting. It can validate the schema of the view to ensure that mandatory fields in the underlying task content type are added to the form.