TAP Product Enhancements Log

TAPSS-1100

Purpose: Campaign Influence provides insight into the impact marketing activity held in Campaigns is having on the pipeline held in Opportunities.

• Customisable Campaign Influence Business Requirements

• TAPSS-1100 AVE-405 /AVE-399 Technical Design Doc and Deployment Steps

Dec 14, 2023

TAPSS-1088

Enhancement to replicate special category alert from Advance in Jarvis. That is also, that the system should be able to flag the constituents accordingly as special category/categories when transactions are being made to the account attributable to contacts through GRC records.

TAPSS-1088 / TAP-57: MS - As a system support, we need to replicate the special category alert existing in Advance

Nov 30, 2023

TAPSS-914 and TAPSS-1708

Enhancement to fix the recurring issue when deceasing contact. The system should automatically put an end date to all active rating and relationship management team records and make then inactive. The utility should then run and the GA team should not have any error.

Flow was built to query on all related records for the Contacts to be deceased to avoid any AQ validation errors when doing the deceasing utility where Death of Date might be greater than the start date on related objects namely:

• Employment (tied up to contact)

• Membership (tied up to contact)

• Relationships with Contact (tied up to contact)

• Volunteer (tied up to contact)

• Relationship Management Team (tied up to contact)

• Relationships with Account (tied up to contact)

• Rating (tied up to account)

• Stewardship (tied up to account)

TAPSS-914/TAPSS-1708 Technical Design Doc

TAP - AQ Utility functionality to Join/Separate/Decease contacts

TAPSS-1708 deployedNov 30, 2023

TAPSS-914 deployed Oct 26, 2023

1. TAPSS-1434

2. TAPSS-1382

Developed a scheduled flow “Contact Case Schedule” that runs daily at 6am. This flow automatically create a case to decease a Contact when its age reaches 105

Made updates to existing flows to handle the following scenarios:

1. A Contact with an Age of 105 or higher, and still has an open decease request case associated. "Do Not Contact" is unticked. Contact has been previously deceased (Deceased? field is ticked).

   1. Flow sets "Do Not Contact" to TRUE (ticked).

   2. Because Contact has already been marked as deceased,

      1. A new decease request case is NOT created.

      2. “Status” of all existing OPEN decease request cases is then updated to “Closed”.

2. A Contact with an Age of 105 or higher, and does not have a decease request case associated. "Do Not Contact" is unticked. Contact has not been previously deceased (Deceased? field is unticked).

   1. Flow sets "Do Not Contact" to TRUE (ticked).

   2. Flow creates a new Case with the following details:

      1. Case Owner: Gifts Administration

      2. Type: Decease Contact

      3. Record Type: Join/Separate/Decease Request

      4. Status: New

      5. Priority: High

      6. Case Origin: Web

      7. Subject: Decease <Contact.Title> <Contact.FirstName> <Contact.LastName>

      8. Description: Decease per age turning 105, contact has been marked DNC (which needs to be reverted if contact will not be deceased). Please refer to Contact History to verify if DNC was updated on the same date/time this case was created.

TAPSS-1434 & TAPSS-1382 Technical Design Doc

TAPSS-1434 Deployed to PROD last Sep 28, 2023

TAPSS-1382 Deployed to PROD last Aug 31, 2023

TAPSS-845

Business Value:

Prevent the following internal salesforce technical error during Batch closing:

• Too many SOQL queries

• APEX CPU time limit exceeded

• DUPLICATE_VALUE: Maximum number of duplicate updates in one batch (12 allowed)

This is a permanent fix to the previous temporary work around of manually deactivating the Process Builder/Flows then update the Batch/Transaction records and re-activating afterwards. This will also avoid implications of data not being updated correctly during the deactivation of the batch/transaction records flow/PB

TAPSS-845/TAP-902 Tech Doc

Jul 27, 2023