Interfacing with Common App

Preventing Students from Submitting Other Applications 

By default, the application widget in the Applicant Dashboard and Portal will offer students the option to start a new application if you use the TargetX Online Application in your CRM. This can be hidden for students who apply via the Common Application, but remember that the method differs for the Applicant Dashboard and Portal.
 

• Hide "Start Application" on Applicant Dashboard
  • If you currently use the TargetX Online Application for some students, you must create a separate Salesforce Community dedicated to non TargetX Online Application students to hide the "Start Application" button. This is because the feature is disabled by adding custom CSS that will be applied broadly to the Community site.
  • To update the Community Theme:
    • Navigate to the "+" to access all tabs
    • Select Community Themes
    • Click to Edit the theme used for your Online Application
    • In the Custom CSS field, enter the following:

.new-app{
display:none;
}

• Hide "Start Application" on Portal
  • The Application and Application with Checklist widgets in the Online Application offer the option to hide/show the Start Application button. You can use conditional logic to display the widget conditionally. Common Application students can see a widget that hides the "Start Application" button, while other students who need access can see the option. 
    • To configure the conditional display:
      • Add a layout section to the Portal
      • Select the Widget content of App or App/Checklist 
      • Disable the "Start Application" feature by toggling it to off (shown below)
      • Add conditional logic to display the section based on application source or other available data points

Updating Application Display Label 

When students view applications in the Applicant Dashboard or Portal, a custom App Dashboard Application Label can be set to provide information regarding the application type. In the example below, you can see Common Application marked on the corresponding application.  
 

The value is stored in the TargetX_SRMb__Portal_Application_Label__c field on the Application Object. It is recommended that the value for the App Dashboard Application Label field be included in your data import file, mapped as a hardcoded value for each new application record.

This field can be updated manually or you can use a Flow to update this field with a concatenated value of the Program and Term to provide additional details.

Inviting Applicants to your Community Site 

After students have applied via a third party application, you will want to invite them to sign-in to the community site where you display their application status and checklist items.

You should create a TargetX Email Campaign to send invitations to students. In the body of your email, please include a merge field displaying the student's email address in the CRM. This will be used as their username when directed to the community site. The student must also know to click Sign Up to set up their account vs Sign In. Please consider cautioning the student to notify the school if they have a duplicate account and which account they have associated with their third-party application.

Note: You may want to run de-duplication processes before sending emails to ensure you do not have multiple contact records with the same email address, as this may cause the student to match on the wrong record and not display any submitted applications.

Accepting Enrollment Deposits 

Additional configuration is needed if you plan to accept Enrollment Deposits from third party applications.