You are here: Home Plone products getpaid.SalesforcePloneFormGenAdapter

getpaid.SalesforcePloneFormGenAdapter (1.6)

1
by Olha Pelishok last modified 2009-11-09
0.0
0.0
0.0
0.0
Released on 2009-10-21 by Rob LaRubbio for Plone 3.0 under GPL - GNU General Public License available for All platforms.
Software development stage: stable
PloneFormGen adapter allowing for creation of arbitrary Salesforce.com records based on data collected from a web form.

This product builds on top of the foundation for through the web form creation provided by PloneFormGen and Salesforce connection provided by the Salesforce Base Connector and Salesforce PloneFormGen Adapter. If you are unfamiliar with PloneFormGen's capabilities and the problem space it intends to serve, we encourage you to start by downloading that and reading the README.txt file in the root of the product. In particular, the "Overview" and "Rationale For This Product" sections are recommended.

In addition if you are unfamiliar with Salesforce please see salesfoce.com. For more information about Salesforce base Connector and Salesforce PloneFormGen Adapter please see http://plone.org/products/salesforcebaseconnector/releases/1.0.1 and http://plone.org/products/salesforcepfgadapter.

Once you've setup a suitable PloneFormGen form folder (and correctly installed and configured the PloneFormGen GetPaid Salesforce Adapter its dependencies), you'll have the option of adding a new action adapter called a "GetPaid Salesforce Adapter".

Once you've added a GetPaid Salesforce Adapter to your form, you're presented with both "default" and "field mapping" (in addition to the standard "overrides") management screens for editing the adapter. The default screen consists of a drop-down menu populated with all the sObject types (i.e. Salesforce Objects) found in the Salesforce.com instance that corresponds to the credentials entered when creating a Salesforce Base Connector in the ZMI. This should include both standard and custom sObjects.

Once you've chosen your sObject type, moving through to the "field mapping" management screen will display two seperate sets of two-column forms. Each for setting which Salesforce field will be populated by a field on either your form, or from data supplied by GetPaid. Each field is represented by a single row, with the field name in the left column, and a drop-down selection menu of all available Salesforce fields on the right. Select the desired Salesforce field for each field and click "Save".

# Add section talking about creating an object per line item

# Probably want to explaing the difference between line item cost and total cost

NB: While it is not required to map every form field to a Salesforce field, you will want to make sure that all the sObject fields defined as required fields in your Salesforce configuration do have a mapping. Otherwise, the sObject will not be succesfully created on submission of the form. All required fields for your chosen sObject should be marked accordingly and appear at the top of the list of options.

Should you go back and switch to a different sObject type after having provided a mapping at any time, you'll want to recreate your desired mapping. This is intended behavior, since the update would fail (or worse, produce very confusing results) if the previously selected sObject type's mapping were maintained.

Document Actions
Powered by Plone