0.4.7
Fixed
- SQL Server (wrong data): in
varchar,charandtextcolumns with a Simplified Chinese (code page 936) or Traditional Chinese (950) collation, some characters were read as other characters without an error. A value picked from a value list could then miss its rows, different values could be grouped as one, and a join could pair the wrong rows. Now runs, Query Drive, data source joins, value lists and samples all read the same characters as SQL Server. Some Traditional Chinese (950) characters are shown as ‘?’, as SQL Server shows them. Results saved before this version can differ from a new run in such values. Runs that read such columns are slower on values that are mostly Latin letters and digits (about twice as slow with 1 million rows × 20 columns). - SQL Server: when a row held a character that the engine's driver cannot read (for example a user-defined character), the runs, value lists and samples that read that row failed. Now the data source is remembered and marked on the data source screen, and from then on such columns are read as SQL Server converts them to Unicode. The first run that meets such a character fails once; run it again and it reads. Schedules do not stop because of that failure. Value lists and samples read again at once.
Improved
- Turbrix Agent: there are three permission modes: ‘Ask’, ‘Plan’ and ‘Auto’. ‘Auto’ goes ahead without asking, and still keeps the deny and ask rules the user made. A setting saved as ‘Bypass permissions’ is read as ‘Auto’; ‘Manual’, ‘Accept edits’ and ‘Allowed only’ are read as ‘Ask’.
- Turbrix Agent: after a plan is shown in Plan mode, the choices are ‘Yes, this time’, ‘Yes, don't ask again’ and ‘No’.
- Turbrix Agent: by default it edits the canvas that is open, and the cards it changes appear on the canvas one by one. While it edits, ‘Turbrix Agent is editing’ is shown at the top of the canvas. It can also build on a new canvas. It makes a saved workflow only when the user asks for one.
- Turbrix Agent: the cards of a workflow it makes are laid out in layers, in the direction the data flows. Links do not cross cards, and cards that are already there stay where they are.
- Turbrix Agent: kinds that are used only as a SubTask, such as Filter, Sort, Pivot, Summary and Calculate, are not made as a Task. The engine's validation refuses them by the same rule.
- Turbrix Agent: when the tables or columns of a data source cannot be listed, the reason is given. The columns of a REST data source are answered from its registered columns, without calling the API.
- Turbrix Agent: problems found by validation are shown as a validation result, not as a failed tool.
- Updates: a new version is checked for 10 seconds after the app starts, then every hour (it was after 1 minute, then every 24 hours).
- Updates: while a new version downloads, the left of the status bar shows a bar that fills as it downloads, ‘Receiving version …’ and the percentage. The update button at the top right of the window appears when the download is complete.
- Updates: when the downloaded file does not pass the checks, only the button ‘Update file check failed’ is shown at the top right of the window. It offers ‘Try again’ and ‘Dismiss warning’. After the warning is dismissed, the failure of that version is not shown again. A failure of a newer version is shown again. The same version is downloaded again by itself once a day.
- Updates: when a version has already been downloaded, its button stays even if the download of a newer version breaks off or fails.
- Tab rows: when the tabs of the run result pages or of the canvases overflow, the scroll bar no longer covers the tabs. The ‹ › buttons at either end move through them, and the ▾ button opens a list of all tabs. The tab in front is always visible.