ProntoGiving - additional configuration

Hide Unused/Deprecated Components

1. Navigate to Setup | Users | Choose Profile. (Note: Do to all Profiles or a specific profile

   that you want to hide those tabs)

2. Click Edit

3. Go to Tab Settings section and hide the following tabs if visible:

   1. DEPRECATED - BDE Wizard 2.0

   2. DEPRECATED-ProntoPayments Settings

   3. DEPRECATED - Bulk Donation Templates

   4. Deprecated ProntoPayments Settings

   5. DEPRECATED - ProntoGiving Settings2

   6. DEPRECATED-Manage ABA Files

   7. Bulk Donation Entry Wizard v1.0

   8. Bulk Donations (v1.0)

   9. Receipt Templates

   10. Consolidated Statements

   11. Consolidated Statements Settings

   12. Quick Donate 1

   13. Batch Data Entry

Quick Donate

Setup Process Type for Payment Transaction

1. Go to Setup | Object Manager | Payment Transactions | Fields & Relationships | Process Type

2. Make sure that the Manual Payment and Via ProntoPayments are active in the picklist values section.

Setup Field Dependencies on Process Type

1. Go to Setup | Object Manager | Payment Transactions | Fields & Relationships | Process Type

   1. Edit the Field Dependencies

   2. Under Manual Payment select:

      1. Cash

      2. Cheque

      3. Bank Account

      4. Credit Card

   3. Under Via ProntoPayments select:

      1. Bank Account

      2. Credit Card

Enable the Manual Payment record type

1. Go to Setup | Object Manager | Payment Transaction | Record Types | Manual Payment | Edit

Setup Cash record type

1. Process Type

   1. Go to Setup | Object Manager | Payment Transactions | Record Types | Cash | Process Type → Edit

   2. Ensure Manual Payment and Via ProntoPayments are in the Selected Values column

2. Payment Type

   1. Ensure all values are in the Selected Values column

   2. Go to Setup | Object Manager | Payment Transactions | Record Types | Cash | Edit Payment Type

3. Card Expiry Month

   1. Ensure all values are in the Selected Values column

   2. Go to Setup | Object Manager | Payment Transactions | Record Types | Cash | Edit Card Expiry Month

4. CardType

   1. Ensure all values are in the Selected Values column

   2. Go to Setup | Object Manager | Payment Transactions | Record Types | Cash | Edit Card Type

5. Payment Status

   1. Ensure all values are in the Selected Values column

   2. 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:

1. One-Off Donation

   1. Close Date

   2. Lead Source

   3. Stage

   4. Primary Campaign Source

   5. Receipt Action (PPlus)

   6. Receipt Template (PPlus)

      

2. Recurring Donation

   1. Schedule Type

   2. Campaign

   3. Installment Period

   4. Installments

   5. Date Established

   6. Lead Source

   7. Always use last day of month

   8. Exclude in RD Monitoring

   9. Receipt Action (PPlus)

   10. Receipt Template (PPlus)

3. QD New Contact Fieldset

   1. First Name

   2. Last Name

   3. Email

   4. Work Email

   5. Personal Email

   6. Alternate Email

   7. Receipt Email (PPlus)

   8. Receipt Action Preference (PPlus)

4. QD Existing Contact

   1. First Name

   2. Last Name

   3. Mailing Street

   4. Mailing City

   5. Mailing Country

   6. Mailing State/Province

   7. Mailing Zip/Postal Code

   8. Phone

   9. Email

   10. Work Email

   11. Personal Email

   12. Alternate Email

   13. Receipt Email (PPlus)

   14. Receipt Action Preference (PPlus)

5. QD New Account Fieldset

   1. Receipt Recipient (PPlus)

6. QD Existing Account Fieldset

   1. Billing Street

   2. Billing City

   3. Billing State/Province

   4. Billing Zip/Postal Code

   5. Billing Country

   6. Receipt Recipient (PPlus)

7. QD Credit Card Fields (This is only optional because not all gateways require CCV field)

   1. 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

1. Set the default values in your Quick Donate Page.

2. Go to ProntoGiving Settings | Donation | Quick Donate. These will be set by the client

Setup Sales Process

1. Go to Setup | Feature Settings | Sales | Sales Process

2. Ensure that the Pledged or Prospecting stage is selected in your active Sales

   Processes

Set Default Record Type to Cash

1. Go to Setup | Profile | System Admin | Object Settings | Payment Transactions

2. 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.

1. Go to ProntoGiving Settings | Donation Fields Mapping.

2. Create new mapping by clicking the New button.

3. Add the mapping below

   1. Donation Type (PPlus)

   2. Receipt Action (PPlus) - for clients that use Wordpress in their Donation Form.

Barcode

1. Go to ProntoGiving Settings | Donation | Settings | Barcode

2. Enable the barcode. Once enabled, the barcode field will display in the Quick Donate and Batch Donation Entries page.

   1. 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

   2. Unique ID Account Field Name - scans a matching value on the field specified for Account

   3. Unique ID Contact Field Name - scans a matching value on the field specified for Contact

   4. 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.

ProntoGiving Settings

Setup Opportunity Stages

a. Go to ProntoGiving Settings | Donation | Stage and set according to the client requirements

Setup Settings

1. Go to ProntoGiving Settings | Donation | Settings and make changes to the following according to the client requirements:

   1. Enable Default Campaign

   2. Anonymous Contact

   3. One-Off Record Type.

Recurring Donations

1. Go to ProntoGiving Settings | Recurring Donations | Recurring Donation Naming

2. Setup Recurring Donation Naming.

3. 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

1. Setup Remote Site Settings

   1. Switch to Classic Environment

   2. Go to ProntoGiving Settings and copy the highlighted link below.

   3. Note: Every org has a different URL

   4. Go to Setup > Security > Remote Site Settings. Update Metadata Remote Site

   5. 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.

1. Go to App Launcher | Trigger Handler

2. The PP_ASPaymentTXN_TDTM trigger handler requires ProntoPayments version 2.7 or

   higher

3. Add the PP_Opportunity_TDTM trigger handler if:

   1. The org has NPSP installed, if none, don’t add

   2. Once the trigger is added, enable the NPSP TDTM toggle in ProntoPayments Settings

4. Load Order should be ProntoPayments, ProntoGiving, ProntoPlus and org customisation for every object.

Please note: all triggers should be Active.

Default Batches to Run

Go to ProntoGiving Settings | Schedule Process | Settings

Recurring Donations

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.

Approval Process

Enable record locking and unlocking in Apex. Go to Setup > Process Automation > Process Automation Settings.

Create Approval Process

1. Go to Setup > Process Automation > Approval Process. Create new Approval Process for Batch Donation Entry (if not yet created)

2. In Manage Approval Process For picklist, select the Batch Donation Entry and select the Use Standard Setup Wizard option.

3. The Process Name should be “Batch Donation Entry Approval Process”. Click Next to proceed.

4. Under the Use this approval process of the following picklist select “formula evaluates to true” and copy the formula below. Click Next  to proceed.

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')) )

1. In the Record Editability Properties section, choose the “Admins ONLY can edit records during the approval process”. Click Next to proceed.

2. Choose the BDE Approval Process Template (BDE 2.0). Click Next to proceed

3. Choose the fields to display in the Approval Request page:

   1. Batch Donation Entry Name

   2. Bulk Donation Status

   3. Description

   4. Expected Total Amount of Donations

   5. Expected Number of Donations

   6. Click Next to proceed

4. Select Record Creator as the "Allowed Submitters”.  Click Save to finish. After saving, you will be redirected to this page.

5. Create Initial Submission Actions  for Update Batch Status Awaiting Approval. Click the Add Existing button and select Field Update

6. Create Approval Steps

   1. Click the New Approval Step button

   2. Enter Name and Description, click Next

   3. Step 1: User Approval, Unique Name Step_1_User_Approval

   4. Specify step criteria: Select “Enter this step if the following” criteria are met, else reject record and copy the values below.

Select Approver step and click Save when done.

7. Create Final Approval Actions - for Update Batch Status Approved. Click the Add Existing button and select Field Update

8. Create Final Rejection Actions - for Update Batch Status To Be Processed. Click the Add Existing button and select Field Update. After completing the setup click the Activate button to activate the Approval Process.

Enable Approval Process

Enabling the Approval Process toggle will help the Admin to receive an Approval Request and approve or reject the BDE records. Only those Approved BDE records will be processed.

1. 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) and ensure the tickbox is selected.

User Interface

If some of the components in the Batch Donation Entries are not showing, you can show them by following these steps.

1. Go to Batch Donation Entries tab

2. Select any records in the list

3. Click the settings cog icon and select the Edit Page option. It will load the Lightning record page layout where you can see which Lightning Components are available to use. Search the components by going to the Lightning Components search bar

4. Ensure the following Components are displayed in the Batch Donation Entries tab:

   1. New BDE Item Form

   2. BDE Items Summary

   3. BDE Items Related List

5. Search for the components in the search bar and drag them onto the centre component, and Save. 

Show BDE Barcode Field in BDE UI

The BDE Barcode will only be visible if the toggle is enabled in the settings. Go to ProntoGiving Settings | Donation | Settings | Barcode. Enable the toggle.

Required Custom Fields

Create the following fields under the BDE Item object before creating the BDE Templates and Item Record Mapping.

Add the following fields if not yet added.

BDE Item fields to be manually deleted

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

Under ProntoGiving Settings > Batch Donation Entry > BDE 2.0 > Settings page:

• 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. 

Batch Donation Entry Permission Set

Profile Permissions

Additional Fields

BDE Matching Criteria

Setup BDE Matching Criteria

Note: This step is done automatically after installation. However, if the user needs to add more fields to be mapped, follow the steps outlined below.

Add Mapping

1. Go to ProntoGiving Settings > Batch Donation Entry > BDE Matching Criteria

2. The user can specify Matching Rules for Primary Contact, Soft Credit Contact, Primary Account, Soft Credit Account, Campaign and Primary Campaign on BDE Item fields, based on the specified matching fields and Priority on the setting

3. Submitted BDE Items will search for matching records or create new record if not found

4. When Match is found, action is taken based on the Matching Rules

5. When Match is not found, create new record and populate to appropriate fields. For example a user might want to map the Contact Object with its BDE Item matching fields.

BDE Item fields FirstName, LastName, Email was mapped to the Contact Object as the highest priority 1. Additionally, these are the Matching fields that should be mapped accordingly, although some fields may be omitted depending on the user requirements.

BDE Matching Criteria

Expected Outcome

Assumption: 

The user has typed the First Name, Last Name, Email on the BDE Item record details (before Process Batch). Clicking Process Batch button submits the record, then creates an appropriate Opportunity and will populate the Contact record based on the Matching Criteria fields being setup on the settings. 

If there is a match, it will populate the Contact record on the created Opportunity.

If there is no match, it will create a new Contact record and populate on the Opportunity.

BDE Data Load in BDE Item Object

Data Loader is used to insert or update donations to Salesforce; one-off or recurring donations in one batch. The following instructions will walk you through the minimum required fields for each type.

Minimum required fields for One-Off Donation

ASPHPPADDON__Primary_Account__c/ASPHPPADDON__Primary_Contact__c

ASPHPPADDON__Date__c

ASPHPPADDON__Amount__c

ASPHPPADDON__Opportunity_Stage__c

ASPHPPADDON__Frequency__c (One-Off)

ASPHPPADDON__Donation_Type__c

Minimum required fields for Recurring Donation

ASPHPPADDON__Primary_Account__c/ASPHPPADDON__Primary_Contact__c

ASPHPPADDON__Amount__c

ASPHPPADDON__Date__c

ASPHPPADDON__Frequency__c (Weekly, Monthly, Yearly)

Note: If you want to add a field that doesn’t already exist, you can create it as custom field and add the mapping in the  BDE Item Record Mapping.

Minimum required fields for updating Recurring Donations

ASPHPPADDON__Recurring_Donation__c

It could be any Recurring Donation fields specified in the Item Record Mapping.

Note: For Recurring Donation required fields that are not mapped or setup in BDE Item Record Mapping, make sure to put default values in the following fields:

Date Established → Current Date

npe03_Contactc or npe03Organization_c should not be empty

npe03_Installment_Period_c → Monthly

npe03_Installments_c → 12

npe03_Next_Payment_Date_c → Current Date

npe03_Open_Ended_Status_c → Open

npe03_Schedule_Type_c → Multiple By

Note: If any field that you want to update, then that field doesn’t exist, you can create that as           custom field and add the mapping in the  BDE Item Record Mapping.

Minimum required fields for donations via Credit Card (aside from one-off or recurring donations).

ASPHPPADDON__Credit_Card_Name__c

ASPHPPADDON__Credit_Card_Number__c

ASPHPPADDON__Credit_Card_Expiry_Year__c

ASPHPPADDON__Credit_Card_Type__c

ASPHPPADDON__Credit_Card_Expiry_Month__c

ASPHPPADDON__CCV__c     

Minimum required fields for donations via Bank Account (aside from one-off or recurring donations)

ASPHPPADDON__Bank_Account_Name__c

ASPHPPADDON__Bank_Account_Number__c

ASPHPPADDON__Bank_Account_BSB__c

Minimum required fields for donations with 1 GAU Allocation (aside from one-off or recurring donations)

ASPHPPADDON__GAU_1_Amount__c

ASPHPPADDON__GAU_1_ID__c

ASPHPPADDON__GAU_1_Name__c

Minimum required fields for Donation with Multiple GAU Allocations

ASPHPPADDON__GAU_Allocations__c

ASPHPPADDON__New_GAU_Allocation_on_Recurring_Donation__c

This is the format to be inserted in the GAU Allocations field:

[ 

{

  "gauID" : "a0w0o00000QefXjAAJ",

  "allocationAmount" : 15

}, {

  "gauID" : "a0w0o00000QeYXtAAN",

  "allocationAmount" : 20

}, {

  "gauID" : "a0w0o00000QeYXtAFGH",

  "allocationAmount" : 25

} 

]

Note: You can add as many GAU Allocations provided it meets the criteria.

Import Data via Data Loader

1. Open the Data Loader application

2. Click Insert and enter your Salesforce username and password. To log in, click Log in.

3. Choose the ASPHPPADDON__BDE_Item__c object. If this object name is not displayed on the default list, select Show all objects to see the complete list of the objects that you can access. 

4. To select your CSV file, click Browse

5. Click Next. After the object and CSV file are initialised, click OK

6. Define how the columns in your CSV file map to Salesforce fields. To select an existing field mapping, click Choose an Existing Map. To create or modify a map, click Create or Edit a Map

7. For each operation, the Data Loader generates two unique CSV log files, one file name starts with “success”, and the other starts with “error”. Click Browse to specify the directory for these files.

8. To complete the operation, click Finish, and then click Yes to confirm. As the operation proceeds, a progress information window reports the status of the data movement

9. To view your success or error files, click View Successes or View Errors. To close the wizard, click OK. To verify that the records are saved to Salesforce successfully, go to the BDE Items tab. Create a list view that will display all the records created today to see your imported records.

Map BDE Item fields to any record fields

Please follow this link.

Process BDE Items

To process the records that you imported, please follow this link.