If you have trouble understanding how the action works, check the description: Scheduled task
Description
A scheduled task that allows you to rewrite data from a datasource to a database. Datasource can be invoked with input parameters specified in Scheduled Task definition. Input parameters can use time and date placeholders (see tag table below).
Requirements
One or more defined data sources that enable the data read operation.
Configuration parameters
| Name of the parameter | Parameter type | Description | Notes and restrictions |
|---|---|---|---|
| Datasource id* | Text | Id of the datasource from which the data will be rewritten. | |
| Database name* | Text | The name of the database where the data will be saved. | |
| Schema name in database* | Text | The schema in the database where the target table exists. | |
| Table name* | Text | Name of the table in which the data will be saved. | |
| Parameters mappings* | Text | Mapping the output parameters from data source to the corresponding column names from the database table. | Parameter mapping formula: <dataSourceParameter>=<TableColumn> Subsequent mappings should be separated by a comma, e.g. <dataSourceParameter1>=<TableColumn1>,<dataSourceParameter2>=<TableColumn2> |
| Synchronization type* | Text | Data synchronization type. | The following types are available:
|
| Keys | Text | The key value of which will be checked with the "upsert" synchronization type. Possibility of specifying multiple comma-delimited keys. | Successive keys should be separated by a comma, e.g. key1,key2,key3 |
| Datasource parameters | Text | Datasource input parameters. Example time and date tag usage: {current_YYYY}-{current_MM}-{current_DD} - will insert current date (format: yyyy-MM-dd). | Input parameters pattern: <datasourceParam>=<value> Each subsequent input parameter should be separated by comma e.g. <datasourceParam1>=<value1>,<datasourceParam2>=<value2> |
| Save data condition | Text | Save data condition written in JavaScript that needs to be met in order to process datasource response. | Example: Let's assume that "statusCode" is one of the datasource's output parameter. We can condition further processing by specifing that it's value should be between 200 and 300: statusCode >= 200 && statusCode <= 300 We can mix and match different datasource parameters and values keeping in mind that the result must be a boolen type. |
Parameter*- required field
Data from the data source will not be successfully written to the database table if the returned values do not match the defined table column types.
Sample configuration
Add Comment