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

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

Merged
merged 44 commits into from
Nov 10, 2022

Conversation

daniel-fuller
Copy link
Contributor

@daniel-fuller daniel-fuller commented Oct 18, 2022

This work allows a user to switch between a recurring and one-time Elevate-connected gift in batch gift entry before processing the gift in the batch.

W-11871096

Critical Changes

Changes

Issues Closed

Community Ideas Delivered

Features Intended for Future Release

Features for Elevate Customers

New Metadata

Deleted Metadata

salesforce-org-metaci bot and others added 30 commits October 14, 2022 21:03
@daniel-fuller daniel-fuller marked this pull request as ready for review November 3, 2022 18:02
@daniel-fuller
Copy link
Contributor Author

We are still waiting on a label approval from @ErinWiedemer in this one

Copy link
Contributor

@npsp-reedestockton npsp-reedestockton left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, @daniel-fuller. I appreciate the fact that you always improve what you touch!

@ErinWiedemer
Copy link
Contributor

@daniel-fuller Stephen Cox is reviewing the error message now and I hope that we'll have an approval tomorrow. Right now, he's leaning toward the following text for the error message: You can’t edit this Elevate-connected gift until you re-enter the payment information. Select Edit Payment Information. I'll let you know as soon as I get confirmation from CCX.

Copy link
Contributor

@ErinWiedemer ErinWiedemer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't have the final text for the error message from CCX UI Text Review yet, but I hope to have it tomorrow. I'll Slack you as soon as I get it. But the message will be different from what is in this PR.

Copy link
Contributor

@voduyemi voduyemi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good @daniel-fuller , I just have a comment about when we null the fields

<language>en_US</language>
<protected>true</protected>
<shortDescription>Warns users to re-enter payment information when editing Elevate-connected gifts</shortDescription>
<value>You can’t edit this Elevate-connected gift until you re-enter the payment information. Select Edit Payment Information.</value>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nitpick, but I like to avoid apostrophes in Custom Labels (especially this weird rich-text version!)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

updated

import PAYMENT_ELEVATE_ELEVATE_BATCH_ID from '@salesforce/schema/DataImport__c.Payment_Elevate_Batch_Id__c';
import GeGatewaySettings from 'c/geGatewaySettings';
import Gift from 'c/geGift';
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we removed one unused import, then added another?

@@ -12,6 +31,93 @@ describe('ge-gift', () => {
jest.clearAllMocks();
});

it ('removable elevate status should return false for imported status', async () => {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These tests are great!

this.getFieldValue(PAYMENT_STATUS.fieldApiName) === PAYMENT_STATUSES.AUTHORIZED ||
this.getFieldValue(PAYMENT_STATUS.fieldApiName) === PAYMENT_STATUSES.PENDING
) ||
this.hasCommitmentId();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wouldn't this last condition allow an imported RD to be removed from the Batch, and is that ok? I only ask because we explicitly check for a Status of not Imported in the first condition.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@lparrott You're right. Technically, I don't think it would be a problem since it's already been processed at that point and the Update button is disabled for Imported but I updated the parentheses to be more accurate

Copy link
Contributor

@ErinWiedemer ErinWiedemer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@andrewyu-salesforce andrewyu-salesforce merged commit 3127098 into feature/242 Nov 10, 2022
@andrewyu-salesforce andrewyu-salesforce deleted the feature/242__rd2BatchUpdateBGE branch November 10, 2022 19:17
@salesforce-org-metaci salesforce-org-metaci bot mentioned this pull request Nov 10, 2022
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.

None yet

6 participants