24 October 2021 Release Notes¶
Version 1.1.231
Feature Highlights¶
Run Variation Dialog Redesigned with Expanded UX¶
Many Automation users were not fans of the Run Variation dialog because they had problems managing runtime variable overrides or knowing which variables required user input for a variation to run properly. Additionally, users scheduling runs had no way of knowing if the same or similar scheduled order was already active for a variation.
This release turns the dialog into a four-step wizard, where optional steps provide sufficient detail on variable values and previously scheduled orders to help users make appropriate configurations. [DEV-7808]
See Run an Order and Order-Time Overrides for more information.
Previews of the Updated Dialog¶
The Run Variation dialog shows three or four steps, depending on selections and existing scheduled orders.
The Variables step allows users to view and edit variables to set new runtime values. Modified variables display in bold font.
The optional Orders step lists similar scheduled orders to help users avoid duplication.
The Summary step lists the user's selections and shows the create-order progress.
Other Fixes & Enhancements¶
File Limit Removed from Kitchen Merges: Recently, merge problems required DataKitchen to place a 300-file limit on kitchen merges. One bug caused empty or deleted files to appear in merge previews. This release fixes this bug and a number of underlying issues, and it lifts the max-file restriction. Users may resume large merges. [DEV-8161, DEV-8173, DEV-8287, DEV-8584, DEV-8995]
Note
File Renames: For merges with more than 300 files, the merge preview will treat any renamed file as a pair of changes: the previous filename removed and the new filename added.
Ingredient Variable Records Either Boolean Value: While setting inflowing variables for an ingredient, a user found that a Boolean value set to "true" was registered in the ingredient node's notebook.json file, while the same value set to "false" did not appear in the notebook. Without the proper value in the notebook, any run of the ingredient returned inaccurate results. This issue has been resolved, and the platform codes any Boolean set to "false" properly in the node files. [DEV-9164]
Ingredient Outflow Variable List Revised: When configuring a variation to serve as an ingredient, users found that the autocomplete function for outflow variable fields offered kitchen overrides and variables not in use in the variation, along with available variables. The list also did not include runtime variables. This issue has been resolved, and users can configure the ingredient outflow by selecting from a list containing base recipe variables, variable overrides for the current variation, and runtime variables defined in the current variation. The autocomplete list excludes kitchen overrides and variables not used in the current variation. [DEV-9187]
Node Editor Closes Compile Window Properly: Users reported that after closing a compiled view of a file then navigating away and back to that file, the Node Editor was displaying the original compiled view. This issue has been resolved, and the Node Editor displays the proper code view of a file following user navigations. [DEV-9254]
Container Connection Field Allows Slashes: In a container node's Connections tab, users must designate a Docker image namespace. This Namespace field in the webapp was restricted to alphanumeric characters, hyphens, and underscores. With this release, the field also supports dot (.) and forward slash (/) characters. [DEV-8907]
Wiki Warns about Unsaved Changes: The Wiki tab on the Recipes page was allowing users to navigate away and lose their unsaved edits without any notification. This issue has been resolved, and the Wiki tab displays a warning dialog to users when they risk losing their updates. [DEV-8963]