Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 6 Next »

Draft - In progress

ITS Admin Message Specs

*** VALUES FOR "role" ***
    staff
    studentEmployee

*** SUBAFFILIATION MESSAGES ***
add would be coming into a new position or reactivated (
delete would be leaving ITS 
refresh would be changing the phone number/office locations/, i.e if at the same position

can a ITS person have multiple affiliations?





affiliation(json data specs, not a message)



uhUuidnon-empty


affIDnon-empty


orgHierarchynon-empty


rolenon-empty


officeLocationoptional


phonesAsEnteredoptional


faxesAsEnteredoptional












Employee (Staff & Student)

ROUTING KEY: affiliation.add.{role}.{orgRootCode}.{any-middle-org-codes}.{orgLeafCode} (account for periods in role values)
affiliation.add.staff.ES.ES-1
affiliation.add.staff.ES.ES-2
   {
      "addAffiliation" : {
         "messageData" : {
            "uhUuid" : "12345678",
			"affID" : (check UHIMS - use perspositionID)
            "orgHierarchy" : [
               {
                  "code" : "TI",
                  "description" : "Technical Infrastructure"
               },
               {
                  "code" : "TI-SYS",
                  "description" : "TI - Systems Services"
               },
               {
                  "code" : "TI-SYS-MID",
                  "description" : "TI-SYS-MID"
               }               
            ],
		    "role" : "staff",
possibly a list
		    "officeLocation" : [
			{"building"
			"floor"
			"cubicle"}]
look at UHIMS phones / list of "phone" (ask Dana where she updates the phone number - does she update ITSADMIN and WPMS)
		    "phonesAsEntered" : "(808) 555-9128",
		    "faxesAsEntered" : "(808) 555-9130"
         }
      }
   }


ROUTING KEY: subAffiliation.modify.itsadmin.{orgRootCode}.{any-middle-org-codes}.{orgLeafCode}.{role} (account for periods in role values) 
keep message to affiliation.modify.staff and provide what has changed
messageDataBefore
publisher confirm
onAck means that it was published

   {
      "modifyAffiliation" : {
         "messageData" : {
            "uhUuid" : "12345678", required
			"affID" : required
            "orgHierarchy" : [
               {
                  "code" : "TI",
                  "description" : "Technical Infrastructure"
               },
               {
                  "code" : "TI-SYS",
                  "description" : "TI - Systems Services"
               },
               {
                  "code" : "TI-SYS-MID",
                  "description" : "TI-SYS-MID"
               }               
            ]
		    "role" : "staff.noDetails",
		    "beginDate" : "2015-12-25",
		    "endDate" : "",
		    "officeLocation" : "ITC-Floor 6 / 602",
		    "phonesAsEntered" : "(808) 555-9128",
		    "faxesAsEntered" : "(808) 555-9130"
         }
      }
   }
ROUTING KEY: subAffiliation.delete.itsadmin.{orgRootCode}.{any-middle-org-codes}.{orgLeafCode}.{role} (account for periods in role values) 
provide everything that we provide for the add
   {
      "deleteSubAffiliation" : {
         "messageData" : {
            "uhUuid" : "12345678",
            "orgHierarchy" : [
               {
                  "code" : "TI",
                  "description" : "Technical Infrastructure"
               },
               {
                  "code" : "TI-SYS",
                  "description" : "TI - Systems Services"
               },
               {
                  "code" : "TI-SYS-MID",
                  "description" : "TI-SYS-MID"
               }               
            ]
		    "role" : "staff"
         }
      }
   }
  • No labels