Thanks Larry - I understand the concept of the forms in general (Main versus Mobile; not needing to use a specific form in the workflow designer etc).
My particular problem is that the form that CRM presents to me as a System Administrator in the Workflow Designer seems to be chosen arbitrarily (but consistently). This is not normally a problem (since unused fields appear in an extra section at the end
of the form, in the workflow designer), except that the form that CRM presents to me has some disabled fields on it (by design, they are readonly for end users). This is a problem for me when editing workflows, since the workflow designer won't allow me to
set values in these fields. The only workaround I have at present is to edit the form to make the fields all editable, publish the form, edit my workflow, re-edit my form to make the fields readonly and then republish the form. If I had control over which
form the workflow designer presented to me, then I wouldn't have a problem.
I was interested in Jason's response in particular since he referred to a term that was unfamiliar to me and suggested I may have missed something ("..primary form..."). :)
The puzzling thing, as above, is that I cannot think of any logical criteria that justifies CRM's choice of form.
