Integrator

In the new version 2023.3, we started to use the new Snowflake connector. When the current snowflake connector queries all meta data (e.g. table names, column names), the query is over ALL tables and columns in the Siemens Snowflake Account. This ...

Currently the ETL flow graph can get confusing/insane large if there're many steps. We need to find a better way to filter/re org the information/flow.

Add a JDBC based connection for Google BigQuery that uses the GoogleToken mechanism for authorisation

THe new project overview screens in integrator are great, but what would make the finctionality much better is the ability to: Collapse/Expand the groups of components Adding of a search bar at the top for the components.

When you connect to ADL, the data is "schema-less" (ie there are no field names on the file columns.). Data Lake has a way of presenting multiple files (i.e the data files - there could be multiple.., the json file containing the field definitions...

In complex projects, to ensure readability of integrator, component names can get very long. Currently, with long names you need to guess the name and then check the name on the component tree to see if you have selected the right one. The datasou...

The customer would like to use Token-Based Authentication for JDBC connection (NetSuite in this case) in addition to the User name and Password currently supported. As per Knowledge Base article https://knowledgebase.jedox.com/integration/connecti...

As integrator projects became more and more complex, it would be useful to display the creator, modifier, created and modified date and if it is possible last import date (when it was imported into a certain environment) in integrator components. ...

When a function in field transform runs into an error, its now pretty hard to investigate which function resulted in an error. Intsted of this, the error message should tell more about which function has an error, or, in the field transform data p...

In integrator, it would be very useful if we could generate a global field transform (within a project, or within a certain workspace). For example, during data inputs, customer ID should be processed by a groovy, concatenation, or any other field...