A third-party app is a solution that the consultant can recommend to meet therequirement of electronically sending, and also printing and mailing scholarship and program admission decisions on a preformatted letter template. A third-party app is an application that provides additional features and solutions for Salesforce. There are many third-party apps on the AppExchange that offer document generation and delivery capabilities, such as creating letters, invoices, contracts, or proposals, and sending them via email or postal mail. The consultant can help the International Studies office choose an app that meets their needs and budget. Salesforce reports, Salesforce Files, and Extended Mail Merge are not solutions that can electronically send, and also print and mail scholarship and program admission decisions on a preformatted letter template. References:

https://appexchange.salesforce.com/appxStore?type=App & keyword=document%20generation

https://trailhead.salesforce.com/en/content/learn/modules/appexchange_basics

Single Sign-On (SSO) is an identity management feature that allows users to log in to Salesforce using their university login credentials. SSOsimplifies the login process and reduces the need for multiple passwords. Named Credentials, Two-factor Authentication, and Social Sign-On are not identity management features that allow users to use their university login when accessing Salesforce. References:

https://help.salesforce.com/s/articleView?id=sf.identity_sso.htm & type=5

https://trailhead.salesforce.com/en/content/learn/modules/identity_basics/identity_basics_sso

The first step that the consultantshould take when integrating Salesforce with the Student Information System (SIS) is to identify the integration layers, which are the components that define how data is exchanged between the systems, such as the data model, the data format, the data transport, and the data security. This will help the consultant understand the scope and complexity of the integration project and choose the appropriate tools and methods. Disabling Trigger Handler records and using the Data Import Wizard are steps that can betaken later in the project execution or testing phase, not initially. References:

https://trailhead.salesforce.com/en/content/learn/modules/education-cloud-basics/education-cloud-integrations

https://help.salesforce.com/s/articleView?id=sf.data_loader_disable_triggers_workflow.htm & type=5

https://help.salesforce.com/s/articleView?id=sf.data_importer.htm & type=5

The consultant should package the customizations, refresh the sandbox, and reinstall the customization as the first step to avoid any issues when deploying from a sandbox environment that is a different versionfrom the production org. Packaging the customizations means creating an unmanaged package that contains all the components and metadata that are part of the custom solution. Refreshing the sandbox means creating a new copy of the sandbox environment fromthe production org. Reinstalling the customization means installing the unmanaged package into the refreshed sandbox environment. This step can help avoid any issues that may arise from deploying from a sandbox environment that is a different version fromthe production org, such as compatibility errors, missing dependencies, or data loss. Manually updating the production org by installing the release update from GitHub, submitting a case to Salesforce Support to update the production org, or deploying thecustomizations into the production org via change sets are not steps that the consultant should take first to avoid any issues when deploying from a sandbox environment that is a different version from the production org. References:

https://help.salesforce.com/s/articleView?id=sf.packaging_overview.htm & type=5

https://help.salesforce.com/s/articleView?id=sf.data_sandbox_create.htm & type=5

https://trailhead.salesforce.com/en/content/learn/modules/application-lifecycle-and-development-models/test-your-applications

The consultant should recommend that the program coordinator should be a Salesforce power user for the small college that plans to use Salesforce for its student services and has a part-time system admin who has been working with a program coordinator who has previous Salesforce experience and is eager to work on the project. A Salesforce power user is a user who has advanced knowledge and skills in using Salesforce and can perform tasks such as creating reports, dashboards, or workflows. The program coordinator should be a Salesforce power user for the small college that plans to use Salesforce for its student services and has a part-time system admin who has been working with a program coordinator whohas previous Salesforce experience and is eager to work on the project by leveraging their Salesforce experience and eagerness to work on the project to support the part-time system admin and contribute to the project’s success. The program coordinator should not be assigned the System Admin profile, the program coordinator’s role should not be on top of the role hierarchy, or the program coordinator should not be a Salesforce end user for the small college that plans to use Salesforce for its student services and has a part-time system admin who has been working with a program coordinator who has previous Salesforce experience and is eager to work on the project. References:

https://trailhead.salesforce.com/en/content/learn/modules/salesforce_users_roles_and_permissions

https://www.salesforce.org/wp-content/uploads/2019/03/Education_Cloud_COE_Guide.pdf

The consultant should recommend to disable address-related Trigger Handler records for the university thatuses EDA to manage its prospective and current students and has the student Contact Mailing Address fields and records populated in Salesforce through an integration with an external system. Trigger Handler records are records that control the behavior ofEDA triggers and can be disabled or enabled as needed. Disabling address-related Trigger Handler records can help prevent duplicate or conflicting address records from being created or updated by EDA when the student Contact Mailing Address fields and records are populated in Salesforce through an integration with an external system. Disabling all EDA and custom Trigger Handler records, setting record-level trigger firing based on the Account record type, or setting the Default Account Model to Administrative are not recommendations for the university that uses EDA to manage its prospective and current students and has the student Contact Mailing Address fields and records populated in Salesforce through an integration with an external system. References:

https://powerofus.force.com/s/article/EDA-TDTM

https://powerofus.force.com/s/article/EDA-Addresses

The consultant should configure a security setting to create a Program Plan sharing rule to provide Read access based on record type for the system admin who wants to use the recommended setup for external users when implementing Student Success Hub and Pathways in a new org for the Undergraduate Advising department. A sharing rule is a security setting that allows users to extend sharing access to users in public groups, roles, or territories. A Program Plan sharing rule can help the system admin provide Read access to external users based on record type by granting access to specific Program Plan recordsthat are relevant or appropriate for external users, such as students or advisors. Creating an Account sharing rule to provide Read access based on record type, changing the default Program Plan sharing setting to Private, or creating a custom PermissionSet for external users are not security settings that the consultant should configure for the system admin who wants to use the recommended setup for external users when implementing Student Success Hub and Pathways in a new org for the Undergraduate Advising department. References:

https://help.salesforce.com/s/articleView?id=sf.sharing_overview.htm & type=5

https://powerofus.force.com/s/article/SSHub-Pathways

Data Integration and Analysis:

Data Cloud(formerly known as Salesforce Customer 360 Data Manager) is designed for ingesting, harmonizing, and analyzing data from multiplesources.

It provides a centralized platform to manage batch data from Education Cloud and other systems.

Capabilities of Data Cloud:

Data Ingestion: Ability to import data from various sources including Education Cloud, ERP systems, and other databases.

Data Harmonization: Standardizes and merges data to create a unified view.

Data Analysis: Offers tools to analyze and visualize the harmonized data for insights.

Implementation Steps:

Enable Data Cloud: Work with Salesforce support to enable Data Cloud for your org.

Configure Data Sources: Set up connections to the various data sources.

Define Data Models: Create data models to harmonize data from different systems.

Setup Data Integration: Configure data integration processes to regularly ingest and update data.

Analyze Data: Use Data Cloud's analytics tools to generate insights from the unified data.

Using OmniStudio FlexCard:

OmniStudio FlexCardcan be used to create a dynamicuser interface that displays the application data in a structured format. This can include conditional logic to show or hide fields based on the submission status of the application.

Applying Validation Rule:

Avalidation rulecan be used to enforce that applications cannot be edited after the submission deadline. This ensures data integrity by preventing changes to the application record once the deadline has passed.

Steps to Implement:

Create a FlexCard:

Navigate toOmniStudio > FlexCards.

Create a new FlexCard that displays application details and includes logic to disable editing past the deadline.

Set Up Validation Rule:

Go toSetup > Object Manager > Application Object.

Create a validation rule to check if the current date is past the submissiondeadline and prevent edits.

Example validation rule:AND(ISCHANGED([Application].Status), [Application] .Status = 'Submitted', TODAY() > [Application].Submission_Deadline__c)

Testing:

Test the FlexCard and validation rule to ensure that students cannot edittheir applications after the submission deadline.

Ensure the user interface and validation rule work seamlessly together to provide a smooth user experience.

The consultant should recommend an app on the AppExchange to create a declaratively configured, public-facing form that createsdata in Salesforce, such as FormAssembly or Formstack, which are web form builders that integrate with Salesforce. Process Builder is a tool that automates business processes based on certain criteria or actions, not a form builder. Email-to-case is a feature that converts emails from customers into cases in Salesforce, not a form builder. References:

https://appexchange.salesforce.com/appxStore?type=Product & keywords=form

https://help.salesforce.com/s/articleView?id=sf.process_overview.htm & type=5