TAPSS-1100 AVE-405 /AVE-399 - Customisable Campaign Influence (Deployment ticket)

Table of Contents

Components Added/Modified:

Label	API Name	Type	Type - Description	sObject	New/Update	Description/Change
Opportunity After Save	USYD_OpportunityAfterSave	Flow	record-triggered flow	Opportunity	New	Opportunity Main Flow for After Save Automation
Create Campaign Influence	USYD_CreateCampaignInfluence	Flow	auto-launched flow	Opportunity	New	The automation flow in creating Campaign Influence records
Opportunity Layout	Opportunity Layout	Layout	Page Layout	Opportunity	Update	Added Related List: Campaign Influence
Usyd - AQ Bequest 3.17	Usyd - AQ Bequest 3%2E17	Layout	Page Layout	Opportunity	Update	Added Related List: Campaign Influence
Usyd - AQ Bequest 3.17 Admin	Usyd - AQ Bequest 3%2E17 Admin	Layout	Page Layout	Opportunity	Update	Added Related List: Campaign Influence
USyd - AQ Lightning Outright Gift	USyd - AQ Lightning Outright Gift	Layout	Page Layout	Opportunity	Update	Added Related List: Campaign Influence
USyd - AQ Lightning Outright Gift Admin	USyd - AQ Lightning Outright Gift Admin	Layout	Page Layout	Opportunity	Update	Added Related List: Campaign Influence
USYD Campaign Influence Layout	USYD Campaign Influence Layout	Layout	Page Layout	Campaign Influence	New	New Layout of Campaign Influence
USYD Campaign Influence Permissions	USYD_Campaign_Influence_Permissions	Permission Set	Permission Set that provides access to Campaign Influence Object	-	New	Special Permission Set for users that require seeing Campaign Influence records
System Administrator	Admin	Profile	Profile	-	Update	Campaign Influence Layout assignment
Read Only	Read Only	Profile	Profile	-	Update	Campaign Influence Layout assignment
Usyd ASR User	Usyd ASR User	Profile	Profile	-	Update	Campaign Influence Layout assignment
USyd Standard User - Prospect Development	USyd Standard User - Prospect Development	Profile	Profile	-	Update	Campaign Influence Layout assignment
USyd Standard User	USyd Standard User	Profile	Profile	-	Update	Campaign Influence Layout assignment

Components deployed using TAPSS-1100, but were not actually part of TAPSS-1100’s requirements:

Label	API Name	Type	Type - Description	sObject	New/Update	Description/Change
Usyd move contacts related to Account to Contact Roles	Usyd_move_contacts_related_to_Account_to_Contact_Roles	Flow	record-triggered flow	Opportunity	Deactivated	translated to subflow(auto-launched flow), USYD_CreateOpportunityContactRole
Opportunity_afterInsertUpdate	Opportunity_afterInsertUpdate	Flow	record-triggered flow	Opportunity	Deactivated	translated to subflow(auto-launched flow), USYD_UpdateSourceGiftAccount
Usyd move contacts related to Account to Contact Roles	Usyd_move_contacts_related_to_Account_to_Contact_Roles	Flow Definition	Flow Definition	Opportunity	Deactivated	Flow definition counterpart of flow: Usyd_move_contacts_related_to_Account_to_Contact_Roles
Opportunity_afterInsertUpdate	Opportunity_afterInsertUpdate	Flow Definition	Flow Definition	Opportunity	Deactivated	Flow definition counterpart of flow: Opportunity_afterInsertUpdate
Opportunity After Save	USYD_OpportunityAfterSave	Flow	record-triggered flow	Opportunity	New	Opportunity Main Flow for After Save Automation
Create Opportunity Contact Role	USYD_CreateOpportunityContactRole	Flow	auto-launched flow	Opportunity	New	The automation flow in creating Opportunity Related Contact Role records. Optimized version of Usyd_move_contacts_related_to_Account_to_Contact_Roles
Update Source Gift Account	USYD_UpdateSourceGiftAccount	Flow	auto-launched flow	Opportunity	New	The automation flow in updating Source Gift Account records. Optimized version of Opportunity_afterInsertUpdate

Deployment Steps:

Enable the Campaign Influence Feature in target org.
Add a New Attribution Model in Setup.
1. Model Name: Usyd Attribution Model
2. Unique Name: Usyd_Attribution_Model
3. Default Model: TRUE
4. Locked: FALSE
5. Active: TRUE
6. Record Preferences: All Records
Use branch: TAPSS-1100-PermSetOnly-v2, to deploy the Permission Set: USYD Campaign Influence Permissions, to the target org.
In the target org, assign the Permission Set to the set deploying user: Salesforce DevOps.
Use branch: TAPSS-1100-from-rebased-master, to deploy all TAPSS-1100 components to target org.

Unit Testing Steps:

Setup

*Tester must be assigned to the Permission Set: USYD Campaign Influence Permissions, on top of any Profile listed below, to be successful in viewing/analyzing Campaign Influence records.

Profile:

System Administrator, Read Only, Usyd ASR User, USyd Standard User - Prospect Development, USyd Standard User.

If you are unable to assign the Permission Set to the target User due to the User’s license not allowing it, try updating the User’s “Permission Set License Assignments” first. Tick the checkbox for “Service User” or “CRM User” depending on the requirements/instructions by the Business. Normally “Service User” is what gets ticked.

Acronyms that you may find in the Scenarios section:

*GT = Greater Than
*LT = Less Than

Preparations:

Create a Test Opportunity
1. Record Type: Gifts in Will (API:Gifts_in_Will) OR Gift/Pledge (API:OutrightGift)
2. Has Related Contact Roles
  1. The Contact is assigned to Campaigns.
    How to add a Contact to Campaigns:
    1. Contact>Engagement>Campaigns>Campaign History: Click on Add to Campaign>Select a Campaign>Set Values for a New Campaign Member record:
      1. Responded: TRUE (Ticked) - change Status to Donated to set Responded to TRUE.
      2. Start Date: GT Today()-2557 Days [Greater Than Date From 7 Years Ago]. If Date Today is November 17, 2023, suggested Start Date would be any Date after January 20, 2017 … e.g. January 27, 2017 should work!
        [Click on EDIT after you create for each campaign member to view all its fields (e.g. Responded,etc)]
Apply the Scenarios listed below.
After Applying the scenarios, trigger the automation by updating the Opportunity Stage to Closed Won. Make sure that the previous Stage is not Closed Won.
Check the new Campaign Influence records that gets created by the automation to verify expected results.

Scenarios

Scenario #1: 1 FTP (First Touchpoint) - Only 1 Campaign Member

1 campaign member that satisfies all the configurations mentioned above.

Scenario #2: Total of 7 Campaign Members
A. 1 FTP (First Touchpoint), 1 STP (Second Touchpoint) - 2 Campaign Members that satisfies all the configurations mentioned above. The one with the earliest Start Date will be the FTP, the one with the second earliest date will be the STP.

If Date Today is November 17, 2023, suggested Campaign Member Start Date for FTP would be any Date after January 20, 2017 … e.g. January 27, 2017 should work! For STP, January 28, 2017 should work!

Note: Campaign Members are processed sequentially, following a waterfall approach. For instance, the categories below will handle the remaining Campaign Members that were not processed by the preceding category. Then, the next category will only process what’s left in the waterfall (list of remaining Campaign Members), and so on.

B. 1 MRGBO (Most Recent Gift before Opportunity) - 1 Campaign Member with the following attributes:
Status=Donated
Start Date=GT (Opportunity CreatedDate)-366 AND LT (Opportunity CreatedDate).

*If your Opportunity Created Date is November 17, 2023, Suggested Start Date for your Campaign Member should be between November 17, 2022 AND November 17, 2023 … e.g. November 16, 2023 should work!

Note: MRGBO only processes the Campaign Member with the most recent Start Date that is left from the waterfall.

C. 1 MRCBO (Most Recent Campaign before Opportunity) - 1 Campaign Member with the following attributes:

Status=Donated
Start Date=GT (Opportunity CreatedDate)- 180 AND LT (Opportunity CreatedDate)

*If your Opportunity Created Date is November 17, 2023, Suggested Start Date for your Campaign Member should be between May 21, 2023 AND November 17, 2023 … e.g. November 15, 2023 should work!

Note: MRCBO only processes the Campaign Member with the most recent Start Date that is left from the waterfall.

D. 1 MRCBS (Most Recent Campaign before Solicitation) - 1 Campaign Member with the following attributes:

Status=Donated
Start Date=GT (Opportunity Solicitation Stage Date)-90 AND LT (Opportunity Solicitation Stage Date)

*If your Opportunity Solicitation Stage Date is November 17, 2023, Suggested Start Date for your Campaign Member should be between August 20, 2023 AND November 17, 2023 … e.g. November 14, 2023 should work!

Note: MRCBS only processes the Campaign Member with the most recent Start Date that is left from the waterfall.

E. 1 MRCBW (Most Recent Campaign before Closed Won) - 1 Campaign Member with the following attributes:

Status=Donated
Start Date=GT (Opportunity CloseDate)-90 AND LT (Opportunity CloseDate)

*If your Opportunity Close Date is November 17, 2023, Suggested Start Date for your Campaign Member should be between August 20, 2023 AND November 17, 2023 … e.g. November 13, 2023 should work!

Note: MRCBW only processes the Campaign Member with the most recent Start Date that is left from the waterfall.

F. 1 Even Distribution - 1 Campaign Member

Status=Donated

Any remaining Campaign Members that did not satisfy any of the conditions above will be processed under Even Distribution.

Expected Results

Notes:

Created Campaign Influence records will show up in the related list of the triggering Opportunity.

Because the Campaign Influence list view only show a few fields, you can click on Edit to view all the fields.

Scenario #1: Expected NEW Campaign Influence Records

Campaign Influence:
Campaign ID=Campaign ID of Campaign Member in Scenario #1
Contact ID=Contact ID of Campaign Member in Scenario #1
Influence=20
Model/Model Id=DeveloperName is Usyd_Attribution_Model, ID may vary by ORG
Opportunity Id=ID of Triggering Opportunity

Scenario #2: Expected NEW Campaign Influence Records

Note: Campaign Members are processed sequentially, following a waterfall approach. For instance, the categories below handle the remaining Campaign Members that were not processed by the preceding category.

Campaign Influence 1 FTP (First Touchpoint):
Campaign ID=Campaign ID of a Campaign Member in Scenario #2 with the earliest Start Date
Contact ID=Contact ID of a Campaign Member in Scenario #2 with the earliest Start Date
Influence=20
Model Id=DeveloperName is Usyd_Attribution_Model, ID may vary by ORG
Opportunity Id=ID of Triggering Opportunity

Campaign Influence 1 STP (Second Touchpoint):
Campaign ID=Campaign ID of a Campaign Member in Scenario #2 with the second earliest Start Date
Contact ID=Contact ID of a Campaign Member in Scenario #2 with the second earliest Start Date
Influence=14
Model Id=DeveloperName is Usyd_Attribution_Model, ID may vary by ORG
Opportunity Id=ID of Triggering Opportunity

Campaign Influence 1 MRGBO (Most Recent Gift before Opportunity):
Campaign ID=Campaign ID of a Campaign Member in Scenario #2.B
Contact ID=Contact ID of a Campaign Member in Scenario #2.B
Influence=14
Model Id=DeveloperName is Usyd_Attribution_Model, ID may vary by ORG
Opportunity Id=ID of Triggering Opportunity

Campaign Influence 1 MRCBO (Most Recent Campaign before Opportunity):
Campaign ID=Campaign ID of a Campaign Member in Scenario #2.C
Contact ID=Contact ID of a Campaign Member in Scenario #2.C
Influence=14
Model Id=DeveloperName is Usyd_Attribution_Model, ID may vary by ORG
Opportunity Id=ID of Triggering Opportunity

Campaign Influence 1 MRCBS (Most Recent Campaign before Solicitation):
Campaign ID=Campaign ID of a Campaign Member in Scenario #2.D
Contact ID=Contact ID of a Campaign Member in Scenario #2.D
Influence=IF Opportunity Record Type is 'Gifts in Will', Then 7, Else 14
Model Id=DeveloperName is Usyd_Attribution_Model, ID may vary by ORG
Opportunity Id=ID of Triggering Opportunity

Campaign Influence 1 MRCBW (Most Recent Campaign before Closed Won):
Campaign ID=Campaign ID of a Campaign Member in Scenario #2.E
Contact ID=Contact ID of a Campaign Member in Scenario #2.E
Influence=IF Opportunity Record Type is 'Gifts in Will', Then 7, Else 14
Model Id=DeveloperName is Usyd_Attribution_Model, ID may vary by ORG
Opportunity Id=ID of Triggering Opportunity

Campaign Influence 1 Even Distribution:
Campaign ID=Campaign ID of remaining/last Campaign Member in Scenario #2
Contact ID=Contact ID of remaining/last Campaign Member in Scenario #2
Influence=IF Opportunity Record Type is 'Gifts in Will', Then (24/NumOpptyContactCampaigns), Else (10/NumOpptyContactCampaigns))
Model Id=DeveloperName is Usyd_Attribution_Model, ID may vary by ORG
Opportunity Id=ID of Triggering Opportunity

**NumOpptyContactCampaigns is the number of remaining Opportunity Campaign Members that is left to process that did not get processed by preceding categories (e.g. Campaign Influence 1 First Touchpoint, Campaign Influence 1 STP, Campaign Influence 1 MRGBO, and so on…).