Release notes: Sprint 75

Notes

Notice: We’re aware of some ongoing issues with the accuracy of the responses from the FDM validation endpoint. This is due to a few problems getting data out of Workday, through the data lake, and into the API’s product datastore. We’ve identified the causes of these problems and are working with the appropriate teams to sort them out.

Another notice: We’ve increased the frequency of our ETL runs. Data is still only exported from Workday once a day, Monday through Friday, but this increase may mean you can run your own scheduled processes earlier in the day:

  • If you’re only interested in FDM data (INT027), we’ll load that data at 4am, so you can run your own integrations against the API by 4:15am
  • All other data should be available by 7:15am

You can now filter journal entry lines by a date range, similar to what you could already do with journal entries. We’ve also added a number of columns to the responses for both journal entries and journal entry lines. All FDM worktags referred to now have the ID and name split into separate columns.

We also made some tweaks to the initial responses from the journal endpoints so that they’re fully compliant with JSON:API specifications. This should help anyone who’s using a library to parse that data.

We created some internal documentation of our AWS infrastructure, and we completed a number of security maintenance tasks. We also fixed a bug with the ancestorOf filter on the hierarchies endpoint and it now returns the correct records for that query.

API changes

  • start_date and end_date filter parameters for journal entry line queries
  • Journal endpoint responses now include a data block with ID and type for JSON:API compliance
  • New columns in journal entry data:
    • award_id
    • award_name
    • cost_center_id
    • cost_center_name
    • function_id
    • function_name
    • fund_id
    • fund_name
    • gift_id
    • gift_name
    • grant_id
    • grant_name
    • interworktag_affiliate_id
    • interworktag_affiliate_name
    • ledger_account_id
    • ledger_account_name
    • program_id
    • program_name
    • project_id
    • project_name
    • revenue_category_id
    • revenue_category_name
    • spend_category_id
    • spend_category_name
  • New columns in journal entry line data:
    • activity_name
    • award_name
    • cost_center_name
    • function_name
    • fund_name
    • gift_name
    • grant_name
    • ledger_account_name
    • program_name
    • project_name
    • revenue_category_name
    • spend_category_name

Recording

ASP API Sprint 75 Recording