Skip to content

20 July 2020 Release Notes

Version 1.1.175

Feature Highlights

Create Kitchen Wizard Redesigned

The latest web app update incorporates user feedback into the redesign of the Create Kitchen Wizard! The new process includes the following features.

  • Faster loading of the wizard and its steps
  • Forward and backward navigation among steps
  • A button to skip optional steps to expedite the child kitchen
  • A new Add Alerts step, as kitchen-level alerts are not inherited from the parent
  • All recipes from version control available for search and selection
  • Access to view problems with ingredient setup
  • A button to enter the new kitchen directly when the process is complete

See a preview of the new wizard below, and see Create Kitchens for more information. [DEV-3038]

()

The Create Kitchen wizard now offers a step for alerts setup.

()

The redesigned wizard offers a search field for recipe selection.

()

The Select Ingredients step provides more information on ingredient variations for the creation process.

New Data Source & Sink Supported

The DataKitchen platform has added another new input/output connector that can serve as a data source and data sink. Now, users can configure their recipe nodes to connect to their Azure Data Lake Storage Gen2 XREFHERE (ADLS2) instances. [DEV-6264, DEV-6265]

()

DataKitchen introduces an Azure Data Lake Storage connector.

Connection String Field Change: This field has been renamed with an underscore character for all Azure data sources and sinks.

connection-string

IS NOW

connection_string

Users with existing Azure Blob Storage recipes must update this property.

Other Fixes & Enhancements

Templates Updated for Recipe Files: The legacy description.json and variables.json recipe files contained pre-defined fields for configuring recipe-level order run alerts. With the release and increased use of the kitchen-level alert function, these fields became a liability for users who had to manually remove them to avoid runtime errors. This release introduces the simplified templates for these files. Description.json retains only the system default settings for alerts. [DEV-6411, DEV-6412]

  • See Alerts Configuration XREFHERE for more information on setting kitchen- and recipe-level alerts.
  • See Recipe Structure for more information on how these files are used.

new description.json template

{
    "description": "",
    "recipe-emails": {
        "recipe-over-duration-email-estimated-maximum-time-in-minutes": "240",
        "email-delivery-service": "aws-email"
    }
}
 

new variables.json template

{
    "variable-list": {
        }
    }
}

Variation Edits Do Not Affect Order in Variation File: Users found that when they made changes to a variation using the Edit action in the Variations tab of the Recipes page, the updated variation moved to the bottom of the variation-list field in variations.json. This automatic sorting defect caused problems when users later attempted to resolve kitchen merge conflicts. This issue has been resolved with a patch to prevent any unintentional reordering of the variations.json file. [DEV-6625]

Order Scheduler Supports Literal Strings for Days: When configuring a schedule in the web app using the "On certain days of the week" option with a timezone entry, users found that order runs never execute at the expected times. This issue has been resolved with an update to the scheduler to fully support string literals for days of the week, such as MON,TUE,THU, with or without timezone definitions. See Schedule Syntax XREFHERE for more information. [DEV-6638]

Agents Settings Persist When Reloading Configure Kitchen Page: Users in kitchens that use custom agent groups discovered that their settings on the Configure Kitchen > Agents tab were not displayed in the web app following any refresh of the Configure Kitchen page. The issue was limited to the web app display of agent settings only. The defect occurred on manual browser refreshes, logins following session timeouts, as well as updates made elsewhere on the Configure Kitchen page. This issue has been resolved and the Agents tab only alters settings for user-initiated changes. [DEV-6630]