-
1. Re: Submission Receipts
RedBaron2012 Feb 3, 2012 11:53 AM (in response to Randy Swineford)Thank you for this enhancement.
I wonder how the field + value listing in the e-mail can be formatted more explicitly.
I have a multi-page form, and several pages have the same list of fields (labels), since the branching among pages is limited. For example (bear with me here):
Page 1: "Can you send or receive commands from your device?"
Go to page 2 if "Sending".
Go to page 3 if "Receiving".
Page 2: Process for sending each command:
Command_1 [____________]
Command_2 [____________]
etc.
Go to page 4.
...
Page 3: Process for receiving each command:
Command_1 [____________]
Command_2 [____________]
etc.
...
Page 4:
Submit the form.
When the e-mail arrives, it lists the fields and their values, but does not distinguish (in the syntax) between "Command_1" on the sending page, and "Command_1" on the receiving page.
It would be great if fields had names that were separate from their labels.
Then, when editing a form in FormsCentral, the tool could prevent multiple fields from having the same name, just because their labels happen to match.
-
2. Re: Submission Receipts
Randy Swineford Feb 4, 2012 10:06 AM (in response to RedBaron2012)Would providing a way to have a static text object that appears in the form also appear in the reciept. For example, have an option to let the text "Process for sendig each command:" show up in the email before the commands. I think that would also address your issues.
Thoughts?
Randy
-
3. Re: Submission Receipts
RedBaron2012 Feb 7, 2012 8:38 AM (in response to Randy Swineford)This could help, if the static text were defined according to the route (page sequence) the user took through the form.
Putting a static text box (hidden) for each possible option through the form, with different text for each option, would allow the email to look unique for each option.
Paint Order Form
Select One Option: [Red] [Green] [Blue]
<<go to page 2 if Color==Red>>
<<go to page 3 if color==Green or color==Blue>>
Page 2
{Thank you for submitting the order form for Red paint.} ----> a hidden field set when the user jumps to the Red Paint page.
[ ] Click Yes if you accept that Red paint is non-washable and there is no guarantee it can be washed out if you spill it on your clothes.
Page 3
{Thank you for submitting the order form for a non-Red paint.} ----> a hidden field set when the user jumps to the non-Red Paint page.
Non-red paints are washable, using ordinary soap and water.
Is there some fundamental limitation in using form field values in the text of later text blocks in the form, or in the e-mail formatting?
I have seen in some other tools (Footprints by Numara, for example), that %%FIELD_NAME%% is used when formatting a response.
This could be very flexible when formatting the Confirmation Message, the Submission Receipt, the Notification E-mail, or in the form itself.
Submission Receipt
Thank you, %%CUSTOMER_NAME%%, for ordering %%PAINT_COLOR%% paint from our web site.
Note that sales tax has been applied for your order to be shipped to %%STATE_NAME%%.



