16 November 2020 Release Notes

Version 1.1.192

Feature Highlights

New Confirmation Warns Users of Unsaved Changes

The platform allows users to run variations or run individual nodes while editing their recipes. It is a good practice to perform test runs at all stages of recipe building to ensure that workflows accomplish the desired results. If, however, users run a variation or node without first clicking Update to save their changes, the order submitted will disregard those changes when it runs.

With this release, users who have made changes to a variation then click the Run Variation button on the Variation page or click the Run Node button in the Node Editor, will see the Unsaved Changes dialog. This safety feature warns users of changes and gives them the options to ignore or save those changes. [DEV-7126]

Warnings appearing on the Variations page and in the Node Editor.

Other Fixes & Enhancements

Editing Simplified for Kitchen-Settings File: The kitchen-settings.json file is used to customize the Create Kitchen wizard with, for example, ingredients. This file was coded in a manner that sometimes forced users to edit it outside the platform. This issue has been resolved with a reformat of the file to make it human-readable, so it may now be edited using the Automation command line. See Kitchen Settings for more information. [DEV-7073]

Database Bulk-Insert Error Clarified: When a data sink in a DataMapper node attempted to add more columns than existed in a target database, the system generated a generic "error inserting data" exception. Users could not locate the problem based on the logged information. This issue has been resolved with a new error message for this scenario: "Number of columns on insert statement does not match the column count of the input data (column count)." This message appears in the logs when any insert statement has more, fewer, or different columns than the target data table. [DEV-6433]

Persistent Table Connections Prevented with Database Connectors: An incident occurred where a platform connection locked a database table, and future orders could not access it. With this release, the Automation supported database connectors, except for MS SQL which will be addressed separately, have been updated to guarantee the proper release of database connections. [DEV-6939]

Platform Parses Escape Characters Consistently: Some users received errors when their order runs attempted to insert CSV data into certain database sinks. Faulty parsing of escape characters used with sql-specific keywords caused this problem. This issue has been resolved with an updated CSV parser. [DEV-7274]