#K-12 Architecture Kit0 人正在讨论

With some exciting changes coming for EDA Settings in our Summer release, we sent an email out to all the EDA Admins. As another avenue for communication, I have pasted the content of that email below. Please, feel free to use the thread to ask any questions you may have. We are very excited about this release and the improved experience we are delivering with Education Data Architecture.

***

In the Summer ’21 release, coming to sandboxes starting on July 1 and production starting July 13, EDA will be making two important changes: deprecating the EDA managed classic app and delivering a new settings design.

The future of Salesforce is on Lightning and all new innovation is solely in Lightning. To bring customers the best experience on the platform, the Education Data Architecture is embracing this exciting future. Starting in the Summer ’21 release, all new installs of EDA will come with an EDA Lightning app. Current customers who have been using the classic EDA app will need to create their own EDA Lightning app.

The current EDA Settings page is being retired and will be replaced with a new design, including a new landing page called Education Cloud Settings. After the Summer ’21 release, the old settings page will display a message that includes a link to the EDA documentation with instructions on how to configure the new Education Cloud Settings.

The Summer ’21 release will include updated documentation that describes these changes and how to configure EDA to use the new settings experience.

What does this mean for my org?

• The EDA Settings feature is for System Administrators and is not recommended for users with other profiles. System Administrators who require access to EDA Settings are required to use the Lightning Experience.
• With this change, System Administrators will navigate to the new EDA Settings UI from the Education Cloud Settings tab, which must be added to a Lightning app. System Administrators can also access the new UI from the App Launcher, but will not get access to the functionality provided by the Education Cloud Settings tab.

What do I need to do after Summer release?

Customers who are already using a Lightning App will need to add the Education Cloud Settings tab to an existing Lightning App. Customers how are not using a Lightning App for EDA will need to follow instructions in the EDA documentation to create the Education Data Architecture Lightning App, grant App access to user profiles, and enable new Apex classes. Full instructions will be provided in the Summer ’21 release documentation.

What happens if I don’t take action?

Our new Education Cloud Settings tab does require a Lightning app. If you do not have a Lightning app you cannot add this tab to it and will only reach our settings from the App Launcher.

How do I learn more about the Lightning Experience?

To learn more about transitioning to the Lightning Experience, check out the Journey to Lightning Experience site or the Successfully Rolling Out the Lightning Experience Guide. A multi-week Lightning Transition engagement for Higher Ed kicks off Monday, June 28. For more information or to register, click here.

***

Hello Community!

We are evaluating if we should use a single record type for contacts for the entire life cycle of the student from recruitment, success, alumni and donations/advancement or use many.

We started with the high school and university recruitment process 5 years ago, however we have grown in Salesforce and now we have more processes such as advancement, student success, 360, continuing education, etc. Also this year we will include recruitment and admissions of postgraduates, masters, etc.

Our analysis starts to complicate when we think about an active high school student can be a college candidate and the same is true of a graduate college student. It can also happen that a former student requires a master's degree or that an employee is a former student and in turn a candidate for a master's degree. There are many combinations and many departments inside our institution that can share student information at the same time.

One idea is to use a single record type on contact, but on other objects such as opportunities, applications and others utilizing more record types. We are also using a custom field called “Role” that is a multipicklist where a contact can have N profiles such as career candidate, active student, employee, high school alumni, etc.

What do you think? Any best practice or something to take into account in the decision?

Thank you so much