Notes
In Sprint 22, we implemented some new checks on strings submitted to the funding validator. In addition to checking that the assigned worktags exist, we now also check that the combination of worktags is allowed. There are new error messages that provide details on why exactly a given combination is not considered valid.
In response to feedback received at the last sprint review, we started some preparatory work on allowing API users to filter results by when their value last changed. This could be used to help synchronize an ancillary system’s own data store with the API while eliminating redundant requests for data that hasn’t changed since the last check. More on this to come in the next sprint!
For anyone trying to connect Peoplesoft to the Finance API, we’ve prepared a tutorial showing how to connect Peoplesoft to a REST API such as our own. Note that not all steps may be required in your particular environment. The tutorial assumes you’re starting from scratch.
We’ve also created an API resource collection that can be imported into either Postman or Insomnia, two popular API exploration and testing tools. Import this collection into either program and the basic configuration for all the Finance API endpoints will be set up for you. You’ll need to have an approved application registered with the Developer Portal, and you’ll need to enter your client key and secret from there into the collection’s authorization.
API Changes
- The funding validator now performs checks for allowable combinations of worktags. Strings that were previously considered valid may now be considered invalid. More detail is provided in the error messages.