Until this is solved, our rollout and user adoption is going to be very limited.
Our roll-out is limited due to the significant confusion around the 'Subject' field. We need each form to have it's own flexibility and not rely on system-wide limitations around this field. Outlined a couple of ideas below.
#1 - Preferably, the Subject field would be completely optional.
#2 - Optionally, hide the field and then chose which custom form field will be used to autopopulate the contents of the subject field. That way, you can keep the subject field if needed, but in the form designer tool, you chose to hide the field from view and then from a dropdown beside the subject field in teh designer tool, you chose which text field in the custom form will be used to autopopulate the contents of the subject field.
