Candidates & Prospects
The Candidates and Prospects consists of features accessible from any web-enabled device and allows better communication and service between persons with Candidate roles and J1 Desktop.
When submitted, online application data is mapped to the J1 Desktop database and is available for processing.
Online application forms can be customized to meet the unique needs of your academic programs.
Candidates have online access to their admissions folders, which allows them to see the status of their applications and to update their information.
Candidates can participate in chat areas, forums, and email messages.
Quick Links
If your institution is licensed for Candidates and Prospect features, the following are available for your use:
There are three types of setup for the Candidates and Prospects feature.
Candidates and Prospects Feature Setup
Verify or create ID numbers (Name Entity and Users windows) for users who need to access Candidates and Prospect features.
Verify or configure JICS Base and JICS CAND to Y (Maintain Config Table window).
Verify or create appropriate Candidates and Prospect roles to which users can be assigned (Role Definition window).
Define candidacy stages that create JICS logins for candidates (Stage Definition window).
Assign users to the Candidates and Prospects roles. This can be done manually through the Role Membership window in J1 Desktop or automatically during the Stage Change process, depending on the stage configuration.
Grant Campus Portal roles access to the Candidates and Prospects page to allow users assigned to those roles access to the features (Admin Toolbar > Access; may vary according to your portal setup).
Verify or create a Campus Portal login and password for each Candidate. This can be done manually through the Maintain Web Access Code window in J1 Desktop or automatically via a candidacy stage change to a stage that is configured to create a new Campus Portal login.
Set configurations for the New Account Messaging feature (New Account Messaging > Setup).
Ensure that each J1 Desktop user who needs to receive an email notification that a submission has been received has an email address for notifications (Name Entity window).
Place the features on a page, and configure each feature in the required Candidates and Prospect features (Admin Toolbar > Options > Add a new feature to this page).
Enter the appropriate setup values in J1 Desktop.
Grant Campus Portal roles global access to features that appear on the Candidates and Prospects page and may also appear on other Campus Portal pages (Admin Toolbar > Access; may vary according to your portal setup).
Candidates and Prospects Feature Setup
Select the stages in J1 Desktop that will be used to automatically create a Campus Portal login for a candidate. The Edit Stage Configuration window allows you to define which candidacy stages push Candidate logins to Campus Portal through the DIS and create the Candidate role.
In J1 Desktop, open the Stage Definition window.
Locate the appropriate stage, right-click and choose Edit Stage Config (or double-click the row) to open the Edit Stage Configuration window.
For the Candidate J1 Portal Account option, select the Create radio button to indicate that a candidate moving into this stage should have a Campus Portal login and the Candidate role created if the candidate does not already have one defined.
Note
Select the No Change radio button for a stage if the stage should not create or delete a Campus Portal login or the Candidate role for a candidate at the selected stage. Additionally, if the candidate should be removed from the Candidate role (i.e., the candidate has withdrawn his/her application), select the Delete radio button. The Delete option does not remove the login from Campus Portal but that it only removes the login from the Candidate role.
Click the OK button.
Click Yes or No when the confirmation message appears.
Note
Clicking Yes retrieves the list of candidates currently at that stage and automatically creates a J1 Portal ID and puts them into the Candidate role as needed.
Clicking No does not update any existing candidates at that stage, but a Campus Portal login and role are created for any candidates who are moved into the specified stage in the future.
Repeat steps 2-5 for any other stage that should create a Campus Portal login for a candidate when the candidate reaches the stage.