Notes
Over the weekend, the Workday tenant that supplies our data was refreshed. This means that the data in the Finance API is now based on a much more recent snapshot of Peoplesoft (taken September 13th). Your data in the API will be much closer to what you see in current state, but there will still be some differences. In particular, the recent work around restructuring cost center hierarchies to designate level 7 as the proper place for department-level groupings was still in progress when this snapshot was taken. This means that some of the cost center hierarchies you see in the API results are out of date and don’t align with the new structure. This is only temporary until the next refresh.
We presented a flowchart of the new proposed validation process for FDM combinations. Currently, the API allows any number of driver worktags to be used. In most cases, only one is allowed, but if a cost share grant is involved, there will be two. We now know enough to be able to reliably distinguish these cases, so we’ll be able to add validation to the number and type of driver worktags included in the combinations. This will be a feature in a future release.
We also discussed our progress on a new endpoint for award billing schedules. This is another part of the research administration data set we’ve been working on. We expect this endpoint will be available at the end of the next sprint.
Because we’ve recently added awards and award lines, we can start to offer new features on related endpoints. We’ve released the first of these: you can now filter grants by the award they’re linked to. You’ll need the ID of the award you’re interested in to use this filter.
A small bug in our JSON serializer led to an empty “programs” section being included in the relationships for driver worktags. Driver worktags will never have an allowed/disallowed relationship to another driver worktag, so this section was redundant. We’ve removed it from the API response.
We also spent a lot of time on internal improvements this sprint. Our codebase has been rapidly evolving over the two years that the team’s been working, and we’ve developed some leftovers from old approaches and discarded features. We’ve developed some automated analysis to help find the sections of code that aren’t needed and can be safely removed.
API changes
- Grants can be filtered by the award they’re linked to
- Empty programs section removed from relationships for driver worktags