My perspective is that even we can completely detach an Infopath form from the workflow it is always better to keep workflow supporting data within the Infopath form such as form status or approval status. It is true that we have other ways to do that within the workflow itself. But with my experience, I believe that keeping those values in the form is straightforward and easy to work with.
I've seen a lot of people confuse a Status field on a form and some list views with Workflow. Its part of the consultant skill to know when we're talking about form logic and when we move into a workflow to follow a complex process.
InfoPath is a very powerful tool and I've seen entire applications build within a single form using 10s of views. Nintex have been careful with their forms application to discourage this and separate the Form from a Workflow that enforces a business process.
My perspective is that even we can completely detach an Infopath form from the workflow it is always better to keep workflow supporting data within the Infopath form such as form status or approval status. It is true that we have other ways to do that within the workflow itself. But with my experience, I believe that keeping those values in the form is straightforward and easy to work with.
Really great article Marc! Thank you.
I've seen a lot of people confuse a Status field on a form and some list views with Workflow. Its part of the consultant skill to know when we're talking about form logic and when we move into a workflow to follow a complex process.
InfoPath is a very powerful tool and I've seen entire applications build within a single form using 10s of views. Nintex have been careful with their forms application to discourage this and separate the Form from a Workflow that enforces a business process.