/
PosiGive v1.1 - 1.3 - MAY 28, 2025

PosiGive v1.1 - 1.3 - MAY 28, 2025

Package URL: /packaging/installPackage.apexp?p0=04tOZ00000046jZYAQ

Post Config

  • Deploy/push the post-config folder in this version

  • Delete the following custom fields if your organization has them. If they do not exist, no action is required:

    • External Invoice ID (API Name: ExternalInvoiceID__c) on the Gateway Invoice object

    • Transaction Reference ID (API Name: TransactionReferenceID__c) on the Gift Transaction object

  • Delete the Gift Entry Mapping custom metadata type record on the Gift Entry Mapping custom metadata type with the following details,

    • Source API Name Field = Gift Entry’s Payment Identifier 

    • Target API Name Field = Gift Transaction’s Transaction Reference ID (custom field) 

    • Target API Name Object = Gift Transaction

What’s New

  • When processing a one-off credit card payment via a Gift Batch, the Token field in the associated Payment Instrument will be populated automatically.

  • When a Recurring Gift Entry is created via Single Gift Entry, its processing behavior depends on the Process First Payment Immediately option:

    • If Process First Payment Immediately is set to FALSE, the entry will not be processed immediately. Instead, it will be tokenized, and the associated Gift Transaction will be deferred. At this stage, the Stripe Customer form will be displayed to complete the setup process.

    • If Process First Payment Immediately is set to TRUE, the first payment of the recurring donation will be processed immediately upon entry creation.

  • The Gift Entry flow has been updated as follows:

    • In the Batch Gift Entry process, when New Recurring Gift is set to FALSE, the Set Designation Information section will be displayed regardless of the selected Payment Method. Additionally, the referenced designation component from NPC will also be shown.

    • Gift Entry now displays 3 columns.

      image-20250526-063334.png

    • The Gift Entry flow has been enhanced for both Single and Batch Gift Entry processes. When the Payment Method is set to Direct Deposit, the behavior of the Payment Identifier field is updated as follows:

      • If the Campaign Member Matching Fields in the PosiGive Settings custom setting is empty, the system will default to using the Campaign Member's Barcode field as the filter criteria.

      • If the Campaign Member Matching Fields setting is populated, the existing functionality will be maintained, using the specified Campaign Member field API Name as the filter criteria.

    • When running the subflow for the Process Gift Entry—whether for once-off or recurring gifts—the existing functionality will be followed, where each Gift Entry record is processed accordingly.
      Ensure that all Gift Entry records, regardless of the Payment Method, are properly handled. Once a Gift Entry record is processed, the necessary related records will be created based on whether it is a once-off or recurring gift.
      For any Gift Transaction record using payment methods other than Credit Card or BECS Debit, the Transaction Due Date will be left blank, while the Transaction Completion Date will be filled in using the Gift Received Date from the Gift Entry. Additionally, ensure that all created records have the correct field mappings, including the Payment Identifier mapping.

  • As part of the Gateway Invoice’s Change Data Capture (CDC) event, when linking a Gateway Transaction record to a Gateway Invoice record, use the Gateway Transaction’s Transaction Reference ID and the Gateway Invoice’s External Invoice ID external fields as a secondary matching option.

  • Gift Batch Layout has been renamed to [PosiGive] Gift Batch Layout.

  • [PosiGive] The “New Entry” button has been renamed to “New Gift”.