PosiGive v0.136
- Jhetah Mae Leornas
Release Date: Feb 19, 2025
Package URL: /packaging/installPackage.apexp?p0=04tOZ0000003H5xYAE
Dependencies
PosiPay version 0.95
PosiPay for Industry Cloud version 0.3
Pre Config
If the version installed from the org is 0.124 or below, please do the following:
Install the PosiGive 0.125 (/packaging/installPackage.apexp?p0=04tOZ0000002rWTYAY)
After Installing go to Setup>Flows then delete these following flow ([PosiPay] Immediate Run of Scheduled Donation, [PosiPay] Scheduled Donations - Schedule)
Then go to Setup>Batch Management and proceed on deactivating these two batch (GiftTransactionStatusUpdate, ScheduleDonationBatch)
Bugfix
Internal Alert Message (Editing issue)
Internal Alert Message is populated in the Person Account, and a toast message appears. If you edit the Internal Alert Message while the existing toast message is still displayed, the old toast message should close automatically. Only the new toast message will show the updated value of the Internal Alert Message field.
Manage Gift Entry - Acknowledgement Channel Validation
In creating a Gift Entry, the Acknowledgement Channel field is auto populated with the value that has set in the Deafault Acknowledgement Channel field.
When Gift Entry is saved, the Gift Entry record is created with the selected Acknowledgement Channel. A Gift Transaction is also created linked to the Gift Entry, with the Acknowledgement Channel field populated to match the Gift Entry’s Acknowledgement Channel.
Donation Order - Create Multiple Order Product records issue
Created an Order where multiple Order Product record was created. When updating the Create Gift Transaction field to True, an Error message displayed.
Manage Gift Entry: Gift Type 'Organization' mismatch with Linked Gift Transaction as 'Individual' When Recurring
In processing The Organization/Household Account record the donor details are mapped to the Gift Entry record.
After processing, the necessary records for the gift are created, and the donor is linked.
The linked Gift Transaction’s Gift Type should be Organization/Household
Manage Gift Entry - Recurring Organization/Household Account's Phone number become empty after processing a Gift Entry
After creating a Gift Entry the following result is expected.
The Matching Rule identifies the existing Organization/household Account record.
The Gift Entry record is mapped to the existing Organization/household Account.
Necessary records for the recurring gift are created.
The matched Organization/household Account is linked to the created records.
Fixed the status of the gift transaction in Manage Gift Entry that remains 'Pending' when the payment method is set to Direct Deposit.
Fix the status of the Gift Transaction, which remains 'Pending' when processing a Gift Entry from a recurring donation (CC and BECS Payment Method).
Fixed the Internal Error when Processing Gift Commitment API using an Individual as Donor Type.
Released
Manage Gift Entry - An error occurs when doing a Once gift entry using Direct Deposit as a payment method.
In processing a Once-off Gift Entry with a Payment Method of Direct Deposit,
After saving,
A Gift Entry record is created and processed where:
New Recurring Gift = FALSE
The necessary records for the once-off gift are created
An Account record is created (new donor details)/updated (update existing donor)
A Payment Instrument record is created ONLY if the Payment Method = Credit Card OR BECS Debit
A Gift Transaction is created
A Gift Transaction Designation is created
Manage Gift Entry - Gift Commitment record issue.
Action:
Navigate to the Gift Entry List View.
Click the New Entry button.
Fill in the gift details, ensuring:
New Recurring Gift = TRUE.Fill in the recurring gift fields:
Effective Start Date, Expected End Date, Gift Transaction Period, Gift Transaction Interval, Gift Transaction Day (if applicable).
Set Payment Method to
Credit Card.
Save the Gift Entry record.
Expected Result:
If the New Recurring Gift = TRUE (recurring gift),
The following fields for recurring gift on the page have been replaced:
Start Date (custom) → Effective Start Date (standard)
End Date (custom) → Expected End Date (standard)
Transaction Period (custom) → Gift Transaction Period (standard)
Transaction Interval (custom) → Gift Transaction Interval (standard)
Transaction Day (custom) → Gift Transaction Day (standard)
If the Gift Transaction Period = Monthly, the Gift Transaction Day field is displayed
If the Gift Transaction Period != Monthly, the Gift Transaction Day field is hidden
After saving,
A Gift Entry record is created and processed where:
New Recurring Gift = TRUE
Effective Start Date (field) = Effective Start Date
Expected End Date (field) = Expected End Date
Transaction Period (field) = Gift Transaction Period
Transaction Interval (field) = Gift Transaction Interval
Transaction Day (field) = Gift Transaction Day (UI)
The necessary records for the recurring gift are created
An Account record is created (new donor details)/updated (update existing donor)
A Payment Instrument record is created ONLY if the Payment Method = Credit Card OR BECS Debit
A Gift Commitment is created where:
Effective Start Date = Gift Entry’s Effective Start Date
Expected End Date = Gift Entry’s Expected End Date
A Gift Commitment Schedule is created where:
Start Date = Gift Entry’s Effective Start Date
End Date = Gift Entry’s Expected End Date
Transaction Period = Gift Entry’s Transaction Period
Transaction Interval = Gift Entry’s Transaction Interval
Transaction Day = Gift Entry’s Transaction Day
A Gift Default Designation is created
A Gift Transaction is created
A Gift Transaction Designation is created
Scheduled Donation batch - BECS Debit Gift Transaction was not included.
Actual Result:
When running the Scheduled Donation batch, Gift Transactions that are BECS Debit will not be included resulting in Gift Transaction remaining unpaid.
Expected Result:
When running the Scheduled Donation batch, Gift Transactions that are BECS Debit and also meet the criteria for Scheduled donation batch processing should be included.
Manage Gift Entry - Gift Transaction naming has issue when the Donor type is Organization and the Donation type is Once Off
When creating a gift entry where the Donor type is Organization and Donation type is Once off,
The Gift Transaction name should be complete and follow the normal format.
Manage Gift Entry: Barcode field - matched donor cannot be searched.
The user can only search for donors who are not deceased
The Donor Details field should be populated
The Gift Entry record is mapped to the existing Person Account.
Gift Entry Process for Recurring Gift - 'No such column 'EffectiveStartDate' on entity 'GiftEntry'
From Malou (CCV): When EffectiveStartDate is added in the Gift Entry Mapping custom metadata type, it throws an error. We've tried adding to permission sets, but still an error.
Expected Result:
When processing a Gift Entry record for a recurring gift,
The Gift Entry record should be processed successfully
The following records should be created:
Gift Commitment
Gift Commitment Schedule
Gift Transaction
Return Mail Entry - Outreach Source Code Field Not Populated in Campaign Member Details
Description:
The Campaign Member Details section fields are expected to be auto-populated when a valid barcode is scanned on the Return Mail Entry page. While most fields (e.g., Donor Information, Mail Preferences) are correctly populated based on the matching Campaign Member record, the Outreach Source Code field remains empty and does not auto-populate.
Scheduled Donation batch - BECS Debit Gift Transaction was not included.
When running the Scheduled Donation batch, Gift Transactions that are BECS Debit and also meet the criteria for Scheduled donation batch processing should be included.
Manage Gift Entry - Two Internal Alert toast Message appears when creating a gift entry via New Entry button in Person Account/Account record page and New entry button from Gift Batch
Action:
Navigate to the Account detail or Gift Batch page.
Click the New Entry button.
Verify the Donor field is auto-populated with the current Person Account record.
Save the record.
Data:
Auto-Populated Donor: Person Account.
Account Internal Alert Message: "Account requires special handling."
Expected Result:
A toast message appears with the text: "Account requires special handling."
PosiGive API - Missing Account Holder Name for BECS Debit/ACH Payment Instrument
Once-off gift
Pre-work:
Execute an API callout in Postman where the API request body contains the necessary details for a once-off gift
Once the API callout is executed,
A PosiPay Log record is created where it contains the external API request
The following records are expected to be created/updated:
Account
Payment Instrument
If the Payment Instrument’s Type = BECS Debit, the Payment Instrument’s Account Holder Name field is populated based on the provided account holder name on accountHolderName from the external API request
Gift Transaction
Gift Transaction Designation
Recurring gift
Pre-work:
Execute an API callout in Postman where the API request body contains the necessary details for a recurring gift
Once the API callout is executed,
A PosiPay Log record is created where it contains the external API request
The following records are expected to be created/updated:
Account
Payment Instrument
If the Payment Instrument’s Type = BECS Debit, the Payment Instrument’s Account Holder Name field is populated based on the provided account holder name on accountHolderName from the external API request
Gift Commitment
Gift Commitment Schedule
Gift Default Designation
Gift Transaction
Gift Transaction Designation
Result:
If the Payment Instrument’s Type is BECS Debit, the process is failed
If the Payment Instrument’s type is ACH, the process will be successful; however, the Account Holder Name field in the Payment Instrument record remains empty.
Manage Gift Entry - Existing Organization/Household Account - Donor Matching error
When the user attempts to use the matching rule for processing a Gift Entry, where existing Organization/Household Account record has a Phone number but an error occurs and PosiPay Log record is created but empty details
Steps
Navigate to the Gift Entry page (via the New Entry button in the Gift Entry list view or Gift Batch).
Enter donor details matching the Organization/Household Account record
Organization Name
Phone
Save the Gift Entry record.
Process the Gift Entry record.
Expected Result
The Matching Rule identifies the existing Organization/household Account record.
The Gift Entry record is mapped to the existing Organization/household Account.
Necessary records for the recurring gift are created.
The matched Organization/household Account is linked to the created records.
Manage Gift Entry - Gift Transaction's Transaction Completion Date is populated even though the Status is not Paid
Steps:
Navigate to Gift Entry list and click on New Entry button to create new gift entry.
Fill out gift entry fields and make sure New Recurring Gift is TRUE.
After creating the gift entry, check if gift entry’s Gift Transaction’s Transaction Completion Date is populated.
Expected Result:
When creating a new Gift Entry and a Gift Transaction status is not yet Paid, the Gift Transaction’s Transaction Completion Date should be EMPTY.
Manage Gift Entry - When editing a gift entry via Edit Entry button from Gift entry record, an error occurs
Action:
Navigate to an existing Gift Entry record.
Click the Edit Entry button.
Observe the Manage Gift Entry page that loads.
Navigate to the Payment Information section.
Expected Result:
The Payment Information section is accessible.
Manage Gift Entry - The Receiving Bank Account field did not display below the Payment Identifier field
Expected Result
When creating a once-off single Gift Entry record via the Manage Gift Entry (New Entry button in Gift Entry list view and Person Account record detail page),
If the selected Payment Method = Direct Deposit,
The Receiving Bank Account field will display below the Payment Identifier field
Manage Gift Entry: Error Occurred on Recurring Donation
Test Steps
Navigate to the Gift Entry page (via the New Entry button in the Gift Entry list view or Gift Batch).
Enter donor details matching the Organization/Household Account record
Save the Gift Entry record.
Process the Gift Entry record.
Expected Result
The Gift Entry record is mapped to the Account.
Necessary records for the recurring gift are created.
Process Gift Batch - Process gift batch fails when gift entry payment methods are Cash. Check, and Direct Deposit.
Test Steps:
Navigate to Gift Batch Record where Gift Entry payment methods are Cash, Check, and Direct Deposit.
Click on Process Gift Batch
Expected Result:
When processing a gift batch by clicking on Process Gift Batch button on a Gift Batch record where gift entry payment methods are Cash, Check, and Direct Deposit,
Gift Batch Status will be updated to Processed,
Gift Entry records will be processed and existing functionality will be followed.
Process Gift Batch - Process gift batch fails when gift entries are recurring gifts
Test Steps:
Navigate to Gift Batch Record where Gift Entry are recurring.
Click on Process Gift Batch
Expected Result:
When processing a gift batch by clicking on Process Gift Batch button on a Gift Batch record where gift entries are recurring,
Gift Batch Status will be updated to Processed,
Gift Entry records will be processed and existing functionality will be followed.
Scheduled Donation - Latest Gateway Invoice not linked to Gift Transaction record
Test Steps:
Create a Gift Batch record with a recurring Gift Entry.
Process the Gift Batch
Run the Scheduled Donation.
Check if Gift Transaction has been processed successfully and records are linked correctly:
Latest Gateway Transaction
Latest Gateway Invoice
Expected Result:
When the Scheduled Donation is executed,
The Gift Transaction records will be processed:
1st: The Gift Transaction record is updated where:
Status = Processing
2nd: An invoice API callout will be executed for each Gift Transaction record
3rd: Assuming the webhook is configured properly:
A Gateway Invoice record is created and is linked to the Gift Transaction record.
A Gateway Transaction record is created and is linked to the Gift Transaction record.
The Gift Transaction record is updated where:
Status = Paid (if invoice is successful) / Failed (if invoice is failed) → monitor the field’s history
Exclude from Payment Processing = TRUE
Other fields are populated based on the parsed payload
Manage Gift Entry - BECS Debit's Current Gift Commitment schedule doesn't have a linked Payment Instrument.
Test Steps
Navigate to the Gift Entry List View.
Click the New Entry button.
Fill in the gift details, ensuring:
New Recurring Gift = TRUE.Fill in the recurring gift fields:
Effective Start Date, Expected End Date, Gift Transaction Period, Gift Transaction Interval, Gift Transaction Day (if applicable).
Set Payment Method to
BECS Debit.
Save the Gift Entry record.
Run the Scheduled Donation batch.
Verify if appropriate records are created:
Gift Commitment
Gift Commitment Schedule
Payment Instrument linked to Gift Commitment Schedule
Gift Transaction
Gift Transaction Designations
Payment Instrument
Expected Result
A Gift Entry record is created and processed where:
New Recurring Gift = TRUE
Effective Start Date (field) = Effective Start Date (UI)
Expected End Date (field) = Expected End Date (UI)
Transaction Period (field) = Gift Transaction Period (UI)
Transaction Interval (field) = Gift Transaction Interval (UI)
Transaction Day (field) = Gift Transaction Day (UI)
The necessary records for the recurring gift are created
An Account record is created (new donor details)/updated (update existing donor)
A Payment Instrument record is created ONLY if the Payment Method = Credit Card OR BECS Debit
A Gift Commitment is created where:
Effective Start Date = Gift Entry’s Effective Start Date
Expected End Date = Gift Entry’s Expected End Date
A Gift Commitment Schedule is created where:
Start Date = Gift Entry’s Effective Start Date
End Date = Gift Entry’s Expected End Date
Transaction Period = Gift Entry’s Transaction Period
Transaction Interval = Gift Entry’s Transaction Interval
Transaction Day = Gift Entry’s Transaction Day
Payment Instrument
A Gift Default Designation is created
A Gift Transaction is created
A Gift Transaction Designation is created
Manage Gift Entry - Gift Transaction's Transaction Completion Date is populated even though the Status is not Paid
Steps:
Navigate to Gift Entry list and click on New Entry button to create new gift entry.
Fill out gift entry fields and make sure New Recurring Gift is TRUE.
After creating the gift entry, check if gift entry’s Gift Transaction’s Transaction Completion Date is populated.
Expected Result:
When creating a new Gift Entry and a Gift Transaction status is not yet Paid, the Gift Transaction’s Transaction Completion Date should be EMPTY.
Updates
Added new flow in processing Once-off Gift Entry and Recurring Gifts
Added the [PosiPay] Process Gift Entry Once-Off & Recurring flow and this flow will process a Gift Entry record for once-off and recurring gifts.
Add the correct BECS Debit and Direct Deposit Payment Methods to the Gift Entry, Payment Instrument, Gift Commitment Schedule, and Gift Transaction (Winter '25)
The single Gift Entry and batch Gift Entry processes are working as expected especially when using the new BECS Debit and Direct Deposit picklist values
The Gift Entry record should have a Payment Method referencing the new BECS Debit and Direct Deposit picklist values
The Payment Instrument record should have a Type referencing the new BECS Debit picklist value
For recurring gift, the Gift Commitment Schedule record should have a Payment Method referencing the new BECS Debit and Direct Deposit picklist values
For once-off and recurring gifts, the Gift Transaction record should have a Payment Method referencing the new BECS Debit and Direct Deposit picklist values
The Scheduled Donation should pick up Gift Transaction records that has a Payment Method referencing the new BECS Debit picklist value
Automatic bank reconciliation when matching a Bank Statement Line record to a Gift Transaction record where it has a Payment Method referencing the new Direct Deposit picklist value
Gift Entry Process for Once-Off - Create Payment Instrument for BECS Debit as Standard NPC Process Gift Entry doesn't support Creation of Payment Instrument for Custom Payment Methods
The single Gift Entry and batch Gift Entry processes when using the new BECS Debit picklist value
The Gift Entry record should have a Payment Method referencing the new BECS Debit picklist value
The Payment Instrument record should have a Type referencing the new BECS Debit picklist value
For recurring gift, the Gift Commitment Schedule record should have a Payment Method referencing the new BECS Debit picklist value
For once-off and recurring gifts, the Gift Transaction record should have a Payment Method referencing the new BECS Debit picklist value
Integrate NPC’s Winter ’25 Gift Entry in PosiGive’s Gift Entry
Test 1: Single Gift Entry via the New Entry button in Gift Entry list view,
If the New Recurring Gift = FALSE (once-off gift),
The existing functionality of the page for once-off gift will be followed
After saving,
A Gift Entry record is created and processed where:
New Recurring Gift = FALSE
The necessary records for the once-off gift are created
An Account record is created (new donor details)/updated (update existing donor)
A Payment Instrument record is created ONLY if the Payment Method = Credit Card OR BECS Debit
A Gift Transaction is created
A Gift Transaction Designation is created
If the New Recurring Gift = TRUE (recurring gift),
The following fields for recurring gift on the page have been replaced:
Start Date (custom) → Effective Start Date (standard)
End Date (custom) → Expected End Date (standard)
Transaction Period (custom) → Gift Transaction Period (standard)
Transaction Interval (custom) → Gift Transaction Interval (standard)
Transaction Day (custom) → Gift Transaction Day (standard)
If the Gift Transaction Period = Monthly, the Gift Transaction Day field is displayed
If the Gift Transaction Period != Monthly, the Gift Transaction Day field is hidden
After saving,
A Gift Entry record is created and processed where:
New Recurring Gift = TRUE
Effective Start Date (field) = Effective Start Date (UI)
Expected End Date (field) = Expected End Date (UI)
Transaction Period (field) = Gift Transaction Period (UI)
Transaction Interval (field) = Gift Transaction Interval (UI)
Transaction Day (field) = Gift Transaction Day (UI)
The necessary records for the recurring gift are created
An Account record is created (new donor details)/updated (update existing donor)
A Payment Instrument record is created ONLY if the Payment Method = Credit Card OR BECS Debit
A Gift Commitment is created where:
Effective Start Date = Gift Entry’s Effective Start Date
Expected End Date = Gift Entry’s Expected End Date
A Gift Commitment Schedule is created where:
Start Date = Gift Entry’s Effective Start Date
End Date = Gift Entry’s Expected End Date
Transaction Period = Gift Entry’s Transaction Period
Transaction Interval = Gift Entry’s Transaction Interval
Transaction Day = Gift Entry’s Transaction Day
A Gift Default Designation is created
A Gift Transaction is created
A Gift Transaction Designation is created
Test 2: Single Gift Entry via the New Entry button in Account record detail page,
If the New Recurring Gift = FALSE (once-off gift),
The existing functionality of the page for once-off gift will be followed
After saving,
A Gift Entry record is created and processed where:
New Recurring Gift = FALSE
The necessary records for the once-off gift are created
An Account record is updated (update existing donor)
A Payment Instrument record is created ONLY if the Payment Method = Credit Card OR BECS Debit
A Gift Transaction is created
A Gift Transaction Designation is created
If the New Recurring Gift = TRUE (recurring gift),
The following fields for recurring gift on the page have been replaced:
Start Date (custom) → Effective Start Date (standard)
End Date (custom) → Expected End Date (standard)
Transaction Period (custom) → Gift Transaction Period (standard)
Transaction Interval (custom) → Gift Transaction Interval (standard)
Transaction Day (custom) → Gift Transaction Day (standard)
If the Gift Transaction Period = Monthly, the Gift Transaction Day field is displayed
If the Gift Transaction Period != Monthly, the Gift Transaction Day field is hidden
After saving,
A Gift Entry record is created and processed where:
New Recurring Gift = TRUE
Effective Start Date (field) = Effective Start Date (UI)
Expected End Date (field) = Expected End Date (UI)
Transaction Period (field) = Gift Transaction Period (UI)
Transaction Interval (field) = Gift Transaction Interval (UI)
Transaction Day (field) = Gift Transaction Day (UI)
The necessary records for the recurring gift are created
An Account record is updated (update existing donor)
A Payment Instrument record is created ONLY if the Payment Method = Credit Card OR BECS Debit
A Gift Commitment is created where:
Effective Start Date = Gift Entry’s Effective Start Date
Expected End Date = Gift Entry’s Expected End Date
A Gift Commitment Schedule is created where:
Start Date = Gift Entry’s Effective Start Date
End Date = Gift Entry’s Expected End Date
Transaction Period = Gift Entry’s Transaction Period
Transaction Interval = Gift Entry’s Transaction Interval
Transaction Day = Gift Entry’s Transaction Day
A Gift Default Designation is created
A Gift Transaction is created
A Gift Transaction Designation is created
Test 3: Batch Gift Entry via the New Entry button then Process Gift Batch button in Gift Batch record detail page,
If the New Recurring Gift = FALSE (once-off gift),
The existing functionality of the page for once-off gift will be followed
After saving,
A Gift Entry record is created where:
New Recurring Gift = FALSE
After the Gift Entry record is processed,
The necessary records for the once-off gift are created
An Account record is created (new donor details)/updated (update existing donor)
A Payment Instrument record is created ONLY if the Payment Method = Credit Card OR BECS Debit
A Gift Transaction is created
A Gift Transaction Designation is created
If the New Recurring Gift = TRUE (recurring gift),
The following fields for recurring gift on the page have been replaced:
Start Date (custom) → Effective Start Date (standard)
End Date (custom) → Expected End Date (standard)
Transaction Period (custom) → Gift Transaction Period (standard)
Transaction Interval (custom) → Gift Transaction Interval (standard)
Transaction Day (custom) → Gift Transaction Day (standard)
If the Gift Transaction Period = Monthly, the Gift Transaction Day field is displayed
If the Gift Transaction Period != Monthly, the Gift Transaction Day field is hidden
After saving,
A Gift Entry record is created where:
New Recurring Gift = TRUE
Effective Start Date (field) = Effective Start Date (UI)
Expected End Date (field) = Expected End Date (UI)
Transaction Period (field) = Gift Transaction Period (UI)
Transaction Interval (field) = Gift Transaction Interval (UI)
Transaction Day (field) = Gift Transaction Day (UI)
After the Gift Entry record is processed,
The necessary records for the recurring gift are created
An Account record is created (new donor details)/updated (update existing donor)
A Payment Instrument record is created ONLY if the Payment Method = Credit Card OR BECS Debit
A Gift Commitment is created where:
Effective Start Date = Gift Entry’s Effective Start Date
Expected End Date = Gift Entry’s Expected End Date
A Gift Commitment Schedule is created where:
Start Date = Gift Entry’s Effective Start Date
End Date = Gift Entry’s Expected End Date
Transaction Period = Gift Entry’s Transaction Period
Transaction Interval = Gift Entry’s Transaction Interval
Transaction Day = Gift Entry’s Transaction Day
A Gift Default Designation is created
A Gift Transaction is created
A Gift Transaction Designation is created
Delete PosiGive’s Gift Entry Fields for Recurring
The following custom fields on the Gift Entry object are deleted (these are replaced by standard objects):
Donation Type
Start Date
End Date
Transaction Period
Transaction Interval
Transaction Day
PosiGive Settings - Add 'None' option to Field Set for Gift Entry Fields
When the PosiGive Settings page loads,
On the Manage Gift Entry section,
The Field Set for Gift Entry Fields field has the following picklist values:
None
Available Field Sets of the Gift Entry object
If the PosiGive Settings custom setting’s Field Set for Gift Entry Fields = EMPTY, the Field Set for Gift Entry Fields (UI) field is autopopulated with ‘None’ value
If the PosiGive Settings custom setting’s Field Set for Gift Entry Fields != EMPTY, the Field Set for Gift Entry Fields (UI) field is autopopulated based on the field set stored to PosiGive Settings custom setting’s Field Set for Gift Entry Fields field
When the Save button is clicked,
If the Field Set for Gift Entry Fields (UI) = None, the PosiGive Settings custom setting’s Field Set for Gift Entry Fields field is EMPTY
If the Field Set for Gift Entry Fields (UI) != None, the PosiGive Settings custom setting’s Field Set for Gift Entry Fields field is populated based on the selected field set
Convert the "New Entry" button into LWC instead of a flow
When "New Entry" is clicked on the account page, the screen width will significantly increase compared to the initial size.
When searching for longer names, such as Campaigns, the names should not be truncated.
All new entry functions, behavior, and expectations should work as intended.
Integrate the Missing Winter '25 Manage Gift Entry Flow updates in PosiGive
Gift Entry Internal Alert
When creating a Gift Entry record via the Manage Gift Entry page (New Entry button in the Gift Entry list view),
When a donor is selected,
If the selected donor is a Person Account record,
If the Person Account’s Internal Alert Message is NOT empty,
A toast message will pop up where the message is based on the Person Account’s Internal Alert Message
If the Person Account’s Internal Alert Message is EMPTY, the Person Account’s equivalent Contact record will be checked,
If the Person Account’s equivalent Contact’s Internal Alert Message is NOT empty,
A toast message will pop up where the message is based on the equivalent Contact’s Internal Alert Message
If the Person Account’s equivalent Contact’s Internal Alert Message is EMPTY,
NO toast message will pop up
If the selected donor is an Account record,
If the Account’s Internal Alert Message is NOT empty,
A toast message will pop up where the message is based on the Account’s Internal Alert Message
If the Account’s Internal Alert Message is EMPTY,
NO toast message will pop up
When creating a Gift Entry record via the Manage Gift Entry page (New Entry button in the Account record detail page),
The Donor field is auto-populated based on the current donor record,
If the current donor is a Person Account record,
If the Person Account’s Internal Alert Message is NOT empty,
A toast message will pop up where the message is based on the Person Account’s Internal Alert Message
If the Person Account’s Internal Alert Message is EMPTY, the Person Account’s equivalent Contact record will be checked,
If the Person Account’s equivalent Contact’s Internal Alert Message is NOT empty,
A toast message will pop up where the message is based on the equivalent Contact’s Internal Alert Message
If the Person Account’s equivalent Contact’s Internal Alert Message is EMPTY,
NO toast message will pop up
If the current donor is an Account record,
If the Account’s Internal Alert Message is NOT empty,
A toast message will pop up where the message is based on the Account’s Internal Alert Message
If the Account’s Internal Alert Message is EMPTY,
NO toast message will pop up
When creating a Gift Entry record via the Gift Batch (New Entry button in the Gift Batch record detail page),
When a donor is selected,
If the selected donor is a Person Account record,
If the Person Account’s Internal Alert Message is NOT empty,
A toast message will pop up where the message is based on the Person Account’s Internal Alert Message
If the Person Account’s Internal Alert Message is EMPTY, the Person Account’s equivalent Contact record will be checked,
If the Person Account’s equivalent Contact’s Internal Alert Message is NOT empty,
A toast message will pop up where the message is based on the equivalent Contact’s Internal Alert Message
If the Person Account’s equivalent Contact’s Internal Alert Message is EMPTY,
NO toast message will pop up
If the selected donor is an Account record,
If the Account’s Internal Alert Message is NOT empty,
A toast message will pop up where the message is based on the Account’s Internal Alert Message
If the Account’s Internal Alert Message is EMPTY,
NO toast message will pop up
When a barcode is provided to the Barcode field and a matched Campaign Member record is found,
If the matched Campaign Member record is a Person Account,
If the Person Account’s Internal Alert Message is NOT empty,
A toast message will pop up where the message is based on the Person Account’s Internal Alert Message
If the Person Account’s Internal Alert Message is EMPTY, the Person Account’s equivalent Contact record will be checked,
If the Person Account’s equivalent Contact’s Internal Alert Message is NOT empty,
A toast message will pop up where the message is based on the equivalent Contact’s Internal Alert Message
If the Person Account’s equivalent Contact’s Internal Alert Message is EMPTY,
NO toast message will pop up
If the matched Campaign Member record is an Account,
If the Account’s Internal Alert Message is NOT empty,
A toast message will pop up where the message is based on the Account’s Internal Alert Message
If the Account’s Internal Alert Message is EMPTY,
NO toast message will pop up
If the matched Campaign Member record is a Contact,
If the Contact’s Internal Alert Message is NOT empty,
A toast message will pop up where the message is based on the Contact’s Internal Alert Message
If the Contact’s Internal Alert Message is EMPTY,
NO toast message will pop up
PosiGive API - Missing Cardholder Name for Credit Card Payment Instrument
Test 1: Once-off gift
Pre-work:
Execute an API callout in Postman where the API request body contains the necessary details for a once-off gift
Once the API callout is executed,
A PosiPay Log record is created where it contains the external API request
The following records are expected to be created/updated:
Account
Payment Instrument
If the Payment Instrument’s Type = Credit Card, the Payment Instrument’s Cardholder Name field is populated based on the provided cardholder name on accountHolderName from the external API request
If the Payment Instrument’s Type = BECS Debit, the Payment Instrument’s Account Holder Name field is populated based on the provided account holder name on accountHolderName from the external API request
Gift Transaction
Gift Transaction Designation
Test 2: Recurring gift
Pre-work:
Execute an API callout in Postman where the API request body contains the necessary details for a recurring gift
Once the API callout is executed,
A PosiPay Log record is created where it contains the external API request
The following records are expected to be created/updated:
Account
Payment Instrument
If the Payment Instrument’s Type = Credit Card, the Payment Instrument’s Cardholder Name field is populated based on the provided cardholder name on accountHolderName from the external API request
If the Payment Instrument’s Type = BECS Debit, the Payment Instrument’s Account Holder Name field is populated based on the provided account holder name on accountHolderName from the external API request
Gift Commitment
Gift Commitment Schedule
Gift Default Designation
Gift Transaction
Gift Transaction Designation
Return Mail Entry - Tick the Return Mail Checkbox by Default
When updating the mail preferences of a donor via the Return Mail Entry page
When the Return Mail Entry page loads, the default value of the Return Mail field is TRUE
PosiGive API - Gift Commitment Status
Pre-work:
Execute an API callout in Postman where the API request body contains the necessary details for a recurring gift
Once the API callout is executed,
A PosiPay Log record is created where it contains the external API request
The following records are expected to be created/updated:
Account
Payment Instrument
Gift Commitment
Status = status field under the commitments object
Gift Commitment Schedule
Gift Default Designation
Gift Transaction
Gift Transaction Designation
Manage Gift Entry - Do not process a Gift Entry for a deceased Donor
When manually creating or updating a Gift Entry record,
If the Account record on the Donor field is a Person Account,
If the Person Account’s Deceased = TRUE,
When saving, an error message will display below the Donor field: You are not allowed to create or process a gift for a deceased donor.
If the Person Account’s Deceased = FALSE,
When saving, the Gift Entry record will be saved successfully
If the Account record on the Donor field is a Person Account,
When saving, the Gift Entry record will be saved successfully
When creating a Gift Entry record via the Manage Gift Entry page (New Entry button in the Gift Entry list view),
When searching for a donor in the Donor field,
The user can only search for donors who are not deceased (Person Account’s Deceased = FALSE)
If the donor searched is deceased (Person Account’s Deceased = TRUE),
An error message will display below the Barcode field: You are not allowed to create or process a gift for a deceased donor.
When creating a Gift Entry record via the Manage Gift Entry page (New Entry button in the Account record detail page),
If the current Account record is a Person Account,
If the Person Account’s Deceased = TRUE,
The Gift Entry page will NOT display
An error message will display: You are not allowed to create or process a gift for a deceased donor.
If the Person Account’s Deceased = FALSE,
The Gift Entry page will display
If the current Account record is NOT a Person Account,
The Gift Entry page will display
When creating a Gift Entry record via the Gift Batch (New Entry button in the Gift Batch record detail page),
When searching for a donor in the Donor field,
The user can only search for donors who are not deceased (Person Account’s Deceased = FALSE)
If the donor searched is deceased (Person Account’s Deceased = TRUE),
An error message will display below the Barcode field: You are not allowed to create or process a gift for a deceased donor.
When searching for a donor by providing a barcode in the Barcode field,
The user can only search for donors who are not deceased (Campaign Member → Contact’s Deceased = FALSE)
If the donor searched is deceased (Campaign Member → Contact’s Deceased = TRUE),
An error message will display below the Barcode field: You are not allowed to create or process a gift for a deceased donor.
Dynamic Criteria in Batch Management by using an Input Variable
The whole Scheduled Donation batch process is using a dynamic criteria for Payment Method and Status
Make sure that the Scheduled Donation batch process is working as expected and NO existing functionality will be broken
Scheduled Donation - Transaction Completion Date is populated even though the Status is still Processing
When processing payments via the Scheduled Donation batch job,
During the update of the Gift Transaction’s Status field from Unpaid to Processing, the Gift Transaction’s Transaction Completion Date field is EMPTY
The existing functionality is working as expected where an invoice is created and a payment is processed in Stripe and the equivalent records are created
Once the Gift Transaction record is paid, make sure that the Gift Transaction’s Transaction Completion Date field is populated based on the payment date
Review Code and Flows Referencing 'Check'
Make sure the org has PosiPay and PosiGive Installed and Configured.
Create a Bank Deposite Batch that has a payment method = Check or Cheque
( Dev ) All code and flows referencing ‘Check’ are updated where both ‘Check’ and ‘Cheque’ values are referenced
The process involving the check payment method should complete successfully.
Payment Ready - Include checking of Payment Instrument's Active checkbox
When a Gift Transaction record is created or updated,
The Payment Ready field is set to TRUE once it meets ALL of the following criteria:
The Transaction Due Date is lesser than or equal to TODAY
The Status is Unpaid
The Original Amount is NOT EMPTY
The Payment Instrument is NOT EMPTY
The Payment Instrument’s Flagged As Fraud is FALSE
The Payment Instrument’s Gateway Account is NOT empty
The Payment Instrument’s Gateway Account → Active is TRUE
The Payment Instrument’s Token is NOT empty
The Payment Instrument’s Active is TRUE
Enhance PosiGive Permission Sets
A read and edit field permission is added to Unrequire CVC in Batch Gift Entry field of the Gateway Account object
All permission sets of PosiGive has been checked if it has the necessary object and field permissions
Gift Transaction Payment Status
When processing a payment by using a dispute card number (4000000000002685) via the Manage Gift Entry page,
The payment will be processed first, but later on, the payment will be disputed
Assuming the webhook is configured properly:
A Gateway Event record is created for both processed payment and the dispute
A Gateway Transaction record is created for the actual processed payment (Record Type = Transaction)
A Gateway Transaction record is created as well for the dispute:
Record Type = Adjustment
Transaction Status = Dispute Under Review
The parent Gateway Transaction record is updated where:
Transaction Status = Dispute Under Review
The Gift Transaction’s Payment Status = Dispute Under Review
Manage Gift Entry - Payment Instrument Active Mapping
When creating a Gift Entry record via the Manage Gift Entry page (New Entry button in the Gift Entry list view),
If once-off donation (New Recurring Gift = FALSE) and the Payment Method = Credit Card OR BECS Debit,
The payment will be processed
A Payment Instrument record is created:
Active = FALSE
Other existing mapping will be applied
If recurring donation (New Recurring Gift = TRUE) and the Payment Method = Credit Card OR BECS Debit,
The Credit Card/BECS Debit details will be tokenised
A Payment Instrument record is created:
Active = TRUE
Token = Token (Stripe customer form)
Other existing mapping will be applied
When creating a Gift Entry record via the Manage Gift Entry page (New Entry button in the Account record detail page),
If once-off donation (New Recurring Gift = FALSE) and the Payment Method = Credit Card OR BECS Debit,
The payment will be processed
A Payment Instrument record is created:
Active = FALSE
Other existing mapping will be applied
If recurring donation (New Recurring Gift = TRUE) and the Payment Method = Credit Card OR BECS Debit,
The Credit Card/BECS Debit details will be tokenised
A Payment Instrument record is created:
Active = TRUE
Token = Token (Stripe customer form)
Other existing mapping will be applied
When creating and processing a Gift Entry record via the Gift Batch (New Entry button then Process Gift Batch button in the Gift Batch record detail page),
If once-off donation (New Recurring Gift = FALSE) and the Payment Method = Credit Card OR BECS Debit,
The Credit Card/BECS Debit details will be tokenised
A Payment Instrument record is created:
Active = TRUE
Other existing mapping will be applied
If recurring donation (New Recurring Gift = TRUE) and the Payment Method = Credit Card OR BECS Debit,
The Credit Card/BECS Debit details will be tokenised
A Payment Instrument record is created:
Active = TRUE
Other existing mapping will be applied
Edit Entry - Validate if Gift Entry's Gift Processing Status is Success
When updating a Gift Entry record via the Edit Entry button,
If the Gift Entry’s Gift Processing Status = Success,
The Gift Entry page is NOT displayed
An error message will display: You can’t edit this Gift Entry because the Gift Processing Status is Success.
If the Gift Entry’s Gift Processing Status != Success,
The Gift Entry page is displayed
The existing functionality will be followed where the Gift Entry record will be updated
Replace NPC's Existing Matched Payment Instrument with a New Payment Instrument
Single Gift Entry
Pre-work:
Process a once-off or recurring gift with a Payment Method of Credit Card and BECS Debit
Monitor the created Payment Instrument record, especially the value of the Token and Payment Method ID fields
When creating a Gift Entry record via the Manage Gift Entry page (New Entry button in the Gift Entry list view),
If the Payment Method = Credit Card,
Use the same donor and Credit Card details from the pre-work
After the Gift Entry process,
The necessary once-off or recurring gift records are created
A Payment Instrument record is created
The Payment Instrument record from the pre-work should not be updated, and the Token and Payment Method ID fields should not be overwritten
The Gift Transaction and/or Gift Commitment Schedule records are not using the Payment Instrument record from the pre-work BUT using the new Payment Instrument record
If the Payment Method = BECS Debit,
Use the same donor and BECS Debit details from the pre-work
After the Gift Entry process,
The necessary once-off or recurring gift records are created
A Payment Instrument record is created
The Payment Instrument record from the pre-work should not be updated, and the Token and Payment Method ID fields should not be overwritten
The Gift Transaction and/or Gift Commitment Schedule records are not using the Payment Instrument record from the pre-work BUT using the new Payment Instrument record
When creating a Gift Entry record via the Manage Gift Entry page (New Entry button in the Account record detail page),
If the Payment Method = Credit Card,
Use the same donor and Credit Card details from the pre-work
After the Gift Entry process,
The necessary once-off or recurring gift records are created
A Payment Instrument record is created
The Payment Instrument record from the pre-work should not be updated, and the Token and Payment Method ID fields should not be overwritten
The Gift Transaction and/or Gift Commitment Schedule records are not using the Payment Instrument record from the pre-work BUT using the new Payment Instrument record
If the Payment Method = BECS Debit,
Use the same donor and BECS Debit details from the pre-work
After the Gift Entry process,
The necessary once-off or recurring gift records are created
A Payment Instrument record is created
The Payment Instrument record from the pre-work should not be updated, and the Token and Payment Method ID fields should not be overwritten
The Gift Transaction and/or Gift Commitment Schedule records are not using the Payment Instrument record from the pre-work BUT using the new Payment Instrument record
Batch Gift Entry
1st: new payment details
When creating and processing a Gift Entry record via the Gift Batch (New Entry button then Process Gift Batch button in the Gift Batch record detail page),
For the Payment Method = Credit Card,
Create a Gift Entry record for once-off or recurring gift
Create another Gift Entry record for once-off or recurring gift and use the same donor and Credit Card details from the first Gift Entry record
After the Gift Entry process,
The necessary once-off or recurring gift records are created
A Payment Instrument record is created for each record
The two Gift Entry records are not sharing the same Payment Instrument record
For the Payment Method = BECS Debit,
Create a Gift Entry record for once-off or recurring gift
Create another Gift Entry record for once-off or recurring gift and use the same donor and BECS Debit details from the first Gift Entry record
After the Gift Entry process,
The necessary once-off or recurring gift records are created
A Payment Instrument record is created for each record
The two Gift Entry records are not sharing the same Payment Instrument record
2nd: existing payment details
Pre-work:
Process a once-off or recurring gift with a Payment Method of Credit Card and BECS Debit
Monitor the created Payment Instrument record, especially the value of the Token and Payment Method ID fields
When creating and processing a Gift Entry record via the Gift Batch (New Entry button then Process Gift Batch button in the Gift Batch record detail page),
If the Payment Method = Credit Card,
Use the same donor and Credit Card details from the pre-work
After the Gift Entry process,
The necessary once-off or recurring gift records are created
A Payment Instrument record is created
The Payment Instrument record from the pre-work should not be updated, and the Token and Payment Method ID fields should not be overwritten
The Gift Transaction and/or Gift Commitment Schedule records are not using the Payment Instrument record from the pre-work BUT using the new Payment Instrument record
If the Payment Method = BECS Debit,
Use the same donor and BECS Debit details from the pre-work
After the Gift Entry process,
The necessary once-off or recurring gift records are created
A Payment Instrument record is created
The Payment Instrument record from the pre-work should not be updated, and the Token and Payment Method ID fields should not be overwritten
The Gift Transaction and/or Gift Commitment Schedule records are not using the Payment Instrument record from the pre-work BUT using the new Payment Instrument record