Can a User select a recipient from a list to direct Admin notifications to?
Yes, by adding a field named "toemail" to your forms, the User can either pull in, or override the Admin email Setting defined in the Form's Settings.
To pull in the email addresses defined in the Admin email Setting use :
<input type="Hidden" name="toemail" value="2,4">
This will direct email notifications to the 2nd and 4th email addresses defined in the Admin Email Setting in the back end. Multiple email addresses can be separated by commas. Additionally, corresponding names can be assigned for each email address by using a field named "toname".
<input type="Text" name="toname" value="2,4">
If you have the following email addresses defined in the Admin Email Setting :
a@a.a, b@a.a, c@a.a, d@a.a
Then the above example would send email notifications to b@a.a and d@a.a
Both of these fields can also be defined as drop down select menus, or radio buttons allowing Users to select from multiple recipients. For example :
<select name="toemail">
<option value="2">Mark
<option value="2,4">Lisa and James
</select>
To override the email addresses defined in the Admin email Setting use :
<input type="Hidden" name="toemail" value="mark@yourserver.com,lisa@yourserver.com">
Multiple email addresses can be separated by commas. Additionally, correlative names can be assigned for each email address by using a field named "toname".
<input type="Text" name="toname" value="Mark Thompson, Lisa Williams">
Both of these fields can also be defined as drop down select menus, or radio buttons allowing Users to select from multiple recipients. For example :
<select name="toemail">
<option value="mark@yourserver.com">Mark
<option value="lisa@yourserver.com">Lisa
</select>
Are there any Fields that must remain in my Forms for FMAP to keep functioning?
Yes! All Forms must have their action attribute point to the FormMakerAndProcessor Scripts and they also require certain hidden tags be present in your Forms.
All required code can be easily generated by :
- Clicking on either Single Page Forms or Multi Page Forms in the Admin Control Panel.
- For Single Page Forms click the name of the Form in the Name - Code column. For Multi Page Forms click the Get Code in the Get HTML Code column.
Now you have your Form's required code, brief descriptions of each follow.
<form action="http://www.....fmap.cgi?process" enctype="multipart/form-data" method="post">
Copy and Paste the entire <form> tag generated. It has the all-important enctype attribute's value correctly set for File Uploads. This is the start of your Custom Form.
<input type="Hidden" name="id" value="1111222233">
The "id" field is vital. It should not be changed or altered in any way, the case must remain the same, the field must be in every Form. It's value is set to the Form's ID, used to fetch the Form's Settings so it can be processed according to your set configuration. No id, no entry.
<input type="Hidden" name="required" value="fname,lname,email,Age">
The "required" field is optional in your Forms. If you'd like your Customers to be forced to enter a value in, or make a selection of, any of the fields in your Form, add those field names to the "required" tag's value attribute. Do not add any spaces and use a comma to separate the field names. The sample tag above would force Customers to enter a value in the fname, lname, email, and Age Form fields before FMAP would accept the Form for processing.
<input type="Text" name="fname" value="">
The "fname" and "lname" fields can be used to capture the Customer's full name and print easily understood built Error Messages and Preview pages (fname is auto-replaced with First Name). These fields are recommended, but not required. If used, they must also be lower case.
<input type="Text" name="email" value="">
The "email" field is required if you want Customer Autoresponders delivered. It must have a valid email address entered by the Customer. This too should not be changed or altered in any way, the case must remain the same. If there's no field named "email" in your Form, the Customer Autoresponder will not sent.
<input type="File" name="FILE1">
<input type="File" name="FILE55">
The "FILE1" field is optional, however if incorporated in your Forms, you must have the "FILE" portion of the field name in uppercase. If you're using multiple File Upload fields in the same Form, each field must have a unique number after the "FILE" portion as shown in the two sample tags above. Only then will FMAP recognize the field as a File Upload field.
<textarea name="comments" cols="40" rows="6"></textarea>
The "comments" field is optional and is the only built in Textarea field. If you'd like to incorporate additional textarea tags in your Forms, you must append an uppercase "_TA" to the field's name. FMAP then will then process the field as a textarea and preserve line breaks. If for example, you wanted a textarea named "Feedback", you'd name the field ... name="Feedback_TA" cols="40" ...
<input type="Hidden" name="groupid" value="">
The "groupid" field applies to Multi Paged Forms only. It must be coded in to each of the Forms that make up a Multi Page Sequence. If any one of the Forms in a Sequence is missing a "groupid" tag, that Form's data will not be passed through to the last Form, it will not be stored on the server, and will not be sent in any of the email notifications. The data will be non-existent. Nowhere to be found.
<input type="Hidden" name="redirect" value="">
The "redirect" field must be coded in to Multi Page Forms, and is optional in Single Page Forms.
Single Page Forms can have the redirect value set in a Hidden Form tag, or in the Form's Settings in the Admin Section. If utilized, it directs a Customer to any Page of your choice after a successful Submission. The value must begin with "http" otherwise it will be ignored.
Multi Page Forms can only have the redirect values set in the Hidden Form tags. The tag is required in each and every one of the Forms in any Multi Page Sequence, with the exception to the rule applied to the very last Form, where it's optional. The value of each redirect tag must point to the URL of the next sequential Form in your succession of Forms. This is how you control the Customer experienced progression of your Forms. Here's Step by Step guide to creating Multi Page Forms
<input type="Submit" value="Submit">
The "Submit" button must be coded in to your Forms. It should be the last tag in your Form, followed only by the closing </form> tag. This is the end of your Form, you can now any desired Custom Form Fields to it, as long as they are placed between the opening <form action.... > and closing </form> tags.
Notes :
- The same Forms can be used over and over again in to create more Multi Paged Forms.
- Each of the Forms can also be used as a Dedicated Single Page Form.
- To change the text and appearance of the "Previous" and "Next" buttons in Multi Page Forms, click the Multi Page Forms link, then click the Settings link for the desired Form.
- On the same page, you can set your preferred Form Field Sorting Order, using all fields found in all Forms that make up the Multi Page Form. This governs the order used in the Export Wizard, Previews of Forms after Submitted, and the Submission Viewing area in the Admin Section.