SHARE YOUR IDEAS

Hello,

Currently its possible to create an ETL automation where based on a given schedule the defined 'Extractions' are extracted. This works great but in a global scenario where potentially multiple instances of the same source system are in scope, each with their own ETL windows the current capabilities are insufficient to cover this.

This Idea covers various suggestions to improve the automation capability in such a way that it can support complex global ETL:

• I want to be able to schedule multiple 'automations' potentially using different scheduled (e.g. run 1 every day at 02:30, run 2 every day at 6:30)

• For each automation run i want to be able to

  • Select which Extractions should be included as part of the run

  • Select the 'Connection' per Extraction which should be considered in case multiple instances of the same source system are used globally. At the moment a Connection is directly linked to an 'Extraction' meaning if you have multiple instances of the same source system, multiple Extractions need to be build resulting in multiple source tables.

  • Last read time needs to be considered per extraction run

In addition it should also be possible to schedule 'deletion' runs based on a defined parameter set and schedule