Salesforce PFG Adapter 1.0rc1 (Release candidate) (Dec 08, 2007)

This release is no longer supported! If you are using this release, please upgrade to a newer version if possible.

This is not a final release. Experimental releases should only be used for testing and development. Do not use these on production sites, and make sure you have proper backups before installing.

1.0rc1 provides marking via the user interface those fields that are required for the creation of any given Salesforce object, internationalization, better test coverage, and Plone 3.0 support.

For additional information about this project, please visit the overview page .

Available downloads

Product Package

For all platforms (0 kB)

Release Notes

Please note, if you previously installed beatbox, the python library for the Salesforce.com API, you'll need to upgrade that.  You can do so by typing "easy_install beatbox -U".

Change log

- Providing test and migration for legacy adapters that didn't have the 
  capability to mark required fields in the UI (andrewb, jessesnyder)

- Renaming the Salesforce PFG Adapter's archetype_name to Salesforce 
  Adapter, in attempt to increase non-technical accessibility.
  Provided migration for the same (andrewb, jessesnyder)

 - Add zope security checks to methods in the SalesforcePFGAdapter class (jessesnyder)

 - Tweaked i18n infrastructure and added German translation. (davisagli)

 - Don't show extraneous schemata in Plone3 (jessesnyder)
 
 - Ran Zope's test coverage feature against our code base and extended test coverage
   to key parts of the public aspects of our code base (andrewb)

 - Implement IMultiPageSchema so that schemata can be processed separately and in order, since
   the field mapping schemata depends on the default schemata being submitted first. (jessesnyder)
   
 - Re-ordered the adapter's schemata to put 'field mapping' before
   'overrides'. (davisagli)

 - Worked around FGDateField issue to format submitted dates properly for Salesforce.com input.  
   Used DateTime.HTML4() method on field value (ghnatiuk, davisagli)

 - Adding labeling to the field mapping ui to show those fields for the 
   chosen SFObject, which are non-nillable (i.e required) and don't have a 
   computed value (i.e. as in a unique id, which is required but you have no 
   control over) (jessesnyder, andrewb)
   
 - Sorting of fields that are required first, then those that are optional
   second in the field mapping ui (jessesnyder, andrewb)