Versions Compared

Version Old Version 10 New Version Current
Changes made by

Cameron Ahana

Cameron Ahana

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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

look at UHIMS phones / list of "phone" (ask Dana where she updates the phone number - does she update ITSADMIN and WPMS)

publisher confirm, onAck means that it was published

...

Message Specifications





affiliation(json data specs, not a message)

uhUuidnon-empty, single value

affIDnon-empty, single value; persPositionID

orgHierarchynon-empty optional list

  • code
  • description


rolenon-emptyoptional, single value

officeLocationoptional, single object

  • building
  • floor
  • cubicle
phonesAsEnteredoptional, single valuefaxesAsEnteredoptional, single value



ElementValues
role
  • staff
  • student
code (under orgHierarchy)
  • CIO
  • CIO-1
  • ADM
  • AT
  • AT-1
  • AT-2
  • AT-3
  • AT-4
  • AT-5
  • AT-SS
  • CSOC
  • CYB
  • ES
  • ES-1
  • ES-2
  • ES-3
  • ES-4
  • ES-5
  • ES-6
  • TI
  • TI-SYS
  • TI-SYS-DBA
  • TI-SYS-MID
  • TI-SYS-SAA
  • TI-DCTR
  • TI-NETWK
  • TI-PROJ
  • TI-APC
  • TI-SEC
  • TI-TEL-US
building
  • ITC
  • Kuydendall
  • Keller
  • Bilger Addition
  • Sinclair Library
  • Building 37
  • Queen Lili'uokalani Center

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"
        },
        "phonesAsEntered": "808-111-2222",
        "faxesAsEntered":
"808-101-3333"
      }
    }
  }
}


Code Block
ROUTING KEY: affiliation.modify.{role}.{orgRootCode}.{any-middle-org-codes}.{orgLeafCode} (account for periods in role values) 

modifyAffiliation
	messageData
		affiliation
	messageDataBefore
		affiliation

{
  "modifyAffiliation": {
    "messageData": {
      "affiliation": {
        "uhUuid": "10967714",
        "affID": "12345",
        "orgHierarchyofficeLocation": [
          {
            "codebuilding": "ESITC",
            "descriptionfloor": "Enterprise Systems"
          },
          {
            "code": "ES-1",
 6",
          "descriptioncubicle": "ES-PeopleSoft HR615"

         }
      
 ]       }
    },
    "messageDataBefore": {
      "affiliation": {
        "uhUuid": "10967714",
        "affID": "12345",
        "orgHierarchyofficeLocation": [
          {
            "codebuilding": "ESITC",
            "description": "Enterprise Systems"
          },
          {
            "code""floor": "ES-3",
            "descriptioncubicle": "ES-Software Engineering315"
          }
        ]
      }
    }
  }
}


Code Block
ROUTING KEY: affiliation.delete.{role}.{orgRootCode}.{any-middle-org-codes}.{orgLeafCode} (account for periods in role values) 

deleteAffiliation
	messageData
		affiliation

{
  "deleteAffiliation": {
    "messageData": {
      "affiliation": {
        "uhUuid": "10967714",
        "affID": "12345"
      }
    }
  }
}

...