Creating Tasks

This page describes how to create and configure Tasks in SIWENOID v2. Tasks are automated actions that SIWENOID v2 executes automatically when a defined event occurs in the system. They allow the system to respond to security events without requiring manual operator intervention.

A task consists of three components:

• A trigger — the event or condition that causes the task to execute (for example: a specific datapoint entering alarm state, a pre-alarm condition, a fault signal, or a status change on any datapoint in a defined category).
• An action — the operation that SIWENOID v2 performs when the trigger fires (for example: send an SMS message, send an email, activate an output, execute a script, or display a notification).
• User assignment — the user account or accounts that the task is associated with, which may affect delivery targets (for example, which phone number receives an SMS).

Tasks are evaluated in real time by the SIWENOID v2 server. When an incoming event matches the trigger conditions of a configured task, the server executes the associated action immediately. Tasks are entirely server-side — they function even if no client is connected.

Prev ← SIWENOID v2 Map Next → Creating Forced Actions

To access the Tasks configuration, open the main menu and navigate to File → Options → Tasks.

The Tasks screen lists all currently configured tasks. Each task is shown with its name, enabled/disabled status, and the action type it performs. From this screen, tasks can be created, edited, enabled, disabled, and deleted.

To create a new task, click the Add button (plus icon) in the toolbar.

The task editor opens. Fill in the following fields:

Enable / Disable toggle Use this checkbox or toggle to activate or deactivate the task. A disabled task remains saved in the configuration but will not execute when its trigger fires. This is useful for temporarily suspending a task without deleting it — for example, during maintenance periods.

Name Enter a descriptive name for the task. The name should clearly identify what the task does and when it fires, so that other engineers can understand the configuration at a glance. Example: “Alarm SMS to security officer” or “Fire alarm email notification”.

Executable task (Action type) Select the type of action this task will perform from the dropdown list. The available action types depend on the modules configured in SIWENOID v2. Common action types include:

• Send SMS — sends a text message to one or more configured phone numbers via a connected SMS gateway or GSM modem module.
• Send email — sends an email notification to configured recipients via a connected email module.
• Activate output — sends a command to a configured output datapoint (for example, triggering a relay to activate a siren, a strobe light, or an access control lock).
• Execute script — runs a custom script defined in the Scripts configuration of SIWENOID v2.
• Display notification — shows a popup notification on connected client workstations.

When an action type is selected, additional fields specific to that action type appear below (for example: phone number for SMS, email address for email, output datapoint for activate output).

Users Select the user account or accounts that this task is associated with. For notification tasks (SMS, email), the user assignment determines which contact details are used for delivery. For other action types, the user assignment may be used for audit logging purposes.

After setting the basic task properties, configure the trigger that will cause the task to fire. The trigger defines which event or condition activates the task.

Set the following trigger parameters:

Event type Select the event type that will trigger the task. This maps to the event categories and treatment types defined in the system configuration. Examples: Alarm, Pre-alarm, Fault, Excluded, Normal (return to normal). The task fires each time an incoming event of this type is received by the server.

Datapoint or module scope Specify whether the trigger applies to a specific datapoint, a specific container or logical group, or all datapoints system-wide. Scoping the trigger precisely prevents unintended task executions — for example, a task that should only fire for fire alarm events should be scoped to the fire alarm subsystem, not all datapoints.

Module Select the module that will execute the action. Modules are the driver components that provide specific capabilities to SIWENOID v2 (for example: the SMS module, the email module, the script engine). The module must be configured and active before it can be used in a task. See the Creating Module page for module configuration instructions.

The following example demonstrates how to configure a task that sends an SMS message when an alarm event is received.

1. Click the Add button to create a new task.
2. Enable the task using the enable toggle.
3. Enter a name, for example: “Alarm SMS notification”.
4. Select Send SMS as the executable action type.
5. Set the trigger event to Alarm.
6. Select the SMS module from the module dropdown. The SMS module must already be configured with a connected GSM modem or SMS gateway — see the Creating Module page.
7. Enter the recipient's phone number in the phone number field. The number must be in international format (for example: +36201234567).
8. Assign the relevant user account.
9. Click Save to save the task.

From this point, every time the SIWENOID v2 server receives an alarm event matching the trigger scope, an SMS message will be sent automatically to the configured phone number.

• Tasks are executed by the SIWENOID v2 server process, not by individual client sessions. A task will fire even if all client applications are disconnected, as long as the server is running.
• All task executions are recorded in the event log, including the task name, the triggering event, the execution time, and whether the action was successful or failed.
• If a task's action module is unavailable (for example, the SMS modem is offline), the task execution will fail and a fault entry will be recorded in the event log. The trigger event itself is still logged normally.
• Tasks that are too broadly scoped (triggering on all events system-wide) can generate very high volumes of actions during major incidents. Scope triggers as precisely as possible to avoid notification floods.

—

Prev ← SIWENOID v2 Map Next → Creating Forced Actions