Adjust State#
This task is used to change the state of an entity in the MES System. The entity must have a state model associated to it.
Details#
| Fields | Details |
|---|---|
| Scope | Connect IoT Data Platform Enterprise Integration Factory Automation |
| Workflow | Data flow Control flow |
IsProtocol flag |
Inputs#
| Name | Data Type | Description |
|---|---|---|
| entity | EntityType | Entity whose state you wish to change |
| toState | String | State name to which you want to change |
| Activate | any | Activate the adjust state |
Outputs#
| Name | Data Type | Description |
|---|---|---|
| Success | Boolean | If there was no problem emits a true |
| Error | Error | Error that occurred during the processing of this task |
Settings#
On the General Tab, there are the following settings:
| Name | Data Type | Default | Description |
|---|---|---|---|
| Entity | Resource | Resource | Entity type that is going to change state (only the entities defined to be usable by Connect IoT will appear) |
| Instance | EntityInstance | Instance that is going to change state | |
| State model State | String | Default state to which it will change when activated. Default states are dependent upon MES modelling |
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 if the connection or execution fails. |
| Sleep Time between retries (ms) | integer | 1000 | Number of milliseconds to wait between retries. It only applies when the previous call fails |
| 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#
When the task is activated, it will load the received input MES EntityInstance by id or name and change the state name to the given input state name or to the given default name, changing the state of the MES Resource.