...
Trigger Handler Name | Object | Class | Load Order | Trigger Action | Asynchronous After Events | Purpose |
|---|---|---|---|---|---|---|
PGIV_ASPaymentRefund_TDTM | ASPHPP__ASPayment_Refund__c | ASPHPPADDON.PGIV_ASPaymentRefund_TDTM | 1 | AfterInsert; AfterUpdate | Holds the process for the refunding of a payment It will create a Negative GAU record | |
PP_ASPaymentTXN_TDTM | ASPHPP__ASPayment_TXN__c | ASPHPPADDON.ProntoPayments_ASPaymentTXN_TDTM | 1 | BeforeInsert; BeforeUpdate; AfterInsert; AfterUpdate | If Asynchronous is true cannot process payment. | After creating/updating the Opportunity record, the Last Payment Transaction field will be populated based on the Payment Transaction of the Opportunity After refunding a payment in Payment Transaction record, the negative Payment Transaction record is populated based on the values from the Payment Refund |
PGIV_RecurringDonation_TDTM | npe03__Recurring_Donation__c | ASPHPPADDON.PGIV_RecurringDonation_TDTM | 3 | BeforeInsert; BeforeUpdate; AfterInsert | Set the important info of Recurring Donation before insert/update of Recurring Donation record Create Recurring Donation Action records for newly created Recurring Donations | |
PP_Opportunity_TDTM | Opportunity | ASPHPPADDON.ProntoPayments_Opportunity_TDTM | 5 | BeforeInsert; BeforeUpdate; BeforeDelete; AfterInsert; AfterUpdate; AfterDelete | Validates the Opportunity record before updating if “Allow Opportunity Update even Stage Name is Closed Won” is FALSE e.g. Not allowed to update the Opportunity Amount, this opportunity is already Closed Won Validate the Opportunity record when deleting the record if it has Pending or Success Payment Transaction Automatically creates Payment Transaction when the Opportunity’s Do Not Automatically Create Payment is FALSE | |
PGIV_Opportunity_TDTM | Opportunity | ASPHPPADDON.PGIV_Opportunity_TDTM | 6 | BeforeInsert; BeforeUpdate; AfterInsert; AfterUpdate | Sets Receipt Number after an Opportunity record is saved Send Receipts for the list of Opportunities Logs the Payment Source update from the Opportunity |
Default Batches to Run
Go to ProntoGiving Settings | Schedule Process | Settings+ProntoGiving - Other
Batches |
|---|
...
Batches
...
Batch Class Name | Descriptions | Default Scheduled Hour | |
|---|---|---|---|
Delete |
...
Donation Page Error Logs | ASPHPPADDON__Donation_Page_Error_ |
...
Log__c | Donation Page Error |
...
Logs records are created if errors are encountered in Donation Page/Forms. All Donation Page |
...
Error_Logs |
...
Recurring Donations - ProntoGiving
+ProntoGiving - RD Batches
with lookup to |
...
Opportunities that are Closed/Won with CreatedDate <LAST_N_ |
...
DAYS> (settings) It remove records because they’re no longer significant. | ||
Process BDE Items | ASPHPPADDON__BDE_Item__c | Processing BDE Items |
...
via list view Query all |
...
BDE Items with Processing Status “Pending Processing” | Every 6pm |
Recurring Donations
Batches | Batch Class Name | Descriptions |
|---|
...
Default Scheduled Hour | |
|---|---|
Recurring Donations Monitoring | BatchUpdateRecurringFields |
...
Every Hour |
...
Update Number Of Failed Recurring Donations | BatchUpdateNumberOfFailedRD | Query all non-closed |
...
RDs and counts the number of (latest) consecutive closed lost |
...
opportunities. |
Update Number Of Failed Recurring Donations
Every Midnight |
Close Open Recurring Donations with Contact Flagged as Deceased |
...
BatchCloseOpenRDWithDeceasedContact | Query all non-closed |
...
RDs with Contact npsp__ |
...
Deceased__c == |
...
TRUE Open-Ended Status = |
...
Closed Status = |
...
Cancelled | Every Midnight | |
Number of Fails before Cancelling Recurring Donation | Based on “Number of |
...
Failed Recurring Donations” field on RD record, if the field matches the set limit in ProntoGiving Settings, RD Status is updated to “Cancelled”, thus Open-Ended Status |
...
is updated to “Closed” | |
Update Paused Donation-s due to Restart |
Post-Config per Release
+ProntoGiving 2.22 - Post Config Guide
+ProntoGiving 2.24 - Post Config Guide
+ProntoGiving Version 2: Update Opportunity Stages via ProntoGiving (Post Config Guide)
Archives
Gather all data that will be archive per changes for documentation purposes only.
+Archive History Prontos
ProntoGiving Version 2: Update Opportunity Stages via ProntoGiving (Post Config Guide)
This config is for ProntoGiving to update Opportunities instead of ProntoPayments.
Set Use ProntoPayments to Update Opportunity
In Custom Settings > ProntoPayments Settings, set Use ProntoPayments to Update Opportunity to FALSE.
Set Update Opportunities in the last n days
In ProntoGiving Settings, provide the Update Opportunities in the last n days. This field indicates the date range of the opportunities to be updated to Closed Won/Lost. If not provided, query will then be Close Date For All Time.
Remove old Update Opportunity Stage schedules
This is now removed because this process is called every time payment processing runs.
Setup Retry Function
Check if these toggles are enabled,
o ProntoPayments Settings>Set n as the maximum Donation Retries for bank
transactions
o ProntoPayments Settings>Set as the maximum Donation Retries for credit card
transactions
Update Logs:
...