What we’ll cover:
Applicable Roles:
-
HR Connect Administrator
Before getting started:
As of October 2022, we allow changes to Unit and Title in order to match the UI functionality. For more information, please watch this video explaining the changes.
Quick Reference Links:
Getting Started with Primary Internal Association Scenarios
Overview of Changes
If Primary Internal Association = True
- If there is an existing Primary record, the Primary record will be updated regardless of whether or not it’s an exact match on the Unit Primary Code and Title. The existing ID will remain. Which means, as long as the Primary Appointment field = Yes, the existing Primary record can be updated with a new Title.
-
If there is an existing non-Primary record that is the same as the new Primary appointment, the secondary (non-Primary) will become a Primary appointment and all sub-resources (contact, distributions, etc.) will remain attached.
- In this scenario, if there’s an existing Primary record, it will become a non-Primary secondary appointment.
- If there is not an existing Primary record, a new one will be created.
If Primary = False (Non-Primary additional Internal Association)
- The existing logic will be maintained for non-Primary Internal Associations, whereas the Unit and Title must match exactly in order for the Internal Association to be updated.
- The existing logic will be maintained for non-Primary Internal Associations, whereas if there is not an exact match on the non-Primary Internal Association then a new additional Internal Association record (second, or third, etc.) will be created.
HR Connect Upload Scenarios
Scenario #1
|
Scenario Pre-conditions: |
The person does not have any existing Appointments. |
|
Scenario Description: |
Uploading a new Appointment A (Unit A + Title A + Primary = Yes) and non-Primary B (Unit B + Title B + Primary = No) to a Person who does not have any Appointments. |
|
Expected Behavior: |
Appointment A (as Primary) and Appointment B (as non-Primary) uploads successfully. |
Scenario #2
|
Scenario Pre-conditions: |
The person already has Primary Appointment A and non-Primary Appointment B. |
|
Scenario Description: |
Updating appointment details (contact info, performance site etc.) for PrimaryAppointment A (Unit A + Title A + Primary = Yes) and non-Primary Appointment B (Unit B + Title B + Primary = No). |
|
Expected Behavior: |
Appointment A (as Primary) and Appointment B (as non-Primary) updates successfully. |
Scenario #3
|
Scenario Pre-conditions: |
The person already has Primary Appointment A and non-Primary Appointment B. |
|
Scenario Description: |
Update Unit of an existing Primary Appointment: Uploading a CSV file for a new Appointment C (Unit C + Title A + Primary = Yes) along with some updates for other sections (contact info, performance site, etc.) that are different from the existing Primary Appointment A. |
|
Expected Behavior: |
Existing Primary Appointment A’s Unit changes to Unit C and remains as Primary, the other section's data also updates successfully. The person should now have two records, B as non-Primary and C as Primary. |
Scenario #4
|
Scenario Pre-conditions: |
The person already has Primary Appointment A and non-Primary Appointment B. |
|
Scenario Description: |
Update Unit and Title of an existing PrimaryAppointment: Uploading a CSV file with a new Appointment C (Unit C + Title C + Primary = Yes) along with some updates for other sections (contact info, performance site, etc.) that are different from the existing Primary Appointment A. |
|
Expected Behavior: |
Existing Primary Appointment A’s Unit and title changes to Unit C, Title C and remains as Primary, the other section's data also updates successfully. The person should now have 2 records, B as non-Primary and C as Primary. |
Scenario #5
|
Scenario Pre-conditions: |
The person already has Primary Appointment A and non-Primary Appointment B. |
|
Scenario Description: |
Swap an existing non-PrimaryAppointment with existing PrimaryAppointment: Uploading a CSV file with Appointment B as Primary (Unit B + Title B + Primary = Yes) along with some updates for other sections (contact info, performance site, etc.) that are different from the existing Appointment B. |
|
Expected Behavior: |
It swaps the PrimaryAppointment from A to B. Appointment B is now Primary, and A is non-Primary. The other section's data also updates successfully. |
Scenario #6
|
Scenario Pre-conditions: |
The person already has two non-Primary Appointments, Appointment A and Appointment B. |
|
Scenario Description: |
Updating an existing non-Primary Appointment as PrimaryAppointment: Uploading a CSV file with Appointment B as Primary (Unit B + Title B + Primary = Yes), along with some updates for other sections (contact info, performance site, etc.) that are different from existing Appointment B. |
|
Expected Behavior: |
Appointment B should be the PrimaryAppointment along with other section updates. |
Scenario #7
|
Scenario Pre-conditions: |
The person already has Primary Appointment A and non-Primary Appointment B. |
|
Scenario Description: |
Add a new non-Primary Appointment while some other Appointments already exist: Uploading a CSV file with a new Appointment C (Unit C + Title C + Primary= No) with additional section detail updates. |
|
Expected Behavior: |
New Appointment C gets added as non-Primary along with other details. Existing Appointments A and B remain as they are. |
Scenario #8
|
Scenario Pre-conditions: |
The person already has Primary Appointment A and non-Primary Appointment B. |
|
Scenario Description: |
Update existing Primary Appointment as non-Primary: Uploading a CSV file with an Appointment A (Unit A + Title A + Primary = No) with additional section details that are different from an existing Appointment A. |
|
Expected Behavior: |
Appointment A should now be updated as a non-PrimaryAppointment along with other section updates. |
Scenario #9
|
Scenario Pre-condition: |
The person already had an Appointment A (Unit A + Title A) or did not had any appointment |
|
Scenario Description: |
When the user tries to upload Appointment A (Unit A+Title A) twice, with one Primary upload and one non-Primary upload, meaning the input CSV file has two records for Appointment A (Unit A + Title A). |
|
Expected Behavior: |
Records will fail to upload. Error message shown in the report would be "There is a primary and non-primary appointment for the same unit and title" |
Scenario #10
|
Scenario Pre-condition: |
The person already had an Appointment A (Unit A + Title A) or did not had any appointment |
|
Scenario Description: |
When the user tries to upload two primary appointments for a person |
|
Expected Behavior: |
Records will fail to upload. Error message shown in the report would be "There must only be one primary appointment for the same person" |