Notes
We made some progress this sprint on a new endpoint for representing cost center hierarchies, as mentioned in our previous review. We showed some of the data we’ll be returning, though it’s not in its final form yet. It’s not quite ready for use, but we’ll have that by our next review. Cost center hierarchies have dense interrelations that make some common query types run slower than we’d like, so we’re looking at ways to mitigate that before we release anything. More to come next time!
We also reviewed where we’re at with budget amendment validation. We’re currently waiting for some extra permissions to allow us to get the results of an amendment run in validation mode. The relevant Workday endpoints work a little different than others, in that they run asynchronously: you submit an amendment for validation, and instead of waiting for a result, you get a confirmation that the job is being processed. You then need to check in on that job’s status to see if your results are ready. That pattern would be difficult for IICS users to implement, so we’re hoping to insulate you from that detail and make our endpoint work just like the others.
We’ve started work on a new customer resource that will represent external customers of UW services. Our Assetworks users would like to pull this data into their own systems. We’ve done the initial data modeling and have a request in for the new data.
API Changes
No user-facing changes this sprint.