EDA REQUIREMENTS FOR SALESFORCE ADVISOR LINK

Salesforce.org’s Education Data Architecture (EDA) is the foundation underlying the Connected Campus. It’s an open source, flexible platform for enterprise-wide

scale. EDA is a requirement for Salesforce Advisor Link (SAL) because it serves as À foundation to connect the student lifecycle so you can easily see what courses

your students are enrolled in and their campus affiliations. Let’s look more at the details of how SAL leverages the features of EDA.

Advisee CaseAlerts

Link to:Program EnrollmentCourse Enrollment

Advisee Case Lightning Page SAL Trigger HandlersContact

PanelStudent Records

Case Alert

Account ContactStudent

Custom ObjectsAffiliations, Relationships, Program Enrollments, …

Data AutomationTDTM

Contact

• SAL’s Advisee Case needs to be linked to a Contact (the Student). Contacts are standard

Salesforce objects so EDA can’t take credit. But EDA does make sure each contact has an

Administrative or Household account through automation, so SAL doesn’t need to worry about

setting that up.

Advisor Link Alerts are linked to the Contact and Advisee Case. They can also be

attributed to the Student’s Program Enrollment or a specific Course Enrollment.

The Advisee Case Lightning Page is the Advisor’s primary user interface for a

student. This page is entirely customizable, but the installed version has several dependencies on

EDA.

• The Contact Panel (a custom SAL Lightning Component) can include a student’s Primary

Academic Program (e.g. B.S. Mathematics) and the Graduation year. This data comes from EDA

fields on Contact and Program Enrollment.

• The other tabs on the student record show all the other important student data provided by

EDA. Affiliations with academic departments, relationships with other students, faculty and

alumni, seasonal addresses, course grades and overall GPA. These tabs and related information

can be customized to show more or less EDA-delivered data and can also include other non-

EDA records implemented by a customer.

Data Automation (TDTM)

• Table Driven Trigger Management is the automation engine that drives EDA. It makes sure all

facets of the EDA data model stay in sync so information is accessible from multiple views.

• TDTM is extendable, so other solutions (like SAL) can use the same automation features used by

EDA. SAL does just that: extending TDTM to perform additional data validation on the Advisee

Case and Alerts.