Skip to content

1 June 2020 Release Notes

Version 1.1.168

Feature Highlights

DataKitchen Implements New Session Timeout Rules

Previously, users who logged in to the DataKitchen platform user interface had a maximum of four hours to work before their user sessions would automatically end. This session timeout occurred regardless of any user activity. As a result, users were in danger of losing the work they were doing in building recipes.

With this release, DataKitchen shortens the UI session length but restarts the session clock with user activity. Users will now be logged out after 2 hours and 10 minutes of inactivity. Work in progress is not saved. See User Sessions for more information. [DEV-4614, DEV-6335]

()

The platform displays a timeout message after a period of no user activity.

Note

User Session Summary:

Session max length: 130 minutes

Session clock: Resets with user activity

Work in progress: Not saved at session timeout

Other Fixes & Enhancements

Default Config Standardized for Container Nodes: When a user added a container node to a graph, the General Purpose Container and other DataKitchen container images supplied an empty config.json file. While this initial state provided flexibility for experienced script-writers, it prevented many users from building recipes quickly. An enhancement in this release sets a standard template for the container config with the following default fields. See config.json in the General Purpose Container topic for more information and field definitions. [DEV-5584]

{
    "apt-dependencies": [ ],
    "dependencies": [ ],
    "keys": {
        "run_script": {
            "script": "",
            "environment": {},
            "parameters": {},
            "export": [ ]
        }
    }
}

Schedule Parses Cron Strings Correctly: Users found that when they scheduled orders using certain cron expressions in variations.json via the File Editor, the variation's Schedule tab in the UI was not showing the proper settings. The tab did not set the schedule as "Advanced" for the cron expression; it left some fields blank; and it indicated that changes still required an update. If users clicked the Update button, the system removed the schedule completely and all future orders would run only once. This issue did not affect any existing schedules.

This issue has been resolved in this release by updating the schedule editor to parse the cron expression for the form field entries and detect an advanced schedule setting, as shown in the following image. [DEV-6336]

()

Advanced order schedules use cron expressions.