coveralls
commented
6 years ago Coverage remained the same at 100.0% when pulling 830cd8e8012271ef31b17d1cc772d8a77a50fba8 on stripe-salesforce-integration into 9054f7fc14653dc0f97e26b7686326dac6945494 on master.
This PR takes the charge object returned by Stripe and passes it to Salesforce.
Supporters table in Salesforce
This adds the optional parameters (i.e., those that are not required in our Salesforce configuration) to the Supporter table.
Some fields that are used in the old site were left out:
FirstName: we have to first separate both from the name fieldWeb_Login__c: we decided that we don't want to save supporter data in our databaseOwnerId: it is defined in maloca asSalesforceUser.current_user.Id, but at this stage we don't have any way to deal with a Salesforce user.Email_is_Web_Login_legacy__c: the new website won't have a loginAlso, at the moment
LastNameis still using the full name until we find a good way of separating it. I am using placeholders for the greeting for the same reason. Maloca's code is also truncating some fields, which for now we are not doing either.Donations table in Salesforce
This PR also adds the optional parameters (i.e., those that are not required in our Salesforce configuration) to the Donation table.
Some fields that are used in the old site were left out:
Web_Payment_Number__c: It needs a complex calculation that requires searching for donations in Salesforce.Donation_for__candWeb_campaign_reference__c: Both need appeals, which are not yet implemented.OwnerId: it is defined in the old site asSalesforceUser.current_user.Id, but at this stage we don't have any way to deal with a Salesforce user.Also, the close date is now calculated from the payment data.
Readme
Finally, this PR updates the readme to explain how to use the gem
Issues added
I've added the following issues:
OwnerIdfield