Registration for Spring 2021 webinars is now closed.  Check back next Fall for our Fall 2021 webinars!


Composting is a great way to reduce your waste and add nutrients back to your soil. Learn how to make compost in your backyard. In this webinar, we’ll cover how to set up and maintain a compost pile.

You’ll receive a reminder email with a link to join the webinar the week of the event.

This value will normally be the email address of whomever is submitting the form.  You can set this value to a value entered by the user.

This value may be the same as the 'email subject - LOB'.  Just code - or copy/paste the value as needed'

This value will normally be the email address of an LOB general mailbox.  Something like: ME.Operations@hennepin.us  

Only one email per field.

(cc)

This value will normally be the email address of an LOB general mailbox.  Something like: ME.Operations@hennepin.us  

Only one email per field. 

If this value should be left blank - noreplay@hennepin.us should be used as the default.  

This value may be the same as the 'email subject - submitter'.  Just code - or copy/paste the value as needed'

A dropdown is used - just in case you change these values when in different environments.

Info:

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.