Clean up.
Hey guys,
I started to make use of the framework available to us. I would like to propose a change of api in the hook_submit_to_salesforce
from a function definition of hook_submit_to_salesforce($sf_object_code,$all_fields) to hook_submit_to_salesforce($sf_object_code,$all_fields,$node);
The reason for the api change is the lots of other contextual information might be stored in the webform node id.
Here's what I mean I am trying to implement the Assignment Rule Feature available in Salesforce http://www.salesforce.com/us/developer/docs/api/Content/sforce_api_heade...
And I plan to do that by storing and gathering user intention information in the node object. Kinda like what we are doing in $node->use_salesforce;
-- removed comment --
Pushing up to the 3.x branch since the issue deals with the Salesforce API.
Comments
Comment #1
chriscalip commentedComment #2
chriscalip commentedComment #3
chriscalip commentedHey guys,
I started to make use of the framework available to us. I would like to propose a change of api in the
hook_submit_to_salesforce
from a function definition of
hook_submit_to_salesforce($sf_object_code,$all_fields) to hook_submit_to_salesforce($sf_object_code,$all_fields,$node);
The reason for the api change is the lots of other contextual information might be stored in the webform node id.
Here's what I mean I am trying to implement the Assignment Rule Feature available in Salesforce http://www.salesforce.com/us/developer/docs/api/Content/sforce_api_heade...
And I plan to do that by storing and gathering user intention information in the node object. Kinda like what we are doing in $node->use_salesforce;
Comment #4
chriscalip commentedComment #5
chriscalip commented-- removed comment --
Comment #6
obsidiandesign commentedPushing up to the 3.x branch since the issue deals with the Salesforce API.