Features

In the following all features are listed which are (partly) included in the release. If no other open parts (stories) are left, the feature is finished and otherwise it is clarified as ongoing.

Finished Features


Supporting write of .gz/.zip files 
GoalIt is possible to write CSV files on a mounted file-system from within a OD workflow which are packed inside .zip/.gz.
Finished parts in the releaseFurther UX/UI improvements 

Spacing

  1. Spacing between header “Data Table” and the variable google should be the same as between header “Connection” and “Select Connection” input field.
  2. Please take care that the spacing between the sections is always the same.
  3. Take care that "Info" below "Select Connection" input field is not jumping as soon as a connection is selected.

Packaging Type

  1. In case of Packaging Type ZIP or GZP the section “File name of packaging file” should appear BELOW the section Packaging Type. Reduce font size of section “File name of packaging file” to indicate that this belongs to section “Packaging Type” (<h4>, 12px). Section Packaging Type shall use the full width.

Connection

  1. Restyle entries in "Select Connection" input field.
  2. Add connection type to entries in "Select Connection" input field.

Info texts and info text dialogs

  1. Info texts for “Save Procedure” and "Schema Mismatch Behaviour” are talking about Data Tables. Please rephrase in case "write to external connection" is selected.
  2. Rephrase additional info text for packaging type GZIP to “In case a GZIP with the same name already exists it will be replaced without asking".
  3. Check which configs are mandatory and make all those mandatory and mark them as mandatory (via adding an asterisk to the name).
  4. For ZIP make in the info text for File name clear that the user has to define a path RELATIVE TO THE PACKAGING FILE.
  5. Icons to open the info text dialogs should be beside the headers, not beside the input fields. Exception: info icons for structuring tokens.


Basic SQL editor functionality 
GoalWe know with which technology it might be possible to support an auto-completion for arbitrary PL/SQL queries to oracle databases. 
Finished parts in the releaseSupport excel download of oracle result Enable the excel download of query result for oracle (also containing executed query).


Flexible ETL Load V2 
Goal

Improve the usability by selecting a connection instead of a data table. Furthermore select queries can be written directly without further wrapping ( (query) as foo). 

Finished parts in the release

Creation of Flexible ETL Load V2 Processor 

Improve the usability by selecting a connection instead of a data table. Furthermore select queries can be written directly without further wrapping ( (query) as foo). 


Execute PL/SQL from ONE DATA
Goal
Data Analysts already use PL/SQL scripts on a daily basis for a various number of problems.
Finished parts in the release
Execution of arbitrary statements on Oracle Databases
This will enable the execution of anonymous PL/SQL blocks among other SQL statements such as INSERT, UPDATE, etc.


Ongoing Features


Client support for File System Write inside Data Table Save Processor 
Goal

The DataTable Save Processor UI should natively support the configuration of either a DataTable or a File System Connection. 


Finished parts in the release

Feedback from UX / Guidance for supporting file system write in client 
Added the feedback from our UX/UI experts. 
Client support for File System Write 
  • It is possible to switch inside the UI of the DataTable Save Processor between the following modes
    • saving a DataTable
    • writing to a file system connection
  • There is full UI support for the configuration of the file system connection mode
  • It is still possible to write either to a DataTable or to a file system connection


Finalize UI for Debug-Mode
Goal
Make a better debug experience for users
Finished parts in the release

Replacing icon for errors in job
For jobs, we need to replace the existing "bug" icon (when an execution failed) with an "exclamation mark" icon, because the "bug" icon will only be used for the debug mode. The same icon needs to be replaced for the failed processors.