Changelog

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

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

Patch Changes

• Remove invalid field from Investigation that was added in 7.7.0 and never released

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

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

Minor Changes

• PA-774 - Support suppliers in calculated defaults
• PA-776 - Add supplierId to TestOptionRestrictionsInput and GetOptionRestrictionInput

Patch Changes

• Fix issue where PresageColumnChart dashboard data source would filter dates in the wrong timezone

Minor Changes

• Dashboard charts now support columns with arbitrary roles

Patch Changes

• Fixed an issue in formatting query strings introduced by a recent update

Patch Changes

• Fix Mutation.createUserAccount and Mutation.updateUserAccount checking for permission to manage API tokens even if you are not including one in the request

Minor Changes

• Implement licensing of a handful of features
• Add Mutation.flushLicenseCache
• Add Query.licenseInfo
• Requires DB version 704

Patch Changes

• The number of connections allocated for data loaders is now increased automatically in order to avoid deadlocks on busy systems
• Mutation.updateWorkOrderType - Support sparse updates. Omitted fields will no longer incorrectly be populated with their default values, so you only have to send the fields you are updating rather than the whole set every time.

Minor Changes

• PA-797 - Implement new permissions for recipe, alert subscription, and report subscription configuration. Requires DB version 703
• Added result and results filter to Query.sampleValues

Patch Changes

• Make DashboardItemLegacy.newConfiguration more resilient to bad data
• Fix Mutation.createSample and Mutation.updateSample checking auth if the analysis did not require it, instead of if it did