Resolve Table#

The Resolve Table Task retrieves data from a specific Generic/Smart table.

Details#

Fields	Details
Scope	Connect IoT Data Platform Enterprise Integration Factory Automation
Workflow	Data flow Control flow
`IsProtocol` flag

Inputs#

Name	Data Type	IsTrigger	Description
Activate	`any`	Yes	Activates the task

Table: Resolve Table inputs

Outputs#

Name	Data Type	Description
Rows	`any`	Rows retrieved from the table
Success	`Boolean`	Triggered when the task is executed with success
Error	`Error`	Triggered when the task failed for some reason

Table: Resolve Table outputs

Settings#

Name	Data Type	Value	Default	Description
Table Type	`enum`	`GenericTable` `SmartTable`	`SmartTable`	Type of table to use mode
Table	SmartTable or GenericTable			Table to use as a source for the data
Returned Results Mode	`enum`	`OnlyFirstRow` `AllMatches`	`OnlyFirstRow`	How the returned dataset should be generated
Partial Resolve	`Boolean`		`false`	Uses 'partial resolve' for smart table resolution (empty key values resolve to any value)
Reset inputs on activate	`Boolean`		`true`	Resets the inputs after being triggered
Emit on table update	`Boolean`		`false`	Emits the task when the table is updated
Use cache	`Boolean`		`true`	Uses cache to load values
Cache TTL	`Integer`		`0`	Number of seconds until the values stored in cache expire. If equal to 0, the cache is never invalidated

Table: Resolve Table settings

And the following retries settings:

Setting	Data Type	Default	Description
Number of Retries	`integer`	30	The maximum number of attempts the IoT process (client) makes to call the MES backend. Only the transient failures listed in Retry Mechanism are retried; any other failure is reported without a further attempt.
Sleep Time between retries (ms)	`integer`	1000	Number of milliseconds to wait after each attempt that ends in a transient failure, including the last attempt, before the task reports the error.
Number of System Retries	`integer`	10	The maximum number of attempts the MES backend makes to call the target service if the execution fails.

Multiplicative Retry Effect

Retry limits are cumulative. In the event of a persistent target service failure, the total number of requests generated will be the product of the Client Retries (N) and the Backend Retries (M). For example, if both are set to 10, a single IoT request could result in up to 100 total attempts (N x M), which may lead to system congestion or high latency.

Behavior#

In the settings, define the type and name of the table to retrieve data. The input values should be, in case of smart tables, the keys to resolve. In the case of generic tables, the column values to use as filters.

Each output added for a column emits the value of that column when one row is found, a list with the value of each row when several rows are found, and an empty list when no row is found.