README.txt in Eloqua 6

Description:
------------
This module expects an existing subscription with eloqua.com. If you do not have
a subscription with eloqua.com at this point, please go to eloqua.com and review
purchasing options if you wish to continue using this module.

This module will allow you to create webforms and link them to your existing
eloqua forms.  At present, this module requires you to still set up the form
in both eloqua (using their form builder) and in Drupal (using webform). This
may change at a later date, but will at least provide a more Drupal-esque way
to create forms for use with eloqua.

Requirements:
-------------
Webform module (6.x-3.x) must installed and enabled.

You will also need to have generated and downloaded the tracking scripts from
eloqua for this module to behave as expected.

The quick version of generating the scripts is:
1. Go to Automate > Web Profiling and click on the Web Integration tab
2. Expand Visitor Tracking Scripts and click Generata Vistor Tracking Scripts
3. Generate the scripts and download them.

For additional information and a step by step walkthrough, view eloqua's support
for information on how to generate and download those scripts:
https://support.eloqua.com/View.jsp?procId=8a7e8d4c2003c998012038a33936546d

Installation:
-------------
Assuming you have generated and downloaded the eloqua tracking scripts as
outlined in "Requirements", copy the "elqNow" directory into
sites/all/libraries.  Once you have done this, the elqCfg.js, for instance,
should reside at sites/all/libraries/elqNow/elqCfg.js.  If that is not the case,
this module will not integrate with eloqua as expected.

Move the contents of the eloqua/elqNow folder to reside in the above library directory.
In total, the three files this script requires are
  elqScr.js
  elqImg.js
  elqCfg.js

Use:
----
Form:
When creating a webform, a new checkbox should exist on the node add page
allowing you to make the particular webform node Eloqua enabled. After checking
the box, there is an "Eloqua Form Name" field that should map exactly to the
form name on Eloqua.
Fields:
After you have created the webform and made it eloqua enabled, when creating new
form components (fields), a new field exists for identifying the Eloqua name of
that field ("Eloqua Field Name"). An example of use: your form might have a
First Name field. When you create the textfield for First Name, Drupal assigns
it the name of first_name (webform only allows lowercase alphanumeric +
underscores), but your field in Eloqua might be First-Name. Drupal/Webform will
have first_name as the "Field Key", but you can set the "Eloqua Form Name" to
First-Name so that, when submitted to eloqua, this field maps over exactly as
expected

URL Parameters
--------------
Using URL Parameters instead of relying on Token values for the default value
provide a better experience when dealing with compound values that cannot
be expressed simply.

This functionality can be extended by implementnig the function
   _eloqua_form_url_map_{type}($value, &$element)
where type is the webform component type.

When using the URL Parameter functionality to define the default values, rather
than token replacement in the default-value, the following rules are in effect.

Type:
 time: Express as a 24 hour value in the format HH:mm.   ie: &t=23:59
 date: Express as an ISO date in the format YYYY-mm-dd.  ie: &h=2010-12-18
 radio: Express as a simple value.  ie: &s=AK
 checkboxes: Use array notation.   ie: &c[]=opt1&c[]=opt2