For good reason in Drupal 6, you are using a highly modified version of the Salesforce API module code as the base for Springboard.

I think it would be a great benefit for everyone, though, if Springboard for Drupal 7 used the Salesforce Suite modules as a base on which your customizations were built.

For one thing, you would gain the benefit of the support for all Drupal entities which is built into the Drupal 7 version of the Salesforce Suite.

I decided to open this issue to give you a chance to list which are the custom features of your Drupal 6 integration which would be crucial to be in the 7.x version of the Salesforce Suite.

I am presuming that the queue processor and the fieldmap business logic which you have are among the most important of these, but I'm sure there are others as well.

Note that in regard to the queue, I had been planning on rewriting to use the Drupal 7 queue API, but it looks like your implementation might be better. If you want to contribute to the Drupal 7 version of the Salesforce Suite module, this issue would be a great place to start: #1207312: Rewrite Salesforce Queue to use a better queue API.

Note also that I created the following issue so that myself and the other co-maintainers could track code from Springboard that would be beneficial to bring into the Salesforce Suite, both for 6.x and 7.x: #1303594: Determine what features can be brought into the Salesforce Suite from Springboard.

Comments

BrockBoland’s picture

BrockBoland CreditAttribution: BrockBoland commented

Thanks for reaching out! We definitely want to work with you guys to use Salesforce Suite in the 7.x version of Springboard. I'm going to ask some colleagues to chime in on this issue, since there are others who are more involved in this part of Springboard than I am.

EvanDonovan’s picture

EvanDonovan CreditAttribution: EvanDonovan commented

Glad to hear it! I had been in touch with some people from your team prior to the code release, but I think that things can move forward better now that the code is out.

pcave’s picture

pcave CreditAttribution: pcave commented

Hi Evan. I finally got a chance to install the D7 version of the project late last week. I'm going to experiment with it a bit and compare it with the changes we made to our forked D6 version and compile a list. Now that Springboard is officially out, our next major initiative is the D7 upgrade. That means we'll be able to commit resources to the D7 port. Thanks again for reaching out.

EvanDonovan’s picture

EvanDonovan CreditAttribution: EvanDonovan commented

Thanks so much! That would be great if we can work together to merge our code in D7. I think that the queue functionality you have will be possible to implement into the D7 branch without too many changes to the core Suite code, since I added a hook_salesforce_api_pre_save() that can "capture" an export before it would get pushed in real-time.

afreeman’s picture

afreeman CreditAttribution: afreeman commented

Hey Evan, we've finally started working on getting Springboard ported to D7 and would love to be able to move away from using a forked copy of Salesforce API. Is there anything else we can provide you to help with getting the required additions into the D7 codebase to make that happen?

kostajh’s picture

kostajh CreditAttribution: kostajh commented

Hey Allen, I'm working on the 7.x-2.x branch of the module at the moment now too. Maybe a good approach would be to use the Salesforce Suite (7.x-2.x) branch as the basis for your 7.x Springboard development and open up issues in the http://drupal.org/project/salesforce issue queue as needed?