QUA-993: Refactor " Flows" userguide.

docs/flows/abort.md

@@ -0,0 +1,17 @@
+# Abort Flow
+
+Users can abort a flow that is currently triggered or running to stop further execution.
+
+**Step 1:** Open the flow execution that is currently in progress and select the **settings** icon.
+
+![chart](.././assets/flows/abort-setting.png)
+
+**Step 2:** Click on the **abort** to stop the execution.
+
+![chart](.././assets/flows/abort.png)
+
+A success message appears confirming the flow is aborted.
+
+Alternatively, you can abort the flow from the Executions tab by clicking the **Abort** icon.
+
+![chart](.././assets/flows/abort-icon.png)

docs/flows/activate-flow.md

@@ -0,0 +1,9 @@
+# Activate Flow
+
+Users can reactivate a flow that was previously deactivated. Once reactivated, the flow’s triggers become active again, allowing it to run automatically based on the defined conditions.
+
+**Step 1**: Click the **vertical ellipsis (⋮)** next to the flow that you want to activate, then click on **Activate** from the dropdown menu.
+
+![activate](.././assets/flows/activate-flow-light.png)
+
+After clicking the **Activate** button, a success notification appears confirming the activation.

docs/flows/add-flow.md

@@ -0,0 +1,44 @@
+# Create a New Flow
+
+Flows allow you to automate actions based on data operations, anomaly detection, or manual execution. When you create a new Flow, Qualytics automatically adds the base nodes you need to begin configuring the automation.
+
+!!! note
+    To create a Flow, you must have **Manager** role. For more details, see the [Team Permissions guide](../settings/security/team-permissions.md){target="_blank"}.
+
+**Step 1**: Click on the **Add Flow** button from the top right corner.
+
+![addflow](.././assets/flows/addflow-light-4.png)
+
+A modal window will appear, allowing you to create a new Flow.  
+Every Flow begins with two default nodes:
+
+- **Flow Node** – Defines the Flow’s name, description, and activation state  
+- **Trigger Node** – Defines when the Flow will start
+
+![flowchart](.././assets/flows/flowchart-light-5.png)
+
+## What You Configure Next
+
+A Flow consists of three main node types. After creating a new Flow, you will configure each one:
+
+### **1. Flow Entry**
+
+Defines the Flow’s general information such as its name and description.
+
+!!! info
+    If you want to learn more about flow entry, check out the [Flow Entry](../flows/flow-entry.md) guide.
+
+### **2. Trigger Node**
+
+Controls *when* the Flow starts (operation completes, anomaly detected, manual, etc.).  
+
+!!! info
+    For more detailed steps, you can review the [Trigger Node Documentation](../flows/trigger-node.md).
+
+### **3. Actions Node**
+
+Defines *what happens* after the Flow is triggered (operations, notifications, HTTP calls, etc.).  
+
+!!! info
+    To explore this in more depth, take a look at the [Actions Node Documentation](../flows/overview-action.md).
+

docs/flows/clone-a-flow.md

@@ -0,0 +1,20 @@
+# Clone a Flow
+
+Users can duplicate existing flows to simplify the reuse and modification of flow configurations for similar scenarios.
+
+**Step 1**: Click on the existing flow you want to clone.
+
+![panel](.././assets/flows/existing-doc-light.png)
+
+**Step 2**: A new window will open displaying the flow's detailed configuration. Click the settings icon and select **Clone**.
+
+![panel](.././assets/flows/clone-light.png)
+
+**Step 3:** After selecting the clone button, click the **Publish** button to publish it.
+
+![panel](.././assets/flows/publish-light-82.png)
+
+!!! important
+    Users with the **Manager Role** can create, edit, clone, or publish Flows. For details, see the [Team Permission ](../settings/security/team-permissions.md){target="_blank"}.
+
+After clicking the **Publish** button, a success notification appears confirming that the flow has been successfully added.

docs/flows/clone-an-action.md

@@ -0,0 +1,14 @@
+# Clone an Action
+
+Users can duplicate an existing action in just a few clicks. Cloning an action allows you to quickly replicate its configuration without manually setting it up again.
+
+**Step 1:** Click the vertical ellipsis (**⋮**) on the action you want to clone, then select the **Clone** option from the menu.
+
+!!! info
+    You can add a maximum of **10 Operation** Actions (such as Catalog, Profile, or Scan) in a single flow.
+
+![vertical](.././assets/flows/vertical-light.png)
+
+**Step 2:** After clicking the Clone option, a cloned action will be created.
+
+![clone](.././assets/flows/clones-light.png)

docs/flows/deactivate-flow.md

@@ -0,0 +1,25 @@
+# Deactivate Flow
+
+Users can deactivate a flow to pause its triggers by disabling it. This prevents the flow from being executed until it is reactivated.
+
+!!! info
+    To deactivate a Flow, you must have **Manager** role. Only users with this role can perform the deactivation action.  
+    For more details about permissions, refer to the [permissions documentation](../settings/security/team-permissions.md){target="_blank"}.
+
+**Step 1**: Click the **vertical ellipsis (⋮)** next to the flow that you want to deactivate, then click on **Deactivate** from the dropdown menu.
+
+![deactivate](.././assets/flows/deactivate-light-95.png)
+
+!!! note
+    If you accidentally deactivate a flow, you can easily reactivate it by following the steps in the [Activate Flow guide](../flows/activate-flow.md){target="_blank"}.
+
+After clicking the **Deactivate** button, a success notification appears confirming the deactivation.
+
+!!! warning
+    Deactivating a flow only pauses its triggers — not deletes it. You can reactivate it anytime, or see the [Delete Flow](../flows/delete-flow.md){target="_blank"} guide to remove it permanently.
+
+## FAQ
+
+**1>.** What happens if I deactivate a Flow?
+
+Once deactivated, the Flow’s triggers stop executing until you reactivate it. Existing executions will not be affected.

docs/flows/delete-flow.md

@@ -0,0 +1,25 @@
+# Delete Flow
+
+**Delete Flow** feature allows you to permanently remove unwanted or outdated flows from the system. This helps in maintaining a clean and organized list of active flows.
+
+!!! info
+    To delete a Flow, you must have **Manager** role. Only users with this role can perform the deletion action.  
+    For more details about permissions, refer to the [permissions documentation](../settings/security/team-permissions.md){target="_blank"}.
+
+
+**Step 1**: Click the **vertical ellipsis (⋮)** next to the flow that you want to delete, then click on **Delete** from the dropdown menu.
+
+![delete](.././assets/flows/delete-light-91.png)
+
+After clicking the delete button, a confirmation modal window **Delete Flow** will appear.
+
+![delete](.././assets/flows/delete-light-92.png)
+
+**Step 2**: Click on the **Delete** button to delete the flow.
+
+![delete](.././assets/flows/delete-light-93.png)
+
+After clicking the **Delete** button, a success notification appears confirming the deletion.
+
+!!! warning
+    This action cannot be undone. If you only want to pause the flow instead of deleting it, see the [Deactivate Flow guide](../flows/deactivate-flow.md){target="_blank"}.

docs/flows/edit-flow.md

@@ -0,0 +1,31 @@
+# Edit Flow
+
+**Edit Flow** feature lets users update existing flows by modifying configurations or adding actions.
+
+!!! info
+    To edit a Flow, you must have **Manager** role. Only users with this role can perform the edit action.  
+    For more details about permissions, refer to the [permissions documentation](../settings/security/team-permissions.md){target="_blank"}.
+
+**Step 1:** Click the flow you want to edit.
+
+![panel](.././assets/flows/panel-light-87.png)
+
+**Step 2:** After clicking the flow, a new window will open displaying the flow's detailed configuration. Click on the boxes you want to edit.
+
+For demonstration purposes we have selected the Flow node.
+
+![result](.././assets/flows/result-light-88.png)
+
+!!! tip
+    If you make changes that you don’t want to keep, you can undo them by discarding the unsaved configuration or refreshing the page before publishing.
+
+**Step 3:** Click the **`Save`** button to apply the updates.
+
+![save](.././assets/flows/save-light-89.png)
+
+**Step 4:** After clicking the **`Save`** button, click the **`Publish`** button located in the top right corner to finalize and publish the changes.
+
+!!! warning
+    If the flow is not published, the setup will not be saved. Always publish the flow after editing to ensure your changes are retained.
+
+![publish](.././assets/flows/publish-light-82.png)

docs/flows/execute-manual-flows.md

@@ -0,0 +1,29 @@
+# Execute Manual Flows
+
+Manual execution gives you complete control over when a Flow should run. You can start a manual Flow directly from the Flows list or from inside the Flow editor.
+
+## Method 1: Execute From the Flows List
+
+**Step 1:** Locate the manual flow in your list of flows.
+
+![manual-flow](.././assets/flows/manual-flow-light.png)
+
+**Step 2:** Click the **vertical ellipsis (⋮)** next to the manual flow you wish to execute, then select **"Execute"** from the dropdown menu to trigger the flow.
+
+![manual-flow](.././assets/flows/verticall-light.png)
+
+After clicking the **Execute** button, a success notification appears confirming that the flow has been successfully executed.
+
+## Method 2: Execute From Inside the Flow Editor
+
+You can also run a manual Flow directly from its editor page.
+
+**Step 1:** Click on the manual flow in your list to open it.
+
+![manual-flow](.././assets/flows/manual-list.png)
+
+**Step 2:** You will be navigated to the Flow editor page; click the **Execute** button.
+
+![manual-flow](.././assets/flows/execute-manual.png)
+
+After clicking the **Execute** button, a success notification appears confirming that the flow has been successfully executed.

docs/flows/flow-entry.md

@@ -0,0 +1,34 @@
+# Flow Entry
+
+The **Flow Entry** is the starting point of every Flow in Qualytics. Think of it as the “root” of your automation — it defines the Flow’s name, purpose, and whether it is active. Once this node is set, you can continue building the rest of the Flow (Triggers, Actions, etc.).
+
+## Trigger Types
+
+A Flow begins when one of its Triggers activates. Here are the four available trigger types:
+
+| Trigger Type | Description |
+|--------------|-------------|
+| [**Operation Completes**](../flows/trigger-node.md#operation-completes){target="_blank"} | Starts the Flow when a catalog, scan, or profile operation finishes. |
+| [**Anomalous Table & File Detected**](../flows/trigger-node.md#anomalous-table-and-file-detected){target="_blank"} | Starts the Flow when anomalies are detected in a table or file. |
+| [**Anomaly Detected**](../flows/trigger-node.md#anomaly-detected){target="_blank"} | Starts the Flow when a single anomaly event occurs. |
+| [**Manual**](../flows/trigger-node.md#manual){target="_blank"} | Starts the Flow only when the user manually executes it. |
+
+## Configure the Flow Node
+
+**Step 1:** Click on the **Flow** node.  
+
+![flow](.././assets/flows/flow-light-6.png)
+
+A panel will appear on the right-hand side, allowing you to:
+
+| No. |             Field Name |                         Description |
+| :---- | :---- | :---- |
+| 1. |              **Name** | Enter the name for the flow. |
+| 2. |            **Description** | Provide a brief description of the flow (optional) to clarify its purpose or functionality. |
+| 3. |            **Deactivated** | Check the box to deactivate the flow. If selected, the flow won't start even if the trigger conditions are met. |
+
+![flow](.././assets/flows/flowsetting-light-7.png)
+
+**Step 2:** Once the details are filled in, click the **Save** button to save the flow settings.  
+
+![save](.././assets/flows/save-light-8.png)