Page Comparison

...

• UHIMS Events - Message Specs
• Note that <messageRoutingKey> in the above specs is not an actual XML tag. It represents the message routing key for the message being described.
• History
  • 7/17/2013 5pm HST

    • Adds <uids> to every message where <uhUuid> is the key, e.g

      No Format
      <addContactInfo> <messageData> <uhUuid> 00000000 </uhUuid> <uids> <uid> jsmith </uid> </uids> ...

      • This is useful for apps that use the UH Username as the key identifier.
      • It lists all usernames a person has at the time of the message. Most people should have only one username, but it is not impossible to see multiple usernames.
      • <uids> is skipped if the person does not have any usernames
      • <uids> is not included in username messages (addUsername, modifyUsername*, deleteUsername) because their key is a single <uid>.
  • 1/23/2013 5pm HST
    • Adds optional <displayName> to <addPerson> and <retrofitPerson>
    • Adds a new value to <role>, staff.executive.overload, its roleCategory in message routing key is staff)
    • Deleted references to date of birth and SSN because they are not usually included:
      • Deleted <modifyPersonSsn>
      • Deleted <modifyPersonDob>
      • Deleted <dob>
  • 8/14/2012 5pm HST
    • includes retrofit messages

...

To request access to UHIMS Events, refer to Consuming UHIMS Events

Reading UHIMS Events

See Consuming UHIMS Events

...