Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

We also have BDE and Quick Donate configuration guides available.

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.

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.

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

Default Schedule d Hour

Batch Class Name

Descriptions

Delete Donatio n Page Error Logs

ASPHPPADDON__Donation_Page_Error_L og__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 Opportunitie s that are Closed/Won with CreatedDate <LAST_N_DA YS> (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

Batch Class Name

Descriptions

Batches

Recurring Donations

BatchUpdateRecurringFields

Default Schedule d Hour

Every Hour

Monitorin g

BatchUpdateNumberOfFailedRD

  • Query all non-closed

RDs and counts the number of (latest) consecutive closed lost opportunitie s.

Update Number Of Failed Recurring Donations

Every Midnight

Close Open Recurring Donations with Contact Flagged as Deceased

BatchCloseOpenRDWithDeceasedCont act

  • Query all non-closed

    RDs with Contact npsp__Decea sed__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:

07May2020 - Updated this document per version 2.36 changes 09April2020 - Created this document

  • No labels