Skip to content

Technical Implementation Guide

Mat Ruff edited this page Jul 31, 2019 · 4 revisions

Table of Contents

Introduction

Purpose

The purpose of this document is to provide a detailed overview of the technical aspects of Interactions for Student Recruitment. It will explain the purpose behind the functionality, features, business logic, expected behavior, and opportunities for customization. It is intended as a specification document for stakeholders, administrators, and developers.

Product Perspective

Interactions serve as a record of a touchpoint with an individual. Interactions can be created manually from an existing Lead, Contact, Opportunity, Campaign, or from the Interaction tab itself. They can also be mass created through integration or a list load.

In addition to tracking points of contact, the Interaction object operates as a staging table. When an Interaction record is created at a status of "New," an Apex process runs and leverages Salesforce functionality such as Lead Conversion and Duplicate Management to upsert other standard and custom records. Interaction Mapping records determine which fields are updated from the Interaction record.

EDA must be installed prior to installing the Interactions for Student Recruitment package. It is possible to install Interactions without EDA by downloading the Interactions for Student Recruitment repository on GitHub and removing references to EDA fields and objects in the code and package before installing. This will require a developer, and if this approach is chosen, the process will not use EDA objects, fields, or the functionality provided through EDA triggers referenced above. Additional testing will be required to confirm Interactions works as expected. See the Installation & Configuration Guide for more information.