In my office we are having an interesting debate on exactly what to put inside our schemas. In the true definition, the schema represents all fields on a form, right? So in its pure sense, we should have a schema for every form, with every field in the form represented in the schema.
A schema is also necessary for workbench orchestrations so that if you need to refer to a field, you can easily drill down to the field value in your process. So along comes a developer that states that if you have a form that has a very simple back end process (like filing the form to the file system once it's submitted), then you don't really need a schema on the form at all, because the orchestration does not need to pull any field values.
Then there's the java developer that thinks you should only expose fields to a process that are required for the orchestration to run. So if a form contains 10 fields, but only 2 are needed in the orchestration, then only those two should be represented by the schema.
Then there's the data purist that wants a schema for everything...
We haven't formed a definitive approach yet. Just wondering what decisions others have made regarding this...
Thanks,
Elaine