Notes
This sprint we un-stuck our issues with configuring our new Locations API for parallel local development. This means we’ll be able to take on a few Locations features in our upcoming sprint. We also loosened the filter requirements on the journal lines endpoint: previously, you always had to include a cost center, but now you can use any kind of FDM worktag to filter your results, and no cost center is needed. You can also filter for multiple cost centers in a single request.
We encountered some troubles in setting up new integrations to post messages to MS Teams channels. We use this as part of our notification process if something goes wrong in our ETL. Our existing integrations work correctly, but they’re due to be EOL’d at the end of the month, so we’re looking at setting up new ones that use the new Workflows in Teams.
We finished our task to pin dependency versions to help avoid surprises when dependencies upgrade. We’ve experienced this a couple of times in the past. We also completed our MySQL upgrade and gotten all our databases on the most recent long term service version.
A programming note: our next sprint will be four weeks long instead of the usual two. Our next sprint review will be on Tuesday, Jan. 6. See you then!
API changes
- Journal entry line filters no longer require a cost center ID. Instead, they require at least one FDM worktag ID, which could be a cost center, but could be something else too (programs, projects, etc.)