recruiter_integration
Differences
This shows you the differences between two versions of the page.
|
recruiter_integration [2009/06/08 18:08] jay |
recruiter_integration [2010/10/22 20:05] (current) jason updated honeypot from 'yourEmail' to comments |
||
|---|---|---|---|
| Line 5: | Line 5: | ||
| ==== Technical Overview ==== | ==== Technical Overview ==== | ||
| - | The approach is this: you supply a form on your website and POST the form to our server. The information entered on the form will then be stored and placed in the queue of prospective partners. There are certain required fields (see "required fields" below) that we require in order to get the process started. There are optional fields that are available to you if you want to capture extra information about the prospective partner (see "optional fields" below). View [[RC-example| sample code here]] for a form that utilizes all fields available. There are also required hidden fields that need to be added into the form in order for our server to be able to process the information. | + | The approach is this: you supply a "Join our Partner Program" form on your website, and POST the form to our server. The information entered on the form will then be stored and placed in the queue of prospective partners. There are certain required fields (see "required fields" below) that we require in order to get the process started. There are optional fields that are available to you if you want to capture extra information about the prospective partner (see "optional fields" below). View [[RC-example| sample code here]] for a form that utilizes all fields available. There are also required hidden fields that need to be added into the form in order for our server to be able to process the information. |
| ==== Integration Steps ==== | ==== Integration Steps ==== | ||
| Line 121: | Line 121: | ||
| * directPostKey | * directPostKey | ||
| - | * The value of this field must match the directPostKey assigned to you on the server. Please ask your account manager to get you a "Recruiter direct Post Key". | + | * The value of this field must match the directRecruitPost key assigned to you on the server. Please ask your account manager to get you a "Recruiter direct Post Key". |
| <code html><input type="hidden" name="directPostKey" value="someRandomKey"></code> | <code html><input type="hidden" name="directPostKey" value="someRandomKey"></code> | ||
| === OPTIONAL hidden field === | === OPTIONAL hidden field === | ||
| - | |||
| - | The following hidden field is used for testing your form: | ||
| * saveRecord | * saveRecord | ||
| - | * when this hidden field is set to 0, submitted form contents are echoed back to the screen and are NOT submitted to the channelsuite recruit database. if this field doesn't exist or is set to any value other than 0, the form is processed normally. | + | * this hidden field is used for testing your form. when this hidden field is set to 0, submitted form contents are echoed back to the screen and are NOT submitted to the channelsuite recruit database. if this field doesn't exist or is set to any value other than 0, the form is processed normally. |
| <code html><input id="saveRecord" name="saveRecord" value="0" type="hidden"></code> | <code html><input id="saveRecord" name="saveRecord" value="0" type="hidden"></code> | ||
| + | * source | ||
| + | * this field is used when you have multiple public forms submitting new recruit records. once a form is submitted, the forwarding URL is retrieved from the recruitDirectPostThankYouURL setting in your channelSUITE configuration. the source variable is then appended to this URL as a parameter so that your public web site that processes this URL can distinguish from which page this recruit has been submitted. an example of how this URL would look with the source attached is as follows: \\ | ||
| + | if your config setting is: | ||
| + | recruitDirectPostThankYouURL = 'http://myPublicWebsite.com/recruit_return/' | ||
| + | and your form's source variable is set in a hidden field like this: | ||
| + | <input name="source" value="publicSite1" type="hidden"> | ||
| + | then after submitting the form, the user will be redirected to this URL on your site: | ||
| + | http://myPublicWebsite.com/recruit_return/?source=publicSite1 | ||
| === CUSTOM fields === | === CUSTOM fields === | ||
| Line 141: | Line 147: | ||
| new_field: A new field \\ \\ | new_field: A new field \\ \\ | ||
| The name of the field will be entered first, followed by a colon (:) and then the value the user entered. Any of these extra fields will be added to the end of any existing Comments already entered. A new line will separate multiple user defined custom fields. | The name of the field will be entered first, followed by a colon (:) and then the value the user entered. Any of these extra fields will be added to the end of any existing Comments already entered. A new line will separate multiple user defined custom fields. | ||
| + | |||
| + | === Anti-spam: the 'comments' hidden field === | ||
| + | |||
| + | Forms on public websites are often targets for "spambots" -- automated "spiders" that wander around the web looking for forms. The spambot puts its irrelevant message in whatever fields it can find, and submits the form in the hopes that the posted content will show up somewhere where it will be seen. These submissions would show up as bogus entries in your recruit database. Quite annoying. | ||
| + | |||
| + | Spambots aren't very sophisticated, and they can be effectively defeated by using a "captcha", the most common example being to ask your users to type in the text from a distorted text image. This works, but it's irritating to your users. We're using a simpler method called a "honeypot". We add a field to your form that users can't see, but that the spambots can't easily identify as a hidden field. The spambots will typically insert content into this field. If the field isn't empty, it's usually a spambot submission, and we reject it with an appropriate error message. It contains a label that instructs users of alternative browsers (handicapped-accessible screen readers, for example) to leave the field empty. This method is very effective, and causes no problems for legitimate users. | ||
| + | |||
| + | To implement the honeypot, simply add the following hidden span containing the empty field 'comments' in your form: | ||
| + | <code html> | ||
| + | <span style="display:none;visibility:hidden;"> | ||
| + | <label for="comments"> | ||
| + | Ignore this text box. It is used to detect spaambots. | ||
| + | If you enter anything into this text box, your submission | ||
| + | will be rejected. | ||
| + | </label> | ||
| + | <input type="text" name="comments" size="1" value="" /> | ||
| + | </span> | ||
| + | </code> | ||
| + | |||
| + | Note: prior to October 2010, the form element name for the honeypot field was 'yourEmail'. This was deemed problematic because some automatic form population tools (like the one built into the Google Chrome browser) were over ambitious and were putting an email in the honeypot field as well, generating false positives. | ||
| === Setting Up the Country Code Select Box=== | === Setting Up the Country Code Select Box=== | ||
recruiter_integration.1244484505.txt.gz ยท Last modified: 2009/06/08 18:08 by jay