The documentation has some ambiguity about where the optional fields come from for POST Service Requests. Are these fields always displayed in the UI as a set of "core" fields or do they come from some kind of user profile that applies to all interactions. How are they related to optional fields defined by service definitions?
Providing a way to define these fields as required much like can be done with fields in service definitions is a separate ticket - #57
The documentation has some ambiguity about where the optional fields come from for POST Service Requests. Are these fields always displayed in the UI as a set of "core" fields or do they come from some kind of user profile that applies to all interactions. How are they related to optional fields defined by service definitions?
Providing a way to define these fields as required much like can be done with fields in service definitions is a separate ticket - #57
http://lists.open311.org/groups/discuss/messages/topic/1Yj3jSrYVYjZYuAgpvpGxx