Skip to main content
Version: 5.4

Transfer State Trigger

The transfer status trigger initiates connections as soon as a record created in the connected database is marked as ready for transfer via a flag. After the transfer is complete, the data set is marked as successful or failed. Failed transfers can optionally be repeated as often as desired via an additional counter.

transfer state trigger

note

The transfer status trigger requires a primary key in the monitored table.

warning

Composite primary keys are not supported.

Tab: General

Column to markSelect the transfer column to be monitored in the table. The transfer status trigger triggers connections only if the value in the transfer column is 0. NULL values are ignored.
Retry failed transfersRetry the execution after an error, please activate this checkbox.
Number of retriesSpecifies the number of retries to start a new transfer attempt in case of failed transfers.
Retry count column

Select a column in the table where the retries can be incremented. Select a column with an integer data type.
Attention: The Transfer Status Trigger triggers the connection only if there is a value < "Number of retries" as well as not NULL in the field of the retry count column.

Retry delayTime period that is waited until a new transfer attempt is started.

Tab: Filter

Filter

Graphically represents filters and filter groups. The SQL statement is constructed from this tree at runtime.
Use the buttons to add single filter criteria ("Filter") and grouped filter criteria ("Filter group"). "Delete" deletes the selected criterion.
Filter types:
EQUAL: Compares whether values are equal.
GREATER: Compares whether the entered value is greater.
GREATER_OR_EQUAL: Compares whether the entered value is greater or equal.
SMALER: Compares whether the entered value is less.
SMALER_OR_EQUAL: Compares whether the entered value is less than or equal to.
NOT_EQUAL: Compares whether the entered value is not equal.
LIKE: Compares strings.
LIKE_WILDCARD: Corresponds to LIKE %VALUE%.
LIKE_WILDCARD_END: Corresponds to LIKE VALUE%.
IN: Compares with multiple values. The values must be passed as an array.
NOT_LIKE: Compares if strings are different.
NOT_LIKE_WILDCARD: Equivalent to LIKE_WILDCARD but negated.
NOT_IN: Compares if multiple values are not equal. The values must be passed as an array.

Edit filterThe possible entries change depending on which element is selected under "Filter". Link: Sets the AND and OR operators between the filters/filter groups. Column: Column to be filtered by Comparison operator for the value comparison
PreviewPreview the SQL statement, e.g. WHERE (TIMESTAMP >_ ?) AND (VALUE = ?) . In the example, all records would be selected whose Timestamp field is greater than a timestamp to be set (= newer than date/time) and whose Value field is equal to a value to be set. The values for the filters can be defined dynamically at runtime (e.g. values from OPC items or other tables) or you can define a variable already at design time (which again could be changed at runtime).

Tab: Output columns

Available columnsColumns (data fields) that are displayed as elements (items) of the trigger and are thus available for transfers. This distinction primarily serves the overview in the project planning area - e.g. if only one column of 30 existing ones is required for the connection. Move the columns by double-clicking on the column name or via the "<" and ">" button (after selecting the column). "<<" and ">>" move all columns. Use the "Up" and "Down" buttons to sort the columns used. This also serves the clarity in the display.