29 June 2020 Release Notes

Version 1.1.172

Feature Highlights

Stay tuned for new DataKitchen features in coming releases!

Other Fixes & Enhancements

New Kitchens Do Not Inherit Alerts: When users created child kitchens, the kitchen-level alerts set in the parent kitchens were copied. This behavior often resulted in alerts being sent to an unintended recipient list. This issue has been resolved by removing the inheritance of kitchen alerts. New child kitchens get created with an empty kitchen alert recipient list. See Configure Kitchen Alerts for more information. [DEV-6483]

Scheduler Handles Sunday Cron Option: Because Sunday can be expressed as a 0 (zero) or a 7 in a cron statement, the order scheduler was misinterpreting cron entries for some orders running on Sundays. This issue has been resolved with a code update to handle 0s and 7s in the same manner. For example, 0 20 * * 7 and 0 20 * * 0 both mean "at 20:00 on Sunday." See Schedules for more information. [DEV-6547]

Node Connections Allow At Signs: Users found that they could not enter the required username to connect to a Microsoft SQL Server, as the syntax @servername was not allowed by platform field validation. This issue has been resolved by adding the at sign (@) to the allowed characters in the username field for most database connections (DB2, MS SQL, MySQL, Oracle, Vertica, and PostgreSQL). [DEV-6248]

File Editor Saves Duplicate Keys: While building recipes using the File Editor, users can input invalid JSON, then view other files in the File Editor with or without saving the working file, and return to see all changes retained so they can continue building. This same scenario was not allowed if users copied keys within recipe files. Those keys were automatically removed when users viewed other files then returned. This issue has been resolved by updating the system to store duplicate keys while users view other files while remaining in the File Editor. The system, however, still prevents users from saving any file with duplicate keys. [DEV-6310]

Platform Warns Users of Invalid Changes: When users try to navigate away from a page with valid, unsaved edits, a warning dialog appears with cancel, discard, and save options. The platform did not provide a similar warning when users navigated away from a page with invalid changes. This issue has been resolved with a new warning dialog, offering cancel and discard options. The dialog appears on the Configure Kitchen, Variation, Node Editor, and File Editor pages. Additionally, the Update button now displays a tooltip on hover to explain why the button is not available. [DEV-5988]