Hide Unused/Deprecated Components
Navigate to Setup | Users | Choose Profile. (Note: Do to all Profiles or a specific profile
that you want to hide those tabs)
Click Edit
Go to Tab Settings section and hide the following tabs if visible:
DEPRECATED - BDE Wizard 2.0
DEPRECATED-ProntoPayments Settings
DEPRECATED - Bulk Donation Templates
Deprecated ProntoPayments Settings
DEPRECATED - ProntoGiving Settings2
DEPRECATED-Manage ABA Files
Bulk Donation Entry Wizard v1.0
Bulk Donations (v1.0)
Receipt Templates
Consolidated Statements
Consolidated Statements Settings
Quick Donate 1
Batch Data Entry
Quick Donate
Setup Process Type for Payment Transaction
Go to Setup | Object Manager | Payment Transactions | Fields & Relationships | Process Type
Make sure that the Manual Payment and Via ProntoPayments are active in the picklist values section.
Setup Field Dependencies on Process Type
Go to Setup | Object Manager | Payment Transactions | Fields & Relationships | Process Type
Edit the Field Dependencies
Under Manual Payment select:
Cash
Cheque
Bank Account
Credit Card
Under Via ProntoPayments select:
Bank Account
Credit Card
Enable the Manual Payment record type
Go to Setup | Object Manager | Payment Transaction | Record Types | Manual Payment | Edit
Setup Cash record type
Process Type
Go to Setup | Object Manager | Payment Transactions | Record Types | Cash | Process Type → Edit
Ensure Manual Payment and Via ProntoPayments are in the Selected Values column
Payment Type
Ensure all values are in the Selected Values column
Go to Setup | Object Manager | Payment Transactions | Record Types | Cash | Edit Payment Type
Card Expiry Month
Ensure all values are in the Selected Values column
Go to Setup | Object Manager | Payment Transactions | Record Types | Cash | Edit Card Expiry Month
CardType
Ensure all values are in the Selected Values column
Go to Setup | Object Manager | Payment Transactions | Record Types | Cash | Edit Card Type
Payment Status
Ensure all values are in the Selected Values column
Go to Setup | Object Manager | Payment Transactions | Record Types | Cash | Edit Payment Status
Setup Manual Payment record type
Follow the same steps as Cash record type
Setup Field Sets
This section uses the Field Sets section found under Setup | Object Manager | Opportunity. For each field set type, select Edit and display the following fields:
One-Off Donation
Close Date
Lead Source
Stage
Primary Campaign Source
Receipt Action (PPlus)
Receipt Template (PPlus)
Recurring Donation
Schedule Type
Campaign
Installment Period
Installments
Date Established
Lead Source
Always use last day of month
Exclude in RD Monitoring
Receipt Action (PPlus)
Receipt Template (PPlus)
QD New Contact Fieldset
First Name
Last Name
Email
Work Email
Personal Email
Alternate Email
Receipt Email (PPlus)
Receipt Action Preference (PPlus)
QD Existing Contact
First Name
Last Name
Mailing Street
Mailing City
Mailing Country
Mailing State/Province
Mailing Zip/Postal Code
Phone
Email
Work Email
Personal Email
Alternate Email
Receipt Email (PPlus)
Receipt Action Preference (PPlus)
QD New Account Fieldset
Receipt Recipient (PPlus)
QD Existing Account Fieldset
Billing Street
Billing City
Billing State/Province
Billing Zip/Postal Code
Billing Country
Receipt Recipient (PPlus)
QD Credit Card Fields (This is only optional because not all gateways require CCV field)
Add CCV (PPlus) field
Additional Information for Quick Donate
If Account is existing/new and the Donation Type is equal to Household or Organisation, the account should have Primary Contact or Receipt Recipient (PPlus) as the value.
If Contact is existing/new and the Donation Type is equal to Individual, the contact should have Receipt Email (PPlus) as the value.
Setup Default Values
Set the default values in your Quick Donate Page.
Go to ProntoGiving Settings | Donation | Quick Donate. These will be set by the client
Setup Sales Process
Go to Setup | Feature Settings | Sales | Sales Process
Ensure that the Pledged or Prospecting stage is selected in your active Sales
Processes
Set Default Record Type to Cash
Go to Setup | Profile | System Admin | Object Settings | Payment Transactions
Set the default record type to Cash.
Donation Fields Mapping
Donation Fields Mapping is a mapping to use for Quick Donate and Batch Donation Entry.
Go to ProntoGiving Settings | Donation Fields Mapping.
Create new mapping by clicking the New button.
Add the mapping below
Donation Type (PPlus)
Receipt Action (PPlus) - for clients that use Wordpress in their Donation Form.
Barcode
Go to ProntoGiving Settings | Donation | Settings | Barcode
Enable the barcode. Once enabled, the barcode field will display in the Quick Donate and Batch Donation Entries page.
Unique ID Campaign Member Field Name - It will recognised the campaign based on what was being setup in the BDE Template. a. Scenario: If the user chooses Barcode Number field the workaround will be; In order to recognise all campaigns with its campaign member barcodes, untick the Campaign as required and remove the campaign from the default list in all templates
Unique ID Account Field Name - scans a matching value on the field specified for Account
Unique ID Contact Field Name - scans a matching value on the field specified for Contact
Unique ID Recurring Donation Field Name - scans a matching value on the field specified for Recurring Donation.
Access permissions
Set these permissions for users to access Quick Donate.
Object | Object Permission | Field Permission | Read Access | Edit Access |
Accounts | Read, Create | Billing Address Receipt Recipient (PPlus) | TRUE | TRUE |
Campaigns | Read, View All | |||
Contacts | Read, Create | Alternate Email Mailing Address Personal Email Receipt Action Preferences (PPlus) Receipt Email (PPlus), Work Email | TRUE | TRUE |
Gateways | Read | |||
GAU Allocations | Read, Create | Amount Percent | TRUE | TRUE |
General Accounting Units | Read | |||
Opportunities | Read, Create | Lead Source Receipt Action (PPlus) Receipt Template (PPlus) | TRUE | TRUE |
Payment Sources | Read, Create | All fields | TRUE | TRUE |
Payments | Read | All fields | TRUE | |
Payment Transactions | Read, Create | All fields | TRUE | TRUE |
Receipt Template (PPlus) | Read | All fields | ||
Recurring Donations | Read, Create | Always use last day of month Campaign Date Established Department Exclude in RD Monitoring Installment Period Lead Source Number of Planned Installments Open Ended Status Receipt Action (PPlus) Receipt Template (PPlus) Schedule Type | TRUE | TRUE |
Visualforce Page access | ASPHPPADDON.QuickDonate2 |
ProntoGiving Settings
Setup Opportunity Stages
a. Go to ProntoGiving Settings | Donation | Stage and set according to the client requirements
Setup Settings
Go to ProntoGiving Settings | Donation | Settings and make changes to the following according to the client requirements:
Enable Default Campaign
Anonymous Contact
One-Off Record Type.
Recurring Donations
Go to ProntoGiving Settings | Recurring Donations | Recurring Donation Naming
Setup Recurring Donation Naming.
Setup Update Payment Sources
NPSP Phone and Email Work Flow
These Phone and Email Work Flow Rules should be turned on by default.
Email Workflow Rule
Contact.EmailChanged_Alternate
Contact.EmailChanged_Personal
Contact.EmailChanged_Work
Contact.Preferred_Email__c
Email only: Paste to Work
Phone Workflow Rule
Contact.PhoneChanged_Home
Contact.PhoneChanged_Mobile
Contact.PhoneChanged_Other
Contact.PhoneChanged_Work
Contact.Preferred_Phone__c
Phone only: Paste to Work
Go to Setup > Workflow Rules. Click Activate the workflow rule’s name.
Remote Site Setup
Update Remote Site - Metadata
Setup Remote Site Settings
Switch to Classic Environment
Go to ProntoGiving Settings and copy the highlighted link below.
Note: Every org has a different URL
Go to Setup > Security > Remote Site Settings. Update Metadata Remote Site
Make sure that the “Active” checkbox is ticked and save when done.
Trigger Handlers
Note: Ensure these triggers are added and activated. Adjust the load order accordingly if the client is not using the other features.
Go to App Launcher | Trigger Handler
The PP_ASPaymentTXN_TDTM trigger handler requires ProntoPayments version 2.7 or
higher
Add the PP_Opportunity_TDTM trigger handler if:
The org has NPSP installed, if none, don’t add
Once the trigger is added, enable the NPSP TDTM toggle in ProntoPayments Settings
Load Order should be ProntoPayments, ProntoGiving, ProntoPlus and org customisation for every object.
Please note: all triggers should be Active.
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 | Yes | 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
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. | |
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. | 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 |
Update Opportunity Stages via ProntoGiving
This config is for ProntoGiving to update Opportunities instead of ProntoPayments.
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
BDE
Ensure Type field picklist values are: Offline Donation, Direct Debit and Credit Card.
Go to Setup > Object Manager > BDE Templates > Fields & Relationships > Type. Picklist values should only be Offline Donation, Direct Debit and Credit Card.
Set Approval Process (If the client org opt to use Approval)
Enable record locking and unlocking in Apex.
a. Go to Setup > Process Automation > Process Automation Settings.
Create Approval Process
Go to Setup > Process Automation > Approval Process.
Create new Approval Process for
Batch Donation Entry (if not yet created).
In
Manage Approval Process For picklist, select the Batch Donation Entry and select the Use Standard Setup Wizard option.
Process Name should be “Batch Donation Entry Approval Process”. Click Next to proceed.
Under the
Use this approval process of the following picklist select “formula evaluates to true” and copy the formula below. Click Next to proceed.
Formula:
AND($Setup.ASPHPPADDON__ProntoGiving_Settings__c.ASPHPPADDON__Use_Approval_Process_for_Batches__c = true, NOT(ISPICKVAL(ASPHPPADDON__Bulk_Donation_Status__c, 'Processed')), NOT(ISPICKVAL(ASPHPPADDON__Bulk_Donation_Status__c, 'Done')), NOT(ISPICKVAL(ASPHPPADDON__Bulk_Donation_Status__c, 'Approved')) )
In the
Record Editability Properties section, choose the “Admins ONLY can edit records during the approval process”. Click Next to proceed.
Choose the
BDE Approval Process Template (BDE 2.0). Click Next to proceed.
Choose the fields to display in the Approval Request page. Click
Next to proceed.
Select
Record Creator as the "Allowed Submitters”. Click Save to finish.
10. After saving, you will be redirected in this page.
11. Create Initial Submission Actions for Update Batch Status Awaiting Approval.
a. Click the “Add Existing” button and select “Field Update”.
12. Create Approval Steps
a. Click the “New Approval Step” button.
. b. Enter Name and Description, click next.
Name | Unique Name |
Step 1: User Approval | Step_1_User_Approval |
. c. Specify Step Criteria
. Select “Enter this step if the following” criteria are met, else reject record and copy the values below.
Field | Operator | Value |
Batch Donation Entry: Bulk Donation Status | equals | To Be Processed,Awaiting Approval |
. d. Select Approver step.
. e. Click Save when done.
.
13. Create Final Approval Actions - for Update Batch Status Approved.
a. Click the “Add Existing” button and select “Field Update” .
14. Create Final Rejection Actions - for Update Batch Status To Be Processed.
a. Click the “Add Existing” button and select “Field Update”.
15. After completing the setup. Click the “Activate” button to activate the Approval Process.
Enable Approval Process in ProntoGiving Settings
Enabling the Approval Process toggle will prevent the Batch Donation Entry records without approval to proceed. This will help the Admin to receive an “Approval Request” and approve or reject the BDE records. Only those Approved BDE records will be processed.
Navigate to ProntoGiving Settings > Batch Donation Entry > BDE 2.0 > Settings > Use Approval Process for Batch Donation Entries.
Enabling the toggle will allow processing of Batch Donation Entry records if status is marked as “Approved” only.
If the toggle is enabled (ASPHPPADDON__Use_Approval_Process_for_Batches__c = true), the user needs to click the Submit for Approval button to get approval before processing the BDE record, or else an error notification message will pop-up that the criteria is not met, because it is not yet approved. Only “Approved” BDE status will be processed.
Disabling the toggle will allow processing of Batch Donation Entry records even though the status is “To Be Processed”.
If the toggle is disabled (ASPHPPADDON__Use_Approval_Process_for_Batches__c = false), the user can process the BDE record bypassing the Approval stage by clicking directly the Process Batch button.
BDE Components
Setup Settings
Go to Setup | Session Settings | Enable Content Delivery Network (CDN) = tick
User Interface
If some of the components in the Batch Donation Entries are not showing, you can show them by following these steps.
Go to Batch Donation Entries tab.
Select any records in the list.
Click the settings icon and select “Edit Page” option.
It will redirect to another page. Then, you can see the
Lightning Components that are available to use.
To find the components that you want to show, just search it in the
Search Components field.
Components that needs to be shown in the Batch Donation Entries tab are:
a. New BDE Item Form
b. BDE Items Summary
. c. BDE Items Related List
Search for the components in the search bar and drag it in the center.
Click the Save button when done.
Show BDE Barcode Field in BDE UI
The BDE Barcode will only visible if the toggle is enabled in the settings. Go to ProntoGiving Settings | Donation | Settings | Barcode
a. Enable the toggle
Required Custom Fields
Please create the following fields under the BDE Item object before creating the BDE Templates and Item Record Mapping.
Field Label | Field API Name | Data Type |
BSB | Cheque_Bank_Number_BSB__c | Text(80) |
Cheque Account Number | Cheque_Account_Number__c | Text(80) |
Cheque Bank Name | Cheque_Bank_Name__c | Text(255) |
Cheque Date | Cheque_Date__c | Date |
Cheque Drawers Name | Cheque_Drawers_Name__c | Text Area(255) |
Cheque Number | Cheque_Number__c | Text(80) |
Cheque Transit Number | Cheque_Transit_Number__c | Text(80) |
Description | Description__c | Long Text Area(32000) |
Payment ID | Payment_ID__c | Text(80) |
Payment Type | Payment_Type__c | Picklist · Cash · Cheque · Credit Card · Tokenisation · Bank Account · Direct Deposit |
Payment Type 2 | Payment_Type_2__c | Picklist · Cash · Cheque · Credit Card · BPay · eWallet · Direct Deposit |
Receipt Actionhttps://ap16.lightning.force.com/lightning/setup/ObjectManager/01I2w000000MmGZ/FieldsAndRelationships/00N2w000005z85C/view(PPlus) | Receipt_Action__c | Picklist · Default · Post · Do Not Receipt |
Receipt Templatehttps://ap16.lightning.force.com/lightning/setup/ObjectManager/01I2w000000MmGZ/FieldsAndRelationships/00N2w000005z85H/view(PPlus) | Receipt_Template__c | Lookup(Receipt Template (PPlus)) |
Billing State | Billing_State__c | Text(80) |
Billing Country | Billing_Country__c | Text(25) |
Billing Street | Billing_Street__c | Text(80) |
Billing City | Billing_City__c | Text(80) |
Billing Postal Code | Billing_Postal_Code__c | Text(18) |
Open Ended Status | Open_Ended_Status__c | Picklist · Open · None |
Add the following fields if not yet added/deprecated.
Object | Field Label | Field API Name | Data Type |
Opportunity | Soft Credit Contact | Soft_Credit_Contact__c | (contact lookup) |
Opportunity | Soft Credit Account | Soft_Credit_Account__c | (account lookup) |
Recurring Donation | Soft Credit Contact | Soft_Credit_Contact__c | (contact lookup) |
Recurring Donation | Soft Credit Account | Soft_Credit_Account__c | (account lookup) |
BDE Item Fields to be Manually Deleted
Object | Field Label | Field API Name | Data Type |
BDE Item | Create BDE Item Only | Create_BDE_Item_Only__c | Checkbox |
BDE Item | RD Status | Revised_RD_Status__c | Picklist |
BDE Item | Next Donation | Revised_Next_Donation_Date__c | Date |
BDE Item | Revised Frequency | Revised_Frequency__c | Picklist |
BDE Item | Revised Campaign | Revised_Campaign__c | Lookup(Campaign) |
BDE Item | Revised Amount | Revised_Amount__c | Currency |
BDE Item | RDA Comments | RDA_Comments__c | Long Text Area |
BDE Item | ASPHPPADDON__Cheque_Account_Number__c | Text(80) | |
BDE Item | ASPHPPADDON__Cheque_Account_Number_2__c | Text(80) | |
BDE Item | ASPHPPADDON__Cheque_Bank_Name__c | Text(255) | |
BDE Item | ASPHPPADDON__Cheque_Date__c | Date | |
BDE Item | ASPHPPADDON__Cheque_Drawers_Name__c | Text Area(255) | |
BDE Item | ASPHPPADDON__Cheque_Number__c | Text(80) | |
BDE Item | ASPHPPADDON__Cheque_Transit_Number__c | Text(80) |
Batch Donation Entry Balancing
Go to ProntoGiving Settings > Batch Donation Entry > BDE 2.0 > Settings User Interface, on the “Batch Donation Entry Total Match Default” field click the dropdown besides to select “Unchecked”, “Checked”, and “Checked and Locked” then click “Save”.
· If Unchecked - The Require Expected Total Match checkbox is unchecked and editable.
· If Checked - The Require Expected Total Match checkbox is checked and editable.
· If Checked and Locked - The Require Expected Total Match checkbox is checked and this field is read-only.
BDE Settings
On the Batch Donation Entry > BDE 2.0 > Settings,
· if the “Use Approval Processs for Batch Donation Entries” toggle is Enabled, it requires that the Batch Donation Entry needs an approval before processing.
· if the “Process Payment Immediately” toggle is Enabled, the payment will be processed immediately.
· if the “Include BDE Items linked to a BDE” toggle is Enabled, when creating a Batch Donation Entry record it allows to linked a BDE item.
· if the “Allow Changes to Processed Batch Donation Entries” is Enabled, it allow changes on the processed Batch Donation Entry records like deleting or editing it.