Design Notes
These are notes you can input that help you and other production staff understand your confirmation elements logic and purpose. This text is never used in the live form in any way, it is only for internal development.

The logic takes the form of:

Variable 1 | Condition | Variable 2

For example, let's assume we have a radio item in our form with the Name/Value of opt_1. The radio item has two possible vales, 'Yes' and 'No'. If the value of opt_1 is 'Yes' we want to send an email, if no, we do not.

We would write the Confirmation Condition PHP Code as such:

#{opt_1} == 'Yes'

In other words, we use the token for our field variable like we would in other property boxes, that is, a pound sign (#) followed by the Name/Value of the field in braces. Recall that at run time this token evaluates to the value set by our forms users, which in this case will be the value of the radio button with the Name/Value of opt_1.

We then set the comparison, in this case out comparison is equal too, denoted with the double == sign. Finally, because we know our radio item is a string value that can be 'Yes' or 'No', we wrap the value we want to check for in single tick marks.

On the raw code side, FormBoss wraps the token call in an isset() block, which is further wrapped in the proper PHP if() syntax:

if(isset($_SESSION['qs']["{$_SESSION['entry_key']}"]['opt_1']) && $_SESSION['qs']["{$_SESSION['entry_key']}"]['opt_1'] == 'Yes') { // condition code start

When run, if the users set value for the radio box was 'Yes', we would process this confirmation element.

Using Array Based Form Elements (Checkboxes)
PHP Treats checkbox items a little differently than other elements. The good news is the only element that needs this special attention is a checkbox field. The difference then, is that in order to use checkbox items we need to place an index indicator just after the field Name/Value token.

For example, lets say we have a checkbox field that had the Name/Value: email_condition and has two elements: Recipient A and Recipient A

To process this field in our condition statement we need to append the proper index of the field used for checking the condition using PHP array index format. It may sound confusing, but it's quite simple when you see it:

#{email_condition[0]} == 'Recipient A'

In short, the non-array way would be to simply use:

#{email_condition} == 'Recipient A'

But because we need to check an array index (again, because PHP treats checkbox items as arrays), we simply add the [0] part before the closing brace (}).

How do we know which array index to use (the number part)? In our example the checkbox field has two values; array indexs start with 0, so the first field, Recipient A, is [0], where Recipient B would be [1].

This numbering simply climbs up by 1 for every checkbox item you add.

This field lets us set the various parameters our payment gateway accounts expect.

Transaction Vendor
Set this to the vendor of your choice. Please note that some vendors support different features. For example, only PayPal supports transacitons other than simple buy now buttons.

Process This Field
The Name/Value property of the form item you want this payment gateway to process. You can only have one item per payment gateway unless you select Shopping Cart Items from this menu, as well selecting Shopping Cart Item from the E-Comm field items Transaction Type menu. In short, by default we usually only process one e-commerce field per E-Commerce confirmation page item. However, as of Build 676 we can now process more than 1 field if we are: a) using PayPal and b) making sure to select Shopping Cart Item from both menus.

Important Note On Shopping Cart Limitations
At this time we cannot mix and match shopping cart and non-shopping cart items. If you have 1 shopping cart item, non-shopping cart items will not process.

Also, at this time we cannot process more than 1 item per e-commerce field item.

As a point of reference, FormBoss uses the PayPal _cart and upload variables to handle multiple items. This is a great way to upload multiple items at once, but has a serious drawback of, when you reach the PayPal checkout page, not showing the user individual items like a traditional shopping cart. If you need a full-on shopping cart solution, it is recommended you research dedicated shopping cart solutions.

Return URL
Not used by all vendors, the url you want your visitors to be directed to after a transaction.

PayPal Users: In order for this option to work you must select the second or third option from the Return Method select item.

Cancel URL
The cancel url a visitor will visit is the gateway provider supports one.

Notify URL
The URL to notify after a transaction.

PayPal Options

PayPal Account Email
Your PayPal account email. Required.

Return Method
New to Build 672, this option requires a value for the Return URL to work. When set to the second or third option, your users will be redirected back to the page specified in the Return URL field. If left on the first option, users will land on the payment confirmation page and not be redirected.

Working Environment
Sandbox or production.

Google Checkout Options

Google Merchant ID
Your Google Checkout Merchant ID

Detailed Product Description
This is the long description for your item, displays next to the product price on the checkout screen.

Working Environment
Sandbox or production.

2Checkout Options

2CheckOut Merchant ID
Your 2Checkout Merchant ID. Required.

Working Environment
Sandbox or production.

Authorize.Net Options [New to Build 675]
As of Build 675, FormBoss supports the Server Integration Method (SIM) for single products.

Authorize.Net API Login ID
This is the API Login ID you received when you created your merchant account.

Transaction ID
Similar to the Login ID, this identifier was provided to you during your account creation, and can be accessed via your Authorize.Net user administration web site

Working Environment
Test or production. If test, your orders are not processed, but they do go to a sandbox environment.