Skip to content

26 September 2021 Release Notes

Version 1.1.229

Feature Highlights

New Node Status Shows Where Order Run Stopped

When an order run stopped because it exceeded set time limits or was stopped manually by a user, the graph on the Order Run Details page continued to display a Running status for the node that was executing at the time. This release introduces the Stopped node status to prevent confusion and give users a clear indication of how far their order runs progressed when they were stopped. Differentiated from "stopped," nodes that have not yet been executed will continue to show the Not Run status. See Graph Processing for more information. [DEV-8853, DEV-8882]

()

A node displays a "Stopped" icon if it had been running when the order run stopped.

Other Fixes & Enhancements

Date Values Handled Properly without Server Errors: The system generated an error when a user attempted to access the Order Run Details page. The cause of the problem was the platform's mishandling of script-output variable values using a date format. This issue has been resolved; the platform now handles date and datetime values in a JSON-compatible manner, and the navigation to order run information is no longer blocked by data type conflicts. [DEV-8737]

Known Limitation: The platform currently does not support the successful export of a date or datetime variable value from a script run within a container node. These data types must be converted to string format prior to export.

Log Level Added to Order Run Logs: In order to be consistent with the Python-based logging generated from any analytic container, the Automation platform now employs the critical log level. Users had requested some clarity in log entry severity because containers reported critical items that the general platform logs treated as errors.  With this release, both container and platform support the following log levels. Platform logging continues to use the trace log level as well. [DEV-8392, DEV-8937]

  • debug
  • info
  • warning
  • error
  • critical

Create Kitchen Ingredients Honor User Inputs: When a user selected more than one ingredient to run in the Create Kitchen wizard and provided new values for the ingredient variables, the system was overwriting user inputs from the first ingredient with entries for subsequent ingredients and defaulting back to parent kitchen values. The results were abnormal kitchen configurations or failures. This issue has been resolved, and the system applies user-specified values properly to each ingredient while creating child kitchens. [DEV-8918]

MySQL Connector Updated: Users building MySQL data sources and data sinks into their recipes reported some issues with the Automation MySQL connector. Specifically, users received "commands out of sync" errors when they did not select a query result type or when they employed multiple statements (for example, an insert and a select statement, in their stored procedure steps. These issues have been resolved, and the connector accounts for incorrect result types and supports multiple statements in a single step. [DEV-9131, DEV-9144]