2.85.122 - 2.85.123 ProntoPayments v2
Release Date: 10/09/2024
URL: /packaging/installPackage.apexp?p0=04tIU000001EBct
Upgrade Risks
When upgrading to version 2.71 or higher, make sure to re-save existing gateway records to have the password field encrypted .
Enhancement
Delete ASPP Logs from Failed Payment Transaction in Batch Delete ProntoPayments Logs
When deleting the old ASPP Log records via the Batch Delete ProntoPayments Logs from the ProntoPayments Settings → Scheduler,
The ASPP Log records of an Opportunity record are deleted where:
ASPP Log’s Created Date is N months ago (N = ProntoPayments Settings custom setting’s PPLogs Default Date Range OR 3)
ASPP Log → Opportunity’s Stage = Closed Won OR Closed Lost
ASPP Log → Opportunity’s SYSPPLogs = TRUE
ASPP Log → Opportunity’s SYSDeletedPPlogs = FALSE
The ASPP Log records of a PPayment record are deleted where:
ASPP Log’s Created Date is N months ago (N = ProntoPayments Settings custom setting’s PPLogs Default Date Range OR 3)
ASPP Log → PPayment’s Payment Status = Success OR Failed
ASPP Log → PPayment’s SYSPPLogs = TRUE
ASPP Log → PPayment’s SYSDeletedPPlogs = FALSE
The ASPP Log records of a Payment Transaction record are deleted where:
ASPP Log’s Created Date is N months ago (N = ProntoPayments Settings custom setting’s PPLogs Default Date Range OR 3)
ASPP Log → Payment Transaction’s Payment Status = Success OR Failed
Manual Closing of PP Payment Batch - Follow Gateway's Default Stage for Opportunity Stage
When manually closing a PP Payment Batch record by updating the Batch Status to Closed,
The PP Payment Batch record is updated where:
Batch Status = Closing
After the PP Payment Batch record is successfully closed,
The PP Payment Batch record is updated where:
Batch Status = Closed
The Opportunity records linked to the PP Payment Batch record are updated where:
Stage = PP Payment Batch’s Gateway → Default Stage for Successfully Processed
Bug Fix
Payment Source was not created due to an error message
Generating Payment Source through WFC/PPAPI failed due to a gateway error message from ProntoPayments
This issue is now fixed