Create Notification#
:iot-notification-lg:{style="font-size:100px"}
This task creates a notification in the MES system and optionally assigns it to users, roles, or everyone. The notification can include severity, detailed content, clearance rules, and optional email delivery to the assigned parties.
Details#
| Fields | Details |
|---|---|
| Scope | Connect IoT Data Platform Enterprise Integration Factory Automation |
| Workflow | Data flow Control flow |
IsProtocol flag |
Inputs#
All input values are static and defined at design time.
| Name | Data Type | Description |
|---|---|---|
| notificationTitle | String | Title of the notification to be created |
| notificationDetails | String | Detailed description or message body of the notification |
| notificationSeverity | String | Severity level of the notification |
| notification | Entity | Notification entity reference |
| activate | Boolean | Enables or disables the execution of the task |
Outputs#
| Name | Data Type | Description |
|---|---|---|
| Success | Boolean | Emitted when the notification is successfully created |
| Error | Error | Error that occurred during the processing of this task |
Settings#
On the General Tab, the following configuration groups are available.
General for the task#
| Name | Data Type | Description |
|---|---|---|
| Name | String | Internal name of the notification |
| Description | String | Optional description for identification purposes |
| Type | Lookup | Notification type |
| Title | String | Notification title |
| Details | HTML | Notification content, supports rich text |
| Severity | Lookup | Notification severity |
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.
Assignment#
| Name | Data Type | Description |
|---|---|---|
| Assignment | Enum | Defines who receives the notification: Everyone, User, or Role |
| User | Entity | Target user when Assignment is set to User |
| Role | Entity | Target role when Assignment is set to Role |
Email Notification#
| Name | Data Type | Description |
|---|---|---|
| Send email to Assigned Party | Boolean | Enables email delivery to the assigned user or role |
| Distribution List | String | Optional email list (semicolon-separated) for additional recipients |
Clearance#
| Name | Data Type | Description |
|---|---|---|
| Mode | Enum | Clearance strategy: manual (single or multiple users) or automatic |
| Valid To | DateTime | Expiration date for the notification clearance, depending on the mode |
Behavior#
When the task is activated, it creates a new notification in the MES system using the configured title, details, type, and severity. The notification is then assigned according to the selected assignment rules (everyone, specific users, or roles).