Questions/Comments
add would be coming into a new position or reactivated, switch from student to staff
delete would be leaving ITS or leaving a position
modify would be changing the phone number/office locations/section
- need to provide the before data so folks know what's changing
can a ITS person have multiple affiliations?
- no; a database query shows that there are no active employees with multiple affiliations
Dana Hane (Unlicensed) look at UHIMS phones / list of "phone" (ask Dana where she updates the phone number - does she update ITSADMIN and WPMS)
- Dana updates both so pull this info from LDAP/UHIMS
- remove phone/fax from the messages
- fields will be static in ITS Admin
publisher confirm, onAck means that it was published
Julio Polo what is the routing key on the modifyAff if the org codes are changing? the old or the new codes?
- if the employee's section changes, send a delete and then an add message
...
Message Specifications
| affiliation | (json data specs, not a message) | |
| uhUuid | non-empty, single value | |
| affID | non-empty, single value; persPositionID | |
| orgHierarchy | optional list | |
| ||
| role | optional, single value | |
| officeLocation | optional, single object | |
| ||
| Element | Values |
|---|---|
| role |
|
| code (under orgHierarchy) |
|
| building |
|
Employee (Staff & Student)
| Code Block |
|---|
ROUTING KEY: affiliation.add.{role}.{orgRootCode}.{any-middle-org-codes}.{orgLeafCode} (account for periods in role values)
ex. affiliation.add.staff.ES.ES-1
ex. affiliation.add.student.ES.ES-2
addAffiliation
messageData
affiliation
{
"addAffiliation": {
"messageData": {
"affiliation": {
"uhUuid": "10967714",
"affID": "12345",
"orgHierarchy": [
{
"code": "ES",
"description": "Enterprise Systems"
},
{
"code": "ES-3",
"description": "ES-Software Engineering"
}
],
"role": "staff",
"officeLocation": {
"building": "ITC",
"floor": "6",
"cubicle": "615"
}
}
}
}
}
|
...