Top of ADM | Index | Table of Contents | Feedback |
ADMF5600 - Maintain Applicant Portal Person Match Details
Purpose |
This form displays the results of matches found between the applicant record and existing Callista Person records as identified by the transfer process and based on the results of an institution-defined function. |
||
Subsystem | Admissions | ||
Normally Run By | Admissions Specialist | ||
Anticipated Frequency |
As required |
||
Structure |
Blocks |
Applicant |
|
Person Match | |||
Buttons |
Find Applicant (ADMF5010) |
||
Applicant (ADMF5100) | |||
Find Person (ADMF1211) | |||
Alternate Person ID (ENRF3010) | |||
Person Alias (ENRF3020) |
This form displays the results of matches found between the applicant record and existing Callista Person records as identified by the transfer process and based on the results of an institution-defined function. The matching routine is open sourced and allows the institution to define the exact matching criteria to employ. If matches are identified, they are recorded against the applicant record in this form. The administrator is able to open this form in context of an applicant from the View Applicant Summary function. If the transfer process has identified a possible match between the applicant and existing Callista person records, the administrator can nominate one of these person records as a definitive match. If a definitive match has been nominated in this form, the transfer process updates the nominated person with the new application details, rather than creating a new record. Only one person record can be nominated as the definitive match with the applicant. To record the person record as the definitive match, the administrator assigns a duplicate person status to the record that is then mapped to a system status of CONFIRMED. For each of the person match records displayed in this form, a Find Person (ADMF1211) button is available. This allows the user to view more specific details of the person if required. It will not, however, allow the user to change the person record to which the applicant record is matched. Person matches are identified by the transfer process and it is not possible for an administrator to insert a person match record. |
The Applicant block contains:
The Person Match block contains:
|
Rules/Notes: The Applicant Block The Find Applicant button is only enabled in Query mode. A lamp showing the applicant's previous surname is displayed above the name field if the applicant recorded a 'previous surname' in Applicant Portal (APAPPDTL - Record Other Person Details). The Applicant button is not available when querying records. The Person Match Block It is possible for the user to query in ADMF1211 and bring back a new Person ID. However, the Person ID field cannot be updated. The standard 'Cannot update field' message will display. The Alternate Person button is disabled when no Alternate Person ID record exists for the person. The Person Alias button is disabled when no Person Alias exists for the person. Only the Person Match Status field and Comments field are updateable. Validations include:
See the Introduction (above) on what to do when a 'perfect match' is found. |
Last Modified on 11 October, 2006
History Information
Release Information | Project | Change to Document |
17.1 | 2055 - Gender Diversity | Changed 'Sex' field label to 'Gender'. |
12.0 | 1457 - eAdmissions - Applicant Portal - Part 4 | New button and lamp added.
|
9.1.0.0.0.0 | 1221 - eAdmissions - Applicant Portal 2 | New form |