Notes
This sprint we completed the data load part of adding supplier invoices to the API as a new endpoint. The endpoint itself should be done in the next sprint.
Some users may have noticed an error with catalog items: the ‘active’ field (which is always true or false) didn’t have the right value in it. The fix for this had to move through several other teams, and it finally made its way to us. This is fixed now and the active status of catalog items is accurate.
Sales items saw a few changes:
- The
objectfield has been renamed toname, which is more descriptive of its purpose - IDs are now set from Workday reference IDs
itemIdentifiersare an optional identifier that some departments may add to their sales items in Workday
We added a new field to cost centers for the subtype from the relevant level 7 cost center. Level 7 is subdepartments, so this is the subdepartment subtype.
We continued our internal cleanup of how we’re representing data inside our own system. We’re storing and manipulating currency as decimal values, but due to the limitations of the JSON format that the API speaks, amounts like $1.10 will still appear as the more mathematical 1.1. You may need to format these values before displaying them to application users. We’re also converting some date fields that had been stored as strings to proper dates. This will let you use GREATER_THAN and LESS_THAN operators on them in filters.
We also converted another six of our ETL processes to use data from EAP instead of direct Workday data, and we built some new dashboard to help us keep an eye on response times.
API Changes
- Sales item
objectattribute renamed toname - Sales items have new IDs
- Sales items have an optional extra ID called
itemIdentifier - Cost centers have a new
cchl7Subtypeattribute