This is not a discussion thread like #1086910: [meta] 7.x Long-Term Roadmap so much as a list of the issues from the 7.x & 6.x queues that I am going to be working on the near future.

Suggestions of issues are welcome, though - just reference the issue number & state why it is important to you.

Comments

EvanDonovan’s picture

Here's a fairly comprehensive list, for now. When enough of the high-priority ones are done, I'll release the first alpha.

High priority

Bug: #1213238: Salesforce Entity field import handlers don't work on FieldAPI fields
Bug: #1207720: Salesforce Entity & Entity API-based modules: various incompatibilities (hook_menu, etc.)
Task: #1207312: Rewrite Salesforce Queue to use a better queue API
Bug: #1199026: JS in fieldmapping UI not working despite attach behaviors switch
Task: #1199030: Test that sf_import works correctly for mass imports/Salesforce re-syncing in D7
Task: #1214102: Finish porting sf_prematch to 7.x-2.x
Task: #966860: Allow fieldmaps to be enabled/disabled
Task: #1127166: Use drupal_queue for Salesforce outbound messages (DONE in 7.x; only shows as not done for 6.x)
Task: #1149114: Handling/queuing of export errors (broken link to Salesforce, error responses/exceptions from Salesforce, etc.)
Feature: #785268: Two way sync rules on the field level

Medium priority

Bug: #1213044: salesforce_api_cron should check if a connection to Salesforce can be made before a rebuild; throws notice otherwise
Bug: #1214076: "Notice: Undefined offset 4 in _menu_translate" because of the way that the fieldmap paths are defined
Bug: #1214094: "Notice: Undefined index [FieldName]" when creating a new fieldmapping - fails to set proper default option for a source field
Task: #1214100: Change the prematching code for checking if an object exists in Drupal to use EntityFieldQuery
Task: #1058920: Create generic upsert function (for use in all cases of Drupal->SF entity export, etc.)
Feature: #1192080: Handing multiple matches (when there are multiple sf_find_match implementations)
Feature: #1199036: Allow prematches to be exported to code
Feature: #1202622: Token support

Possible Architecture Changes - Mid-Priority

Task: #1214112: Move the fieldmapping UI to a separate module than the Salesforce API module
Task: #1214108: Move the "Evaluate PHP" option to a separate module

Improvements

Feature: #1214122: Add a "Unlink and delete from Salesforce" button to the Salesforce tab for an entity
Feature: #1214124: Make it possible to supply a name for cloned fieldmaps
Task: #1214114: Change the Campaign fieldmap to a Case fieldmap

jcarlson34’s picture

+1

Thanks for the focused write-up and roadmap. Great work on putting this together Evan.

I'm looking forward to helping test and fix these issues.

EvanDonovan’s picture

@jcarlson34: Thanks. Note that my colleagues and I may not actually need all of these for our own client's use case, and thus they might not get attention in this particular order. But I think this is fairly accurate for the overall needs of a port, as I see them.

EvanDonovan’s picture

EvanDonovan’s picture

Brian: Just wanted to make sure you saw #1147180: Store time of last import, last export and initial creation for items in salesforce_object_map table. We should probably do this, for the sake of our imports.

EvanDonovan’s picture

Another (mid-priority): #1218318: Fire a trigger upon salesforce_api_log if above a specified logging level. Soon I should probably start folding these into the comment above, and zero out these followups.

mhurston’s picture

Just wanted to say that I'm looking forward to what comes of this module as I think it'd be an awesome addition to Drupal once it's available for production use.

juampynr’s picture

EvanDonovan’s picture

I think at this point I want to lower the bar for release of the first alpha to just fixing the obvious bugs (warnings and the JS issue I noted above), and finishing the port of sf_queue and sf_prematch. sf_notifications is just now done (though it could be further refined), and I think sf_import should potentially be removed from the Suite, at least for the time being.

If people want to help me, the best thing they could do would be to provide patches for the outstanding bugs I've listed above, and for any other bugs that they can find via testing.

At this point, the core salesforce_api, sf_entity, and sf_notifications should be good to test. I think I've discovered most of the issues with them via the list above, and some others for which fixes were just recently committed.

I may have sf_prematch ready for testing within the next few weeks (minus the prematching on the Drupal side, which would be harder to port).

Hope this clarifies things.

kostajh’s picture

I may be using this module for a Drupal 7 build within the next couple weeks, and I wanted to see where things are at in terms of getting the 7.x-2.x branch ready for production use. Is anyone using the D7 module in a production environment?

vasike’s picture

i can confirm that i'm using a dev version of D7 version in a production environment, Salesforce Suite 7.x-2.x-dev (2011-Oct-28).
This version it's a patched one, within patch from #1056630-24: Bug: sf_user allows creating many-to-many relationships between SF and Drupal objects, even as it assumes they're one-to-one

kostajh’s picture

I'm going to release an alpha2, as there are a lot of fixes.

kostajh’s picture

Status: Active » Closed (fixed)