-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
W-7780834 BDI Donation Stage Defaults to "Opportunity Stage When Fully Paid" value #6810
W-7780834 BDI Donation Stage Defaults to "Opportunity Stage When Fully Paid" value #6810
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, just a few small things.
} else { | ||
defaultClosedWonStage = ''; | ||
// if no field is specified in contact setting, then query for the active isWon value and use that |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
// if no field is specified in contact setting, then query for the active isWon value and use that | |
// if no stage name is specified in contact setting, then query for the active isWon value and use that |
* in Contact Setting Payments_Auto_Close_Stage_Name__c | ||
*/ | ||
@IsTest | ||
static void donationShouldUseDIDonationStage() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These two tests are good, but I would consider combining them into one unit test with two data import records to reduce the total number of DML statements and trigger run time (just concerned about total test execution time). Also you could consider just running these synchronously with BDI_DataImport_API.processDataImportRecords instead of batch execution which should save a little more processing time but not effect the outcome. If these didn't involve DML I would agree its cleaner to have them separate.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Implemented, thanks for the suggestions!
WHERE IsActive = TRUE | ||
AND IsWon = TRUE | ||
]; | ||
if (stages.size() > 0) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We could replace these 5 lines of code with the following:
defaultClosedWonStage = stages.size()>0 ? stages[0].MasterLabel : '';
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool. Implemented, thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good 👍
Fixed the issue where BDI Donation Stage ignores Opportunity Stage When Fully Paid value. Now, if "Opportunity Stage When Fully Paid" setting has a value, the default Donation Stage will be set to that value.
(Note that DI's Donation Stage, if different than Opportunity Stage When Fully Paid value, will take precedence)
For reference, here is a table summarizing expected results https://salesforce.quip.com/hW4eA11a5zFd
Critical Changes
Changes
NPSP Data Importer Enhancements
Issues Closed
Community Ideas Delivered
Features Intended for Future Release
Features for Elevate Customers
New Metadata
Deleted Metadata