Certain fields on the physical Uniform Residential Loan Application (Form
1003) consist of a predefined list of "values" that a user must make a selection
from. Two such fields are "Mortgage Applied for" in Section I and "Property will
be" in Section II. Although similar, the distinctive difference between these 2
fields is that in the first one, if the last value ("Other") is selected,
additional user input is expected.
To avoid placing a dependency on string values and to also keep things as
simple as possible, we decided to assign numeric indicators to the values in
these predefined lists. For the "Mortgage Applied for" field, the (name, value)
pairs are:
- (Conventional, 1)
- (FHA, 2)
- (VA, 3)
- (FmHA, 4)
- (Other, 5)
For the "Property will be" field, the (name, value)
pairs are:
- (Primary Residence, 1)
- (Secondary Residence, 2)
- (Investment, 3)
For fields where additional user input may be provided (as discussed above)
both the name and the value of the (name, value) pair will be stored in the
system when calling the ProcessApplication SOAP method. For fields not
requiring additional user input, the value will be the only one stored when
calling the ProcessApplication SOAP method (the name will simply be
discarded if provided in the XML). Therefore, possible value combinations for
the "Mortgage Applied for" field are "1" and "Conventional" or "5" and "Whatever
the 'Other' is"; possible values for the "Property will be" field are "1", "2"
or "3".
The LoadApplication SOAP method will always return both the name and
the value of the (name, value) pair.
The values of all (name, value) pairs are defined as <xsd:enumeration> in
the XSD validating schema. We also provide "Helper SOAP Methods" to return all
(name, value) pairs as XML, enabling client applications to create dropdowns or
radio buttons with the correct (name, value) pair combination.
