...
No | Type | Description | Jira Ticket (
| Due Date | Assignee | Comments / Status Update | ||||||||
1 | OLD-UPDATE/DELTA | Add delta logic to validate old updates |
|
|
| |||||||||
2 | Multiple-Contacts | Exception created when the contact belongs to a household account with multiple contacts. Update phone, address, employment and SAM preference to contact. |
|
|
| |||||||||
3 | ERROR | Exception created when Employment start date is null If same employment record exists with open end date - mulesoft adds an end date and changes status to ‘no longer in this position’. If an employment record does not exist, no new record is created as start date is null  Where start date is null, can we use timestamp from swift form as start date, set started on = on or before? |
|
|
| |||||||||
4 | INVALID-MOBILE | Exception created when either of AustraliaMobile or InternationalPhone is null. If AustraliaMobile AND InternationalPhone is null, skip record  If AustraliaMobile is null AND InternationalPhone is not null, update mobile = InternationalPhone  If AustraliaMobile AND InternationalPhone is not null, update mobile = AustralianMobile, Create Phone = InternationalPhone record in AlternateChannels |
|
|
| |||||||||
5 | CONTACT-NOT-FOUND | Exception created when no match found by first name + last name + email OR Studentid    What is the matching criteria used to validate matches? Can we add DOB to the existing criteria? In the instance a contact is matched by StudentID when supplied email does not exist in Jarvis, do we update new email? |
|
|
|
...