1. The button is only for testing the FDM insert service.  If data is saved successfully, it will return a response.  The code from that is in the Submit button.

2. The FormID is like the table name for the unstructured db.  That should not change once the form is in production.  The version # should stay as is unless components are added to the form in which we need to change the JSON (to string field).

3. Extra/generic components were added to the form below, in case the business area requests more fields and we don't want to change the JSON (to string).  If only using the extra fields, the rule in "to string" shouldn't be changed (column names) but the component names can be changed and updated in the rule.

4. If more fields are needed than the extra ones added below, the version # has to be changed along with the rule in "to string".  When a report is created against the unstructured database, it relies on the FormID, version, and columns to be the same.  Think of the FormID and version, together, make up the table name.

5. "Columns" are in the rule in the JSON (to string).  It's all one string, but the way to see what the columns are is each column/value pair is separated by a colon.  E.g. "city: txtCity.value", "city" is the column and txtCity.value is the form's component name and value.