Notes
In this sprint, we completed the changes we talked about last time regarding performance improvements to the funding validation endpoint. We’re now using an internal cache for some validation data, which is considerably faster than other methods. You should see noticeable improvements when validating funding.
Filters on certain attributes are now more flexible: when filtering on names, you can use the prefixes STARTS_WITH:, CONTAINS:, or ENDS_WITH: with your filter parameters to get matches based on only part of the name. When filtering on dttmLoaded (that’s when a record was last changed in our cache), you can use GREATER_OR_EQUAL:, GREATER_THAN:, LESS_OR_EQUAL:, and LESS_THAN: prefixes to get matches based on a range of dates. This should be especially useful for periodic update processes that only need to know about the records that have changed since the last sync.
There’s now a process for marking records as deleted from our source data, which will be important when we start using more recent data from the new Workday tenant. If you have full links to particular resources bookmarked or stored, they may not be accessible anymore, although this shouldn’t affect many records.
API Changes
- You can now use fuzzy matching prefixes when filtering on
nameanddttmLoaded - Records are marked as deleted and removed from query results if they’re no longer in the source data