Install and configure baseline - Web Integration Toolkit

On this page

WIT Flow Application errors debug logs via email

By default, when a process or flow interview fails, Salesforce sends an email with details about everything that was executed and what failed. The details include the data that's involved in the process or flow, including user-entered data. The user who last modified the flow will be the default recipient of the email. To avoid receiving the FlowApplication errors via email, please follow the steps below:  

1. Go to setup > Process Automation Settings 

2. From the Process Automation Settings, change the “Send Process or Flow Error email to” to Apex Exception Email Recipients and save. 

3. Go to setup > Apex Exception Email and do not set (or remove) any user or emails.

Create Community Page 

Go to Setup > All Sites > Select the community site > Builder

There is one page you need to set up for WIT for every client project; the Checkout Page. If you are notified the client is going to pay for WIT as a separate product licence, set up all the following pages:

To create a new page, just follow the steps below: 

Repeat the same steps for all the pages. 

Page Title 

Make sure to edit the page title in every page and it depends on the client preference. 

Assign flow to the Pages 

Open one of the pages that you created. Drag the “ASFundraisingFlow” custom component into the centre of the page.

Fill out the flow details. Note: Flow name should have a prefix of WITFA__flowname

• See the list of flow details link under “ASFundraising Flow” section. Repeat the same steps for all the pages.

Update the CSS 

A message will appear ‘Override CSS?’; select Use Overrides. Paste the CSS code provided into the edit window.

Security and Privacy

Create the Trusted Sites for Scripts below. Set the Status to Active for all entries.

Public Access

Make all the pages accessible to public. Repeat the same steps for all the 3 pages (Multi Screen, Single Screen and Checkout Page).

Go to Settings > General > Enable “Public can access the site”. 

Publish Site 

Click the Publish button at the top right hand corner of the page.

Guest User Profile Permissions

Object Settings

Set all object permissions to Read.

Object Names:

• Gateway disclaimers

• GAU selection list

• Campaign dollar handles

• GAU allocations

• Campaigns

Apex Class Access 

 Update Time Zone for Guest User 

Go to Setup > Profiles > Web Integration Toolkit Profile > Guest User Licence.

Update the time zone to Australia or wherever is the client located. Click Assigned Users and Edit. 

Click Edit. Set up the correct Time Zone under Locale Settings.

Activate Site

Flow Access 

Give the Salesforce Admin or other profile access to wit flows. Go to Setup > Profile > System Admin > Object Settings.

Setup CSP Trusted Sites 

Go to Setup > CSP Trusted Sites. Make sure that the following trusted sites below are created.

Setup CORS 

Go to Setup > CORS. Make sure that the following CORS below are created.

Setup Remote Site Settings
Go to Setup > Remote Site Settings. Make sure that the following remote sites below are created. 

Manage Campaign Record Types 

These are the available campaign record types.

Setup Custom Metadata Types
Go to Setup > Custom Metadata Types. Find Web_Page_URL and select “Manage Records”. 

Make sure that these metadata are created.

Setup Custom Settings
Go to Setup > Custom Settings > Web Toolkit Settings and click “Manage”. 

Create a new one and choose what WIT features need to enable. For example, if the client is only using the Multi Screen Donation Page then, enables only that feature. 

Note: If they will use PayPal (Make sure that the PayPal Default Currency has a value of “AUD”).

Generate Encryption Key 

Go to App Launcher > Web Toolkit Settings > Session > Encryption. Click Generate. 

Schedule Generate Encryption Key 

Go to Developer Console > Debug > Open Execute Anonymous > Windows > Paste the code below and execute. This will run every midnight. 

String schedName = 'AS Randomize WIT Encryption Key';
System.schedule(schedName, '0 0 0 ? * * *', new WITFA.ASWITEncryptionKeyRandomizerSchedule()); 

To check the job. Go to Setup > Scheduled Jobs. You will see it listed as ‘AS Randomize WIT Encryption Key’.

Trigger Handler  

Go to App Launcher > Trigger Handler > Create new if doesn’t exist yet. 

Product specific settings 

ProntoGiving

Setup Campaign Donation Record Types

Copy the “Donation Page” record type id in the campaign object. Go to Setup > Object Manager > Campaign > Record Types > Donation Page (WITFA) namespace.  

Go to Setup > Custom Settings > ProntoGiving Settings > Manage. 

Edit the Custom Settings. Paste the record type id.

(Optional) If there is an error when uploading a campaign banner 

Switch to a classic environment. Go to Setup > Content Permission > Library Administrator > Edit. Enable all actions.

Content Deliveries and Public Links 

Also, ensure the permission ‘Create Content Deliveries’ is enabled in the profile by going to Setup > Profile Name > System Permissions. 

Go to the Campaign Lightning Page and click on the Flow Component: ASUploadCampaignBanner. On the right hand side you will see a checkbox ‘Pass record ID into this variable’. Ensure this checkbox is enabled.

ProntoPayments 

Go to ProntoPayments Settings > Settings > Basic. Disable the “Auto Create Payment Transaction” toggle.

Other Profiles that will use WIT 

Go to Setup > All Sites > Select Community Site > Administration > Members. Add the custom profile or permission set and save.

Make sure that it has access to all record types in the Payment Transactions object. Go to Setup > Profiles > Custom Profile Name > Object Settings > Payment Transactions. 

Update BDE Item Record Mapping 

Go to ProntoGiving Settings > Batch Donation Entry > BDE 2.0 > Item Record Mapping. Note that this is the baseline mappings for WIT and FA. See link.  

In the table below, the first column is the old mapping, you need to replace it with the second column. See the example. 

Old (BDE Item Fields)

New (BDE Item WIT Fields)

ProntoEngage Mapping 

Go to App Launcher > Campaign Importer > Campaign – Opportunity Mappings.

WIT CICD

These include: 

• Layouts -> Please refer to FA Demo Org  

• Campaign -> Please refer to the FA Demo Org 

• Campaign Member 

• Campaign Dollar Handle 

• BDE Item 

• GAU Selection List 

• Gateway Disclaimer 

• Gateway 

• BDE Item Record Mappings 

• BDE Templates 

• BDE Item Defaults 

WIT Gateway and Security Settings

Google ReCaptcha 

Go to App Launcher > Web Integration Toolkit Settings > Settings. Select Google reCAPTCHA v3 or v3 as Anti-Spam. 

Provide the Google reCAPTCHA site key. See this link on how to setup.

HoneyPot

Go to App Launcher > Web Integration Toolkit Settings > Settings. Select ASHoneyPot as Anti-Spam.

PayPal

Go to App Launcher > Web Integration Toolkit Settings > Settings. Ask the client for the PayPal Client Id. 

You can also select the minimum amount and to allow cents but it depends on the client preference.

Google Pay 

Go to App Launcher > Web Integration Toolkit Settings > Settings. Ask the client for the Google Pay Merchant Id and Google Pay Merchant Name. 

Note: Enable GooglePay Sandbox when you’re in a sandbox environment.

Flow Details

ASFundraisingFlow

UpdateContactDetails

Flow (Standard Component)

Flow Parameters

Multi Screen Donation Page

Campaign Record Type: Donation Page

• AS_Campaign_Id → Campaign Id

• Amount → Amount

  • Any amount values

  • The Amount field is auto-populated

  • If the provided amount value is an existing amount value from Campaign Dollar Handle, the dollar handle will be auto-selected

• GAU → GAU Selection List Id

  • Make sure the GAU Selection List Id is under the Campaign (check Related List)

  • The “Where do you want your donation to go?” will be auto-selected based from the GAU Selection List Id provided in the parameter

• UUID → Campaign Member’s UUID

  • Make sure the provided UUID is an existing Campaign Member of the Campaign

  • Donor details is auto-populated based from the UUID’s details (Campaign  Member.Contact details)

• utm_campaign, utm_content, utm_medium utm_source

  • Optional

  • If provided, no changes for the UI

• RDOnly → only allow the page to process recurring donation

  • If the RDOnly parameter = true/TRUE in the campaign record, the “Multiply my gift by making it a monthly donation” checkbox field in page is hidden

• If the RDOnly parameter = false/FALSE or URL has no RDOnly parameter in the campaign record, the user can tick or untick the “Multiply my gift by making it a monthly donation” checkbox field

Single Screen Donation Page

Campaign Record Type: Donation Page

• AS_Campaign_Id → Campaign Id

• Amount → Amount

  • Any amount values

  • The Amount field is auto-populated

  • If the provided amount value is an existing amount value from Campaign Dollar Handle, the dollar handle will be auto-selected

• GAU → GAU Selection List Id

  • Make sure the GAU Selection List Id is under the Campaign (check Related List)

  • The “Where do you want your donation to go?” will be auto-selected based from the GAU Selection List Id provided in the parameter

• UUID → Campaign Member’s UUID

  • Make sure the provided UUID is an existing Campaign Member of the Campaign

  • Donor details is auto-populated based from the UUID’s details (Campaign Member.Contact details)

• utm_campaign, utm_content, utm_medium utm_source

  • Optional

  • If provided, no changes for the UI 

• RDOnly → only allow the page to process recurring donation

  • If the RDOnly parameter = true/TRUE in the campaign record, the Multiply my gift by making it a monthly donation checkbox field in page is hidden

  • If  the RDOnly parameter = false/FALSE or URL has no RDOnly parameter in the campaign record, the user can tick or untick the Multiply my gift by making it a monthly donation checkbox field

Checkout Page

Campaign Record Type: Donation Page

• AS_Campaign_Id → Campaign Id

• AS_Amount → Amount

  • Any amount values

  • The Amount field is hidden

• AS_GAU → GAU Selection List Id

  • Make sure the GAU Selection List Id is under the Campaign (check Related List)

  • The “Where do you want your donation to go?” is hidden

• AS_Tribute_Type → Tribute Type: Honor, Memorial

  • The Tribute Type is hidden

• AS_Frequency → Frequency: One Off, Monthly

  • If One Off, the “Multiply my gift by making it a monthly donation” is hidden but the flow will identify the frequency as once off

  • If Monthly, the “Multiply my gift by making it a monthly donation” is hidden but the flow will identify the frequency as monthly

• AS_Payment_Type → Payment Type: Credit Card, Direct Debit, Other

  • Credit Card: The Credit Card will only display, other payment options will be hidden

• Direct Debit: The Direct Debit will only display, other payment options will be hidden

• Other: The Other will only display, other payment options will be hidden (NOT WORKING)

• AS_In_Tribute_Of → Name (text)

  • The In Tribute Of is hidden

• AS_Comments → Comments (text)

  • The Comment is hidden

• AS_Donation_Type → Donation Type: Individual, Organisation

  • Individual: The Individual donation type is auto-selected

  • Organisation: The Individual donation type is auto-selected

• AS_First_Name, AS_Last_Name, and AS_Email

  • These 3 parameters should be provided at the same URL

  • No Donor/Personal Details section will display (still in development)

• AS_Account_Name and AS_Email

  • These 2 parameters should be provided at the same URL

  • No Donor/Personal Details section will display (still in development)

• AS_Mobile_Phone → Mobile Phone Number

• AS_Postcode → Postal Code

  • Postal Code will be auto-populated

• AS_Country → Country

  • Country will be auto-populated

• AS_Salutation → Contact Salutation

• AS_State → State

  • State will be auto-populated

• AS_Street → Street Address

  • Street Address will be auto-populated

• AS_City → City

  • Suburb/City will be auto-populated 

Update Contact Details Page

Campaign Record Type: Update Contact Record Details

• AS_Campaign_Id → Campaign Id

• UUID → Campaign Member’s UUID

  • Make sure the provided UUID is an existing Campaign Member of the Campaign

  • Contact details is auto-populated based from the UUID’s details (Campaign  Member.Contact details).

Update Expired RD Credit Card

Campaign Record Type: Update Credit Card

• AS_Campaign_Id → Campaign Id

• UUID → Campaign Member’s UUID

  • Make sure the provided UUID is an existing Campaign Member of the Campaign

• AS_RecurringDonationID → Recurring Donation Id

  • Make sure the Recurring Donation record has a Primary Campaign based from the Campaign (RD is under Campaign)

  • Make sure the Recurring Donation record has a Payment Source where the Payment Source is equals to the Payment Source Id provided from the parameter

  • Make sure the Recurring Donation record has a Contact where the UUID is equals to UUID from parameter and is equals to the Contact of the Payment Source and a Campaign Member under the Campaign

• AS_PaymentSourceID → Payment Source Id

  • Make sure the Payment Source has a Contact where Contact is equals to the UUID from the parameter.

Reprocess Payment

Campaign Record Type: Reprocess Donation

• AS_Campaign_Id → Campaign Id

• UUID → Campaign Member’s UUID

  • Make sure the provided UUID is an existing Campaign Member of the Campaign

• AS_OpportunityId → Opportunity Id

  • Make sure the Opportunity record has a Primary Campaign based from the Campaign (RD is under Campaign)

  • Make sure the Opportunity record has a Payment Source where the Payment Source is equals to the Payment Source Id provided from the parameter

  • Make sure the Opportunity record has a Contact where the UUID is equals to UUID from parameter and is equals to the Contact of the Payment Source and a Campaign Member under the Campaign

• AS_PaymentSourceId → Payment Source Id

  • Make sure the Payment Source has a Contact where Contact is equals to the UUID from the parameter.

Update Credit Card page

Recurring Donations Expired Credit Card feature will create a new payment source to the Recurring Donation record. At the moment, it only supports Credit Card and Direct Debit payment type.

The contact should be a member of the campaign.

An email notification is sent to the contact assigned to RD record.

When the contact receives the email notification and clicked the Update RD Expired Credit Card button, contact will be redirected to the Update RD Expired Credit Card page.

Contact completes the necessary information and clicks the Next button. This creates a new payment source.

Update Contact Details Page

1. When Contact record is created/updated with Address Unknown field ticked. An email notification will sent to the email address added in the Contact.

2. The Contact will click the Update Your Contact Details here button on the email, which routes to the Update Contact Details page

3. Contact completes the necessary information and clicks the Update button

4. The BDE Item record is created with Pending Processing

5. After that you will see the changes at the Contact.

Reprocess Donation page

Required Provide the input field.

• Campaign ID

• Opportunity ID

• Payment Source ID

• UUID

If there is invalid input data, error has occurred. List scenario below:

Contact must have UUID ->

Payment type -> Credit Card

Payment Source must be populated

Campaign Name must be active

Opportunity ID/name must exist

When opportunity stage is a Closed Won

Inputted record is correct, you will see the image below

Input card information.

Input card data is not correct

When successful, it will create a BDE item record