Release Notes: Runner Version 3.5.0¶
Note: Runner release 3.5.0 is an Zuar-internal release that was not deployed to customer instances. Features in 3.5.0 will be delivered to customers in the upcoming 3.6.0 release.
Breaking Changes¶
None
Issues Resolved in this Release¶
Epic¶
Issue |
Summary |
Description |
---|---|---|
File Manager UX improvements |
Various improvements to the Runner File Manager UI to deliver a more intuitive user experience, effective presentation of Search results, and better performance. |
New Feature¶
Improvement¶
Issue |
Summary |
Description |
---|---|---|
Modify webapp startup to ignore possible absence of $MITTO_DATA/tmp |
Change made as described, which only affects development workflows; this does not affect customer instances. |
|
XSV jobs w/ Regex: add support for relative paths |
XSV jobs now support the use of either regex or globbing to specify input from files in nested directories. |
|
File Manager - implement “double click” to open Folder within search results |
In the File Manager interface, the behavior of double-clicking the File object icons within Search Results would not open the file; users needed to right-click the file and select “Open.” This behavior is now consistent between the unfiltered File view, and the view generated as Search Results. |
|
File Manager - column headers don’t “sort” the page display |
In the File Manager UI page, the top headers for the page are now clickable, which will toggle the sorting on the column. |
|
Job Store page: “Remove” button removes the Job, improve the UX |
The button on the Job Store page labeled “Remove” had a non-obvious purpose of removing the Runner Job fully. This is re-named to “Remove Job.” |
|
Add “Remove” button to the Job > Store UI Page |
The User is now able to delete a Job Store directly from the Job Store page in the UI. This assists Users in situations where a Store must be removed and re-populated fully from fresh input data, common in troubleshooting. Prior to this feature, the User would need to use a Command Job to drop the Store. |
|
Make mitto-cli commands available from Host OS |
A convenience feature is added, where the Runner administrator is able to issue |
|
Show database sizes on the Database page |
In previous versions of Runner, the Database storage utilization was only visible on the Settings page of the UI. This location was not as intuitive as desired. The Database storage size information is now added to the Database page of the UI. |
|
Migrate to Python 3.11.1 |
The default system Python version used by Runner is now 3.11.1. |
|
Display store information on jobs page |
Summary information about the Runner job “Store” is visible in the UI. For jobs using a Store, the user now can see the size of the Store on disk, the date when the Store was last modified and the count of records contained in the Store. |
Task¶
Issue |
Summary |
Description |
---|---|---|
Add support for credentials refresh |
Some authentication mechanisms, such as OAuth, will provide a Token that expires after a set time period, requiring Runner to re-authenticate to receive another Token, and this process will potentially repeat frequently. A process has been added to Runner that allows the Tokens to be refreshed transparently to the User. |
Bug¶
Issue |
Summary |
Description |
---|---|---|
Jobs pagination: if total number of jobs is divisible by 50, clicking >> goes to Howdy |
An error in the page navigation would occur whent he page count and the navigation offset were the same value. This is handled correctly now. |
|
Rename of sequence causes 500 internal error |
Runner stores sequences in the internal database only, not in a |
|
TINYINT errors with mysql after merging 3.4.x into 3.5.x |
Identification of values now correctly classified as TINYINT with both MySQL and SQLServer. |
|
Job > Incoming webhook creates broken webhook |
Creation of incoming webhooks no longer result in 403 errors. |
|
Logs not being loaded completely |
Loading of logs into the logging container was not correctly handling the signal indicating that the Job log was loaded completely, resulting in log messages not storing correctly. This is now resolved. |
|
Navigation item > Validation |
In instances of mis-configuration for custom Navigation items (app state being left |
|
Subscriptions job - ‘schema_name’ ignored for ‘subscriptions’ table |
‘schema_name’ value is now respected. |
|
File Manager “Details” and main page summary incrementing Modified/Created times |
In the File Manager UI page, the “created” and “modified” data was being read from |
|
Title tab of migrated Runner instances show previous hostname/IP address |
Runner instances migrated showed the DNS name or IP address of the previous instance; this has been replaced with page titles not specific to any instance. |
|
IO jobs with output schema set to empty string doesn’t render the “Data” navigation button in the Job page banner. |
If an IO Job has a null string listed for the output Schema, the “Data” table navigation link will not display. Since the Runner IO Job will default to using a null output Schema, the result is a large percentage of wizard created Jobs having this button hidden. This has been corrected. |
|
Error in console after browsing to Stage / Swimlanes / Graph pages |
Date range filtering was breaking navigation to certain pages. This is now resolved. |
|
Runner Excel job Tables not populating |
A bug had been introduced in the FlatFile job wizard, where |
|
File Manager - Error after Paste in empty folder |
In the File Manager, when a User “cuts” files and performs a “paste” into another folder, then attempts to “paste” the same files to the original folder, the “Uh Oh” error page is shown. This issue is resolved. |
|
Add retry on supervisor state request fail |
The Mitto Supervisor Service was improved with a more effective handling of delayed responses and retrying that status query. This works to improve stability and UI state during application upgrades. |
|
Data Editor - cannot set Boolean value to “False” |
In previous releases, the table |
|
Mitto 3.3.5 Data Editor existing populated date fields “nulled” when opening Editor modal |
When the Data Editor opened a table for updating, the existing Date fields would be filled with |
|
Mitto 3.3.5 Data Editor bug Uh-Oh screen on record save |
On record saves in the Data Editor, the result was an error page. This is resolved. |
|
Error in console after removing a Job |
When a User deleted a Job, an error was raised because the WebSocket was attempting to update status on the Job after it had already been deleted, and thus failed with error. This is now corrected. |
|
Credentials - renaming existing credential results in empty credential data |
Previously, when the User attempts to rename a Named Credential in the UI, the contents of the credential would be lost. |