...
B. Click “Execute” button.
...
Step 4: Confirm the created schedule in the Scheduled Jobs. Go to Setup | Schedule Jobs
...
This batch will update transactions where gateway is either BPOINT or Ezidebit. This will retrieve settlement dates from the gateway (when available).
Batches | Batch Class Name | Descriptions | Default Scheduled Hour | Set To Scheduled |
Batch Payment Processing | ASPP_AuthBatch |
| Every 12midnight | TRUE |
Batch EziDebit Get Payment Status | BatchGetPaymentsStatusEziDebit | This is for Ezidebit transactions only. This will update the statuses of those pending transactions based on the gateway response and opportunity stages. | Default scheduled every 6am | TRUE |
Batch Attach ProntoPayments Logs | ASPP__ProcessingOpportunityAttachPPLogs | This will create a backup for old ASPP Logs so that when Batch Delete ProntoPayments Logs is scheduled, we can still those records as csv file. | Default scheduled every 8pm |
|
Batch Delete Temporary Payment Source | ASPP__ProcessingBatchDeleteTemporaryPS |
| Default scheduled every 8pm |
|
Batch Send Email for Expired Cards | ASPP__BatchExpiredCardsEmailNotification | This will send an email notification to the running user. The email contains a list of payment sources records. (OPTIONAL - client preference) - Consider deprecation - replace with subscribing to report |
|
|
Batch Get Payments | ASPP__BatchGetPayments | Sync payments from gateway to salesforce. Below are the supported gateways. (OPTIONAL - client preference) Paydock Ezidebit eWAy Paypal Rest PIN Stripe DebitSuccess |
| TRUE |
Batch Get Tokens | ASPP__BatchGetTokens | Sync tokens (as payment sources) from gateway to salesforce. (OPTIONAL - client preference) |
| TRUE |
Batch Inactive Expired Payment Source | ASPP__BatchInactiveExpiredPaymentSource | All expired payment sources, both tokenisation-credit card and credit card, will be updated to inactive ONLY if expiry date is not empty. (OPTIONAL - client preference) |
|
|
Batch Delete ProntoPayments Logs | ASPP__BatchProcessedPayment__DeleteLogs | (OPTIONAL - client preference) |
|
|
Batch Get Subscriptions | ASPP__BatchGetSubscriptions | Sync subscriptions from gateway to salesforce. (OPTIONAL - client preference) |
| TRUE |
Batch Create Subscription PPayment | ASPP__BatchCreateSubscriptionPPayment | Will retrieve transactions from the gateway only if subscription is processed on the gateway (not on salesforce). (OPTIONAL - client preference) |
| TRUE |
Batch Payment Status Update |
|
|
| FALSE - No need to run the batch as it is already included in Payment Processing chain. |
Get Payment Transaction Settlement | UpdateSettlementDateBatch | This batch will update transactions where gateway is either BPOINT or Ezidebit. This will retrieve settlement dates from the gateway (when available) | Scheduled every 6am | TRUE |
Batch Generate CRN for Contact | GenerateCRNforContactBatch | Necessary when Ezidebit BPAY is used. | Scheduled every 7pm | FALSE - pending functionality |
ProntoGiving
Go to ProntoGiving Settings | Schedule Process | Settings
BDE Item processing will only process standard objects; custom objects are not supported.
ProntoGiving - Other Batches
...
What the batch does, for all retrieved ASPHPPADDON__BDE_Item__c records: Process these records, just like processing BDE Items via list view.
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 with lookup to Opportunities that are Closed/Won with CreatedDate <LAST_N_DAYS> (settings) It remove records because they’re no longer significant. |
| TRUE |
Delete Bulk Donation Logs |
|
|
| FALSE - Not in use object |
Process BDE Items | ASPHPPADDON__BDE_Item__c | Processing BDE Items via list view Query all BDE Items with Processing Status “Pending Processing” and process these records | Every 6pm | TRUE |
Recurring Donations – ProntoGiving
...
IE: updates donation back to active 30 days prior to next donation date.
Batches | Batch Class Name | Descriptions | Default Scheduled Hour |
|
Recurring Donations Monitoring | BatchUpdateRecurringFields |
| Every Hour |
|
Update Paused Donations due to Restart |
|
|
| TRUE |
Update Number Of Failed Recurring Donations Number of Fails before Cancelling Recurring Donation | BatchUpdateNumberOfFailedRD | · Query all non-closed RDs and counts the number of (latest) consecutive closed lost opportunities. · 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” | Every Midnight | TRUE |
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 | TRUE |
ProntoPlus
Go to ProntoPlus Settings | Schedule Processes
Batches | Batch Class Name | Descriptions | Default Scheduled Hour | Set To Scheduled |
Send Receipts | RCT__BatchSendReceipts | · Query all Opportunities with Receipt Action Default and update to Email or Post. From Opportunities with receipt action Email it generate receipts of the opportunity without the Last Receipt populated. · BDE Receipt Action Email it will be receipted every 10mins | Every 10 mins | TRUE |
Generate Receipts | RCT__BatchGenerateReceipt | List view from the Opportunity level without the Last Receipt populated for Post. |
| TRUE - if the PPL version is 2.57 or higher. FALSE - if the PPL version 2.56 or below |