Skip to content
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

Merge feature/242 into feature/242__use-configured-payment-methods #7123

Open
wants to merge 604 commits into
base: feature/242__use-configured-payment-methods
Choose a base branch
from

Conversation

salesforce-org-metaci[bot]
Copy link
Contributor

This pull request was automatically generated because an automated merge hit a merge conflict

@salesforce-org-metaci salesforce-org-metaci bot requested a review from a team as a code owner October 13, 2022 01:49
@salesforce-org-metaci salesforce-org-metaci bot requested review from davidjray and removed request for a team October 13, 2022 01:49
lparrott and others added 27 commits November 16, 2022 08:55
…PatchFix

Fix for Pause Request to use PATCH on Updates
…ftEntryController-unit-tests

Add new gateway assignment unit tests.
…PatchFix

Added logic to fix pause patch calls
…lError

Add back missing custom labels causing beta upload failure
…erRefundTests

Updating our refund logic to work with negative payments and no Debit Type
Fixed incorrect internal matches with BDI matching when using the 'Contact Duplicate Rules' (aka Duplicate Management) option.  Essentially if you had two Data Import records with any one of the 4 pieces of contact information used for matching (first name, last name, email, phone) matching, then it would match the two records together incorrectly and only create one new contact.  It should only match internally like that if all the pieces of contact information match.

The cause of the issue was that because the Contact matching rule name didn't include the name of any of the fields used for matching, it was creating a key for matching for each field with just the field populated and all others blank.  This meant that if any of these contact fields matched, the whole contact would be matched (which is very problematic for things like first name).

The fix was to basically make sure that if Duplicate Management was enabled, then it should never include a blank value unless the contact field was actually blank.

Also updated the test class to test the partial contact match scenario and the exact internal duplicate match scenario.  Also added tests for non-dry run scenarios.
…MgmtInternalMatching

W-12250612 - Fixed issue with BDI matching when using Dupe Mgmt
…s-not-updated-ge-batch-process

W-15110724 - 250__fields-not-updated-ge-batch-process
'Upgrade process complete' heading is marked with a heading tag <h4> to overcome accessibility issue.
'Data Migration Run' was only styled to look like headings but wasn’t marked as such, hence added h2 heading tag explicitly.
…structure.

In RD2_EnablementDelegate.cmp elements are reformed to maintain consistency and proper HTML structure.
To ensure that focus moves to new content when it updates, changes has been added to the RD2_EnablementDelegateController.js file for the Validate and Run Migration buttons.
…7427-avoid-use-of-implicit-headings

w-9537427 avoid use of implicit headings
added he 'setFocus' method in RD2 _EnablementDelegateHelper.js and invoked it from RD2_EnablementDelegateController.js.
…6698-update-markup-to-contain-well-formed-elements

W-9536698 ERD page should contain well-formed elements
…6986-move-focus-to-new-content-on-Upgrade-to-ERD-page

W-9536986-move focus to new content on Upgrade to Enhanced Recurring Donations page
Before checking access, fields in the GAU Allocations fieldset are checked for formula field type and permissionability.
…46973-add-formula-field-to-manage-allocations-fieldset

W-15046973 Fix error on adding formula field to GAU allocations fieldset
Change for template tag in bdiObjectMappings.html and bdiFieldMappingModal.html
…28778-invalid-markup-in-bdiObjectMappings

W-16328778 Invalid markup in bdiObjectMappings
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.