mirror of
https://github.com/jokob-sk/NetAlertX.git
synced 2025-12-07 09:36:05 -08:00
wf docs
This commit is contained in:
@@ -105,7 +105,7 @@ DEV_LOCATION=/path/to/local/source/code
|
||||
To run the container execute: `sudo docker-compose --env-file /path/to/.env up`
|
||||
|
||||
|
||||
## #Example 4: Docker swarm
|
||||
### Example 4: Docker swarm
|
||||
|
||||
Notice how the host network is defined in a swarm setup:
|
||||
|
||||
|
||||
@@ -21,6 +21,8 @@ This trigger will activate when a `Device` object is updated.
|
||||
|
||||
## Conditions
|
||||
|
||||

|
||||
|
||||
Conditions determine whether a workflow should proceed based on certain criteria. These criteria can be set for specific fields, such as whether a device is from a certain vendor, or whether it is new or archived. You can combine conditions using logical operators (`AND`, `OR`).
|
||||
|
||||
> [!TIP]
|
||||
@@ -36,8 +38,12 @@ Conditions determine whether a workflow should proceed based on certain criteria
|
||||
|
||||
## Actions
|
||||
|
||||

|
||||
|
||||
Actions define the tasks that the workflow will perform once the conditions are met. Actions can include updating fields or deleting devices.
|
||||
|
||||
You can include multiple actions that should execute once the conditions are met.
|
||||
|
||||
### Example Action:
|
||||
- **Action Type**: `update_field`
|
||||
- **Field**: `devIsNew`
|
||||
|
||||
BIN
docs/img/WORKFLOWS/actions.jpg
Executable file
BIN
docs/img/WORKFLOWS/actions.jpg
Executable file
Binary file not shown.
|
After Width: | Height: | Size: 17 KiB |
BIN
docs/img/WORKFLOWS/conditions.png
Executable file
BIN
docs/img/WORKFLOWS/conditions.png
Executable file
Binary file not shown.
|
After Width: | Height: | Size: 22 KiB |
Reference in New Issue
Block a user