Contact Merge Fixup is Queueable and Calls correct Rollup Process

[jjbennett]

This pull request includes some code cleanup, the move from future to queueable in Contact Merge and ensures the correct rollup process is called on the related Account record.

Critical Changes

Changes

Issues Closed

• Fixes Contact Merge does not use Customizable Rollups for Account post-merge rollup fixing #4071
• Fixes CON_ContactMerge_TDTM cannot be run from batch apex #2463

New Metadata

Deleted Metadata

[jjbennett]

**lurch: attach W-030823

[LurchTheButler]

Tracking W-030823

[rponti-sforg]

@jjbennett Before I merge this, I wanted to confirm with you if this is indeed 'mergeable'... Was there anything else that needed to be 'prepped' for this merge? I ran 'happy-path' regressions for Contact Merge and ran through the Contact Merge Test Scenarios in the WI associated with this PR. Just let me know if you have any questions.

[jjbennett]

@rponti-sforg thanks for the double check. Yes, this should be good to merge. You had done the QA on each individual PR but I thought it'd be good to do this last run through on everything together so thank you!

[rponti-sforg]

QE testing is complete for this PR. Tests have passed.

For further testing details, see: https://foundation.lightning.force.com/lightning/r/agf__ADM_Work__c/a2x1E000008Ll0VQAS/view

Merging PR and deleting branch.

[rponti-sforg]

@jjbennett We have a robot test failure on this one:

Build flow qa_org completed with status fail
2019-04-02 09:40:35: MetadataComponentFailure: Update of Layout Campaign-NPSP Campaign Layout: Error: Invalid field:OPPORTUNITY.NAME in related list:RelatedOpportunityList

Just let me know if safe to merge or if you want another build run on it.

[RadSFDeveloper]

@rponti-sforg , @jjbennett : the error on the page layout during the qa build is intermittent and it happened on other PRs' builds in the last week or two. @davidmreed thoughts?

[force2b]

Thanks @RadSFDeveloper.
@rponti-sforg You can merge this.

[davidmreed]

@RadSFDeveloper Our error tracking documents classify the page layout issue (failures with "invalid field in related list") as an intermittent problem solved by a rebuild. We don't have a fix documented.