...
Your application usually tracks people who are currently active, and . It will typically do an initial load of all active people from UHIMS, followed by ongoing synchronization via UHIMS Events. One problem with this model is that occurs when a previously inactive person becomes active, : UHIMS will not generate an <addPerson> (because person already exists in UHIMS), and your application will receive an <addAffiliation> message for a person that it has not been previously encountered by your application.
We solve this problem by generating retrofit messages that contain all data about a person. Retrofit messages are sent prior to any <addAffiliation>, <addUsername>, <addEmail> or <addContactInfo> messagemessages:
<retrofitPerson> (always)
<retrofitUsername> (if person has a username)
<retrofitEmail> (if person has email)
<retrofitContactInfo> (if person has contact info)
...