Notes
A couple of our team members have been assisting in recruitments that ended up being larger than anyone thought, so we had reduced capacity this sprint. Nonetheless, we’ve been working on an endpoint for validating FDM combinations. This is separate from the existing accounting journal validation endpoint, so you can use this one to validate FDM combos from any source. This will confirm whether those worktags can be used together. This won’t include any validations performed within Workday itself or custom validations, so you would most likely use this as one part of a larger process. We’re going to gather some feedback on the specification before we publish this for everyone.
We’ve also finished converting our ETL process to pull data from Workday reports rather than the native API. This will give us the ability to expand on the data we receive, so we’ll be able to offer new features to API users. It also puts us in closer alignment with the proposed services that will exist in the EAP data lake.
In the near future, we’ll be partnering with the ASP IICS team to deliver some automated validation for budget amendments. For anyone who’s not able to use the API directly, IICS (Informatica Intelligent Cloud Services) may be an option for connecting your data processes together.
We’re also working closely with EAP on the future data lake. This will eventually be a critical part of the UW data integration ecosystem, so we want to make sure our interests are represented there.
API changes
No public-facing changes this sprint.