…n user has disabled the widget

…ations' into feature/242__bgeWidgetFixedValidations

…n user has disabled the widget

…tchUpdateBGE

Update Elevate Recurring Gifts When Info Is Updated in Batch Gift Entry

…widget in do not charge state

…eature/242__pauseE2EFix

…ng Type Fixed

# Conflicts:
#	force-app/main/default/lwc/geFormRenderer/__tests__/geFormRenderer.test.js
#	force-app/main/default/lwc/geFormRenderer/geFormRenderer.html
#	force-app/main/default/lwc/geFormRenderer/geFormRenderer.js
#	force-app/main/default/lwc/geFormWidget/geFormWidget.js

…w Payment Info is required

…dgetFixedValidations

Add a Validation to Prevent a Gift Entry User from Choosing the "Fixed" schedule recurring type for Elevate Recurring Gifts in Batch Gift Entry

…ay-assignment-bug-fixes

Fix Display of Gateway Management Error and Correct Clone Behavior

…E2EFix

Pause API E2E fixes

…lesforceFoundation/NPSP into feature/242__gateway-assignment-tests

…ableFix

Fix for colliding queueables in Gift Entry

…lesforceFoundation/NPSP into feature/242__gateway-assignment-tests

…ateway

remove brackets from DEFAULT_NAME_ON_CARD for paya validation

…ay-assignment-tests

Feature/242  gateway assignment tests

…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

Feature 242

…lError

Add back missing custom labels causing beta upload failure

… created through the UI

…erRefundTests

Updating our refund logic to work with negative payments and no Debit Type

…ization

242 NPSP localized labels

…ization

NPSP Localization

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

- Changing the test setup for this unit test to use .addyear() and .addDay() instead of a fixed number of days that it works with leap years.

…RDPauseUnitTest

W-12632596 - Fix unit test for Recurring Donation Pause

Add Q3 quadrant tags to robot tests

…ot_2

Fix a few locators for Q3 robot tests

Co-authored-by: Melissa Barber <mbarber@salesforce.com>

…lesforceFoundation/NPSP into feature/addStaticReleaseNotes

…Trials