CONFIGURATION
Local Form Configuration File |
 |
 |
 |
 |
| Local Form Configuration File This section is designed as extension to FPP Description / Local Form Configuration File section. Here you will get answers on how to use form variables for best optimization of the Form Processor Pro 4.0 work and how to improve your web forms processing. 1. Messing with Variables. Most important aspect of form.cfg is that _browser_out<digit> variable package is sequential, while other variables, i.e. _send_email<digit> are free. To understand the sequence let’s get to the following example: We have 3-step form: - start page, where user enters data (e.g., start.html), - data verify page, where user visually checks whether entered data is correct (check.html), - output page with thanks and additional information given to user, with no user input on this page (thankyou.html) “browser out” sequence in form.cfg must look like: _browser_out = check.html #start.html – is a start page, we don’t need to move forward to it, so we don’t mention it at all _browser_out1 = thankyou.html # Though thankyou.html has no user input, it is next in page sequence 2. Starting Output. E-mail messages and record logging start on the last page transition sequence. It means, according to our example above, that when user submits check.html, an e-mail is sent to him and his data is logged to external file (if provided by the configuration). Roughly, when Form Processor Pro 4.0 meets last _browser_out directive, it starts final output. When no browser out directives are found for Form Processor Pro 4.0 at all, it outputs Form Processor Pro 4.0 default information on that page has been submitted:  |
|
|
|
