Notes
We started with a short review of how the cutover dress rehearsal went for us:
- On March 3, we stopped getting new data delivered. We continued to deliver the old data using a snapshot of its last state.
- On March 5, new data started arriving. We updated API endpoints as the data came in.
- By 8am on March 6, all the data we source directly from Workday reports was loaded.
- By 6pm on March 7, all data from EAP was loaded.
We found one bug with how programs were getting their companies assigned, but ATP staff were up late into the night fixing it and it was sorted out by the next morning. Big thanks to everyone who helped out: Maria Lindquist, Jen VanTassel, Helen Linderoth, Thomas Osmanski, Akhila Reddy, and Sowmya Shankar!
Since our data sources weren’t consistently available due to the rehearsal, we focused mostly on internal updates that didn’t have any external dependencies. We refactored the logic behind our FDM validation endpoint and added a few new error codes for mismatches between specific elements of a combo. We converted our ETL for activities to use EAP data, and we added ETL for a forthcoming new purchase orders endpoint.
We’d previously been inconsistent in whether or not we abbreviated the term “principal investigator,” but we’ve now settled on abbreviating it as “pi” in the names of attributes for driver worktags. We added a number of new attributes to sales items, and we developed some new logging and analytics to deepen our own picture of how people are using the API.
API Changes
- New attributes for sales items: active, itemIdentifier, and taxStatus.
- Slashes in sales item IDs are now supported
- Validation error codes FDM314, FDM315, and FDM316 deprecated. These will no longer be used.
- New validation error codes FDM318, FDM319, FDM320, and FDM321 for bad combinations of company with a gift, grant, program, or project.
- Gifts, grants, programs, and projects now all use piName and piId for principal investigator attributes.