Page Comparison

...

A person's name and UH Number.  RetrofitPerson is sent before any refreshStudentAcademicProfile or refreshInstructorAssignment message

ROUTING KEY: person.refresh

{
    "messageType":"refreshPerson",
    "transmissionDate":"2016-05-09 13:58:00",
    "bannerEventNumber": ,
    "messageBody":{
        "fullName":"",
        "firstName":"",
        "preferredFirstName":"",
        "lastName":"",
        "middleName":"",
        "nameSuffix":"",
        "uhUuid":"",
        "pidm":
    }
}

The retrofitPerson message is sent before any refreshStudentAcademicProfile or refreshInstructorAssignment message. We don't need retrofitPerson before any other type of messages because a person is either a student or faculty, and those two messages appear for a student or faculty respectively before any other type of messages (e.g. refreshStudentAcademicProfile for a student appears before any refreshStudentRegistration messages, so we don't need to send a retrofitPerson before every registration message)

ROUTING KEY: person.retrofit

{
    "messageType":"retrofitPerson",
    "transmissionDate":"2016-05-09 13:58:00",
    "bannerEventNumber": ,
    "messageBody":{
        "uhUuid":"",
        "actions":[
            {
                "messageType":"refreshPerson",
                "messageBody":{
                    "fullName":"",
                    "firstName":"",
                    "preferredFirstName":"",
                    "lastName":"",
                    "middleName":"",
                    "nameSuffix":"",
                    "uhUuid":"",
                    "pidm":
                }
            }
        ]
    }
}

...