Skip to content

19 April 2021 Release Notes

Version 1.1.212

Feature Highlights

Ingredients for Creating Kitchens Can Be Mandatory

With this release, users may set ingredients used in the create kitchen process as mandatory. This means that a recipe variation declared as an ingredient and added to the wizard with the "required": true setting is pre-selected in the Create Kitchen wizard and cannot be skipped.

Additionally, the platform considers any rollback ingredient associated with a mandatory create-kitchen ingredient as mandatory during the delete kitchen process.

See the following topics for more information. [DEV-7321]

Other Fixes & Enhancements

Encoding Errors Fixed: Several users reported database encoding errors that prevented their order runs from executing following the last release. This problem occurred as a result of code changes that altered serializer logic for storing decimal values. This issue was fixed immediately in production. [DEV-8133]

Kitchen Merge Deletes Deleted Recipes: A user found that in some scenarios, the Kitchen Merge feature did not delete recipes in a target kitchen when those recipes had been deleted in the source kitchen. This problem stemmed from empty JSON files that were not recognized by the platform and, therefore, never deleted. This issue has been resolved, and the merge process applies deletes to source kitchens as expected. [DEV-8034]

Memory Issues Resolved with ADLS2 Data Sinks: The platform's Azure Data Lake Storage Gen2 connector was reading whole files into memory to calculate file size, rather than using available file information. This process caused "memory exceeded" errors in variations where large files were moved to ADSL2 sinks. This issue has been resolved, and ADLS2 connectors no longer consume excessive RAM to calculate file size. [DEV-8085]

Jinja Format Correctly Parsed: A user reported that the platform was generating errors when the percent sign and dash combination (%-) appeared in a Jinja directive within curly braces. This issue has been resolved, and the platform parses the Jinja properly. [DEV-6300]

Kitchen Backup Feature Deprecated: The feature designed to back up a kitchen's order runs to an Amazon S3 resource has been deprecated due to low usage. DataKitchen currently maintains order and order run data for three months, or until a kitchen is deleted without promoting its order runs to a parent kitchen. Customers who maintain their own order run databases should consider backing them up regularly. [DEV-5839, DEV-5840]