/
2025 Q2 Posi Giving Release Notes

2025 Q2 Posi Giving Release Notes

ProntoGiving

2.217 (01/05/2025)

Required packages

ProntoPayments 2.85.121 or higher

Bug Fixes

  • Batch Get Payment Status-Direct Debit|Not SecurePay| Opportunity remains Pledged

    • When getting the Direct Debit transaction response from the Gateway via Get Payment Status whether scheduled/run now;

      • if the Payment Transaction’s → Gateway is not ‘SecurePay’ and its Payment Status is ‘Success’

        • the Opportunity linked to it will be updated to 'Closed Won'

      • if the Payment Transaction’s → Gateway is not ‘SecurePay’ and its Payment Status is ‘Failed’

        • the Opportunity linked to it will be updated to 'Closed Lost'

      • If the Payment Transaction’s → Gateway is ‘SecurePay’

        • the Payment Transaction’s → Payment Status is ‘Success’, and

          • the Opportunity linked to it remains on the ‘Pledged/Open’ Stage

  • BDE Templates | Set Required Fields has too much gap when selecting fields

    • When selecting a set of required fields,

      • There’s no gap in each selected field

  • Batch Donation Entry | issue with the Close Button

    • The process of creating a new batch should be exited immediately when the Close button is clicked

    • This issue is now fixed.

2.218 (30/05/2025)

Required packages

ProntoPayments 2.85.121 or higher

Fixes

Upgrade the API Version for Visualforce Components

  • All visualforce components with an API Version lower than 45.0 are upgraded to version 60.0

ProntoEngage

2.22 (30/05/2025)

Fixes

Upgrade the API Version for Visualforce Components

  • All visualforce components with an API Version lower than 45.0 are upgraded to version 60.0

ProntoPlus

2.101 (01/05/2025)

Upgrade Risk

  • For installation or upgrade to version 2.57 or higher, please make sure to reschedule the receipting batches  

    • Send Receipts  

    • Generate Receipts 

  • For installation or upgrade to version 2.94 or higher, do this configuration

Bug Fixes

  • Receipt Number is Empty when Generating Receipt

    • When a user tries to generate a receipt using the Generate Receipt Copy (PPlus),

      • If Receipt Number is empty and the field is existing, and Receipt Number (PPlus) is not empty

        • a new receipt will be generated successfully where the receipt number is Receipt Number (PPlus)

    • When a user generating a receipt via schedule Generate Receipt batch;

      • If Receipt Number is empty and the field is existing, and Receipt Number (PPlus) is not empty

        • a new receipt will be generated successfully where the receipt number is Receipt Number (PPlus)

2.102 (30/05/2025)

Upgrade Risk

  • For installation or upgrade to version 2.57 or higher, please make sure to reschedule the receipting batches  

    • Send Receipts  

    • Generate Receipts 

  • For installation or upgrade to version 2.94 or higher, do this configuration

Fixes

Upgrade the API Version for Visualforce Components

  • All visualforce components with an API Version lower than 45.0 are upgraded to version 60.0

2.103 - 2.104 (24/06/2025)

Important Notice:

  • Aside from excluding ActionCadenceState field in generating consolidated statement that might cause the error in Apex Jobs, we also fix an error in version 2.105 where we also exclude SourceSystemIdentifier field.

Upgrade Risk

  • For installation or upgrade to version 2.57 or higher, please make sure to reschedule the receipting batches  

    • Send Receipts  

    • Generate Receipts 

  • For installation or upgrade to version 2.94 or higher, do this configuration

Fixes

Generate Consolidated Statement - Exclude 'ActionCadenceState' Field in Contact Query

  • When generating a consolidated statement via the Generate Consolidated Statement (PPlus) button on the Contact or Account record,

    • A Consolidated Statements (PPlus) record is created and linked to the Contact or Account record

    • A receipt file is generated successfully

  • NOTE: ActionCadenceState field will available when the Sales Engagement license is enabled. To see this field, the user also needs the Sales Engagement User or Sales Engagement Quick Cadence Creator user permission set. For reference: https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_contact.htm

2.105 (25/06/2025)

  • For installation or upgrade to version 2.57 or higher, please make sure to reschedule the receipting batches  

    • Send Receipts  

    • Generate Receipts 

  • For installation or upgrade to version 2.94 or higher, do this configuration

Fixes

  • Exclude SourceSystemIdentifier Field in Account Query when generating Consolidated Statement