Changelog

Presage API
3/27/2026

Minor Changes

  • PA-913 - Log emails and push notifications sent by the API to allow for easier debugging of undelivered notifications

Patch Changes

  • PA-817 - Fix issue where some "Key Choice" parameters would use the "id" as the label instead of the label
  • Set the MySQL connection character set and collation to match the global character set and collation to avoid issues running queries due to mismatched collation
  • Query.testOptionRestrictions - Fix error parsing database response
3/16/2026

Patch Changes

  • Fix issue where filledOut might be cleared on a sample value if the sample's productId/locationId/productionVolume is changed
3/6/2026

Patch Changes

  • Resolver.updateSample - Fix an issue where sample values being saved before the sample could result in acceptability being calculated with out of date sample data
2/27/2026

Minor Changes

  • PA-756 - Add Mutation.uploadDashboardReportBackground to support uploading files for dashboard report backgrounds
  • Requires DB version 707
  • PA-756 - Add support for saving new dashboard report and chart background style fields

Patch Changes

  • Disable logging of queries in production
2/26/2026

Patch Changes

  • PA-916 - Move the calculation of sample value acceptability from the API to the database. This brings behavior in line with the other Presage data entry applications and should result in more reliable acceptability calculation
2/17/2026

Minor Changes

  • Implement required backend changes to support markdown charts
  • Requires DB Version 706

Patch Changes

  • Fix bug causing file uploads to error with a foreign key constraint error
2/5/2026

Minor Changes

  • Added the ability to filter productBatches by all of the date-time (start, end) and date (expiration) fields. The user can specify start/end as a range or a specific date
  • Query.investigations - productId and locationId filters will now include child products/locations of the specified product/location
  • Add Mutation.createInvestigations to create investigations
  • Add Query.investigationRootCauses which returns a list of all unique root causes across all investigations
  • Updated to newest version of Apollo and GraphQL
  • PA-880 implement SampleSearchStateInput.productId, allowing you to save searches by product ID, instead of just by product name
  • Add retestSamples field to Investigation entity, which includes all samples created in response to the investigation
  • Add Mutation.updateInvestigations` to update investigations

Patch Changes

  • PA-877 - Fix issue where some mutations would throw an error when releasing or rolling back a MySQL savepoint
  • Fixed some misspellings in API field descriptions
1/9/2026

Patch Changes

  • Remove invalid field from Investigation that was added in 7.7.0 and never released
1/8/2026

Minor Changes

  • Create Query.investigations for querying investigations
  • Add AutomaticWorkOrder.nextOccurrence to replace nextOccurance, which is now deprecated
  • Query.analysisCategories is now alphabetized
  • Add PlantUsageCount.analysisCount to replace analyseCount, which is now deprecated
  • Query.allInvestigationTypes is now alphabetized
  • Improved MySQL v8 support (native SSL and authentication support)

Patch Changes

  • Fix various issues with the Investigation entity, including field types and errors fetching relations
  • Ensure that dashboard chart queries are run in the plant's timezone while being tested, just like when they are run on the dashboard screen
  • Note that all currently deprecated fields will be removed in version 8 of Presage API
  • Undo breaking change of renaming AutomaticWorkOrder.nextOccurance to nextOccurrence
  • Fixed a potential deadlock when selecting plant information
  • Undo breaking change of renaming PlantUsageCount.analyseCount to analyzeCount
  • Ensure default sample value calculations are run in the timezone of the sample's plant, rather than in UTC
12/9/2025

Minor Changes

  • Added support for a setting to disable SSL connectivity for servers where it is not possible
  • Added support for SSL connectivity to the database, which will be on by default
Newer Older