Notes
Some special announcements this time;
Special Characters in identifiers
Workday reference IDs can sometimes have special characters in them, like customer invoice AR-0001907-08/04/22. The date with the slashes is part of the ID. We can expect to see identifiers like this coming from Workday.
If you try to query the API for that ID, it fails because it interprets the slashes as part of the URL path rather than part of the ID parameter. To use IDs with special characters in them, you’ll need to URL encode them first. For example:
This fails: api.wisc.edu/finance/customerinvoices/AR-0001907-08/04/22
This works: api.wisc.edu/finance/customerinvoices/AR-0001907-08%2F04%2F22
Naming Conventions Deployed
Underscores have been removed from paths and attribute names: use camel case instead. For example: country_code is now countryCode. We have a full guide to the changed names here for your migration.
In terms of sprint accomplishments, we’ve completed our switch from Workday’s reports as a service (RaaS) to delivered static files. We requested and got a small change to the data we’re receiving for cost center hierarchies, so we no longer need to determine company by looking at parts of other fields and can instead read it directly from its own field. We’ve also updated our Hierarchies examples in the developer portal.
We’re continuing to work through access issues with EAP to move forward with our Journals endpoint MVP and have completed some internal work on our OpenAPI spec bucket security, and a more specific authorization scheme.
API changes
See the naming convention migration guide for full details.