Skip to content

27 July 2020 Release Notes

Version 1.1.176

Feature Highlights

Web App Refresh Simplifies Ingredient Node Page

The Automation web app updates continue with a new design and simplified functionality on the Ingredient Node page. Ingredient nodes call pre-defined ingredient variations in order to execute a shared function or generate fresh output.

By removing several configuration fields and providing direct access to the underlying ingredient variation, DataKitchen designers and developers have offered an easier path for users to employ ingredients in their recipes.

Summary of Changes

  • Accessing and configuring the ingredient node in the Node Editor is now consistent with the other node types.
  • After selecting the underlying ingredient variation, the user sees a summary and graph of that variation, so it is clear what will be running in the ingredient node.
  • A link in the Node Editor opens the ingredient variation for editing in a new browser tab.
  • The node configuration reduces complexity by excluding some legacy fields:
    • ingredient failure options, as they are already set for the ingredient variation, and the ingredient node will fail on ingredient test failures
    • the agent group setting, as the ingredient will process using the agent defined for the ingredient variation's kitchen by default.
    • the polling intervals, as the node uses standard system polling.

See Call Ingredients from Recipe Nodes for more information. [DEV-4537, DEV-6675]

Page Previews

()

The Ingredient tab summarizes and links to the ingredient variation.

()

The Configuration tab simplifies node setup to timeout and variables settings.

()

The Tests tab mirrors the standard test settings for other node types.

Other Fixes & Enhancements

Full Logs Displayed in Web App: Previously, the web app truncated the display and filtering of order run logs to the first 2000 lines. Users had to export larger logs to view all entries. This issue has been resolved with an enhancement to the Order Run Details page, so it now loads entire logs 200 lines at a time as users scroll down. And, filters apply to all log entries. The enhancement applies to the Order Run Logs dialog as well as the Logs section of the Node Details sidebar. See Logs for more information. [DEV-5420]

Merge Error Resolved for File Conflicts: The system generated errors during the kitchen merge process when child and parent kitchens had conflicts in specific categories of file extensions. Merge conflicts in .json, .txt, .md, and .sql files were not affected; but conflicts in other file types, such as .py, .html, .ipynb, or binary files, caused a merge to fail. This issue has been resolved converting the merged file content to bytes. [DEV-6736]

Data Source Adds to Container Properly: When a user created a container node without selecting a data source during the Add Node process, the platform was generating an error when the user later attempted to add the source in the Connections tab of the Node Editor. This issue has been resolved; container nodes update with the new data sources as expected. [DEV-6689]

Cron Expression Help Published: A new topic has been added to the DataKitchen platform documentation to help clarify the cron syntax supported by the order scheduler. This content includes information on time zone limitations. See Cron Expression Basics. [DEV-6683]