Zum Hauptinhalt springen
Echtzeit-Radar & Feeds
Alle RSS Feeds ➔
👥 Community & Social
Windows Tipps & SecurityGrafikkarte vor Überhitzung schützen: So geht’s(25.09.2026 um 08:00 Uhr)
••••••••••
Windows Tipps & SecurityGrafikkarte vor Überhitzung schützen: So geht’s(25.09.2026 um 08:00 Uhr)
••••••••••
Intelligence View
⚡ tsecurity.de Intelligence

[Tutorial] Chapter 7: Workflow

Originally published at https://www.nocobase.com/en/tutorials/task-tutorial-workflow. Congratulations on reaching the final chapter! Here, we’ll introduce and briefly explore the powerful workflow features in NocoBase. This feature lets y…

0
↗ Quelle (dev.to)
Reagiere als Erste:r — dein Feedback zählt!

Originally published at https://www.nocobase.com/en/tutorials/task-tutorial-workflow.



Congratulations on reaching the final chapter! Here, we’ll introduce and briefly explore the powerful workflow features in NocoBase. This feature lets you automate tasks within the system, saving time and enhancing efficiency.






Challenge Solution from the Previous Chapter



Before diving in, let’s quickly recap the solution to the last challenge. We successfully set up comment permissions for the "Partner" role as follows:





  1. Add Permission : Allows users to post comments.


  2. View Permission : Allows users to view all comments.


  3. Edit Permission : Users can edit only their own comments.


  4. Delete Permission : Users can delete only their own comments.



Image description



With these permissions, Tom can freely post comments, view others’ comments, and ensure that only he can edit or delete his own posts.



Image description






Now, let’s implement an automation: whenever a task assignee is changed, the system will automatically send a notification to the new assignee, informing them of the task transfer.




Workflow: The Workflow Plugin is a powerful automation tool commonly used in Business Process Management (BPM) to design and configure business processes based on data models.



By defining triggers and configuring process nodes, this plugin automates the flow of business processes, enabling efficient task management and data-driven operations.







7.1 Creating a Workflow






7.1.1 Setting Up a Workflow in the Admin Page



First, switch to the Root Role – the system administrator role with all permissions. Then, navigate to the Workflow Module.



Image description



Click the “Add” button in the top right corner to create a new workflow, and fill in the basic information:





  • Name: Send a system notification when the assignee is changed.


  • Trigger Type: Select "Collection Event."



Image description






7.1.2 Explanation of Trigger Types





  1. Collection Event: Triggers when changes occur within a collection (add, modify, delete). This is ideal for tracking updates to task fields, such as when the assignee changes.


  2. Scheduled Task: Automatically triggers at specified times, suitable for schedule-based automation.


  3. Post-action Event: Binds to an action button and triggers after a user action, like clicking "save" on a form.



In future cases, you may also find trigger types such as "Pre-action Event," "Custom Action Event," and "Approval," which can be unlocked through additional plugins.



In this scenario, we use the Collection Event to monitor changes to the "Task Assignee" field in the "Task" collection. After submitting the workflow, click Configure to enter the workflow settings page.



Image description









7.2 Configuring Workflow Nodes






7.2.1 Setting Trigger Conditions



Let’s begin building the automated notification process by configuring the first node and setting conditions to automatically activate the workflow under specific circumstances.





  • Collection: Select "Task." (This collection triggers the workflow and pulls relevant data. We want the workflow to activate when the "Task" collection is updated.)


  • Trigger on: Select "After adding or updating data."


  • Trigger Field: Choose "Task Assignee."


  • Only triggers when match conditions: Select "Task Assignee / ID" "exists," ensuring a notification is only sent when a task is assigned.


  • Preload associations: Choose "Task Assignee," enabling its information to be used in the following steps.






Image description






7.2.2 Enabling the "In-app Message" Channel



Next, we’ll create a node to send notifications.



Before proceeding, we need to create an “In-app Message” channel for notifications.




  • Go back to Plugin Management, select "Notification Management," and create a task notification (task_message).

  • After creating the channel, return to the workflow and add a “Notification” node.



Image description





  • Node Configuration:



    • Channel: Select "Task Notification."


    • Receivers: Choose “Trigger Variable / Trigger Data /Task Assignee / ID” to target the new assignee.


    • Message Title: Enter “Assignee Change Reminder.”


    • Message Content: Enter “You have been assigned as the new task assignee.”








Once complete, click the toggle in the upper right to activate this workflow.



Image description



Image description



Image description



Configuration complete!






7.2.3 Testing the Notification



It’s an exciting moment. Go back to the page, edit any task, change the assignee, and click submit. The system has now sent the notification!



Image description



Image description






That’s the basic workflow setup. However, there’s one more improvement to make:



The notification should dynamically insert task information so users know which task was reassigned.






7.3 Refining the Workflow






7.3.1 Version Management



Return to the workflow configuration. You’ll notice the workflow interface is now grayed out and cannot be edited.



No worries. Click the ellipsis in the upper right corner > Duplicate to New Version, and you’ll enter the new version’s configuration page. The previous version is retained, so by clicking the Version button, you can switch back to historical versions (note: executed workflow versions cannot be modified).



Image description






7.3.2 Enhancing Notification Content



Now, let’s personalize the notification by adding details about the task transfer.





  • Edit the Notification Node.



Change the message content to: “Task 《【Task Name】》 has been reassigned to: 【Task Assignee / Nickname】.”




  • Use the variable panel on the right to add the task name and Task Assignee fields.

  • Then, click the toggle in the upper right to activate this version.



Image description



With the updated workflow version activated, you’ll see the task name in the system notification upon the next test.



Image description









Summary



Fantastic! You’ve successfully created an automated workflow that triggers based on changes to task ownership. This feature not only saves time but also enhances team collaboration. At this point, our task management system has gained powerful capabilities.









Conclusion and Next Steps



You’ve now completed a fully functional task management system from scratch – covering task creation, comments, role permissions, workflows, and system notifications.



The flexibility and extensibility of NocoBase open up limitless possibilities for you. In the future, you can explore more plugins, customize features, or create complex business logic. With this knowledge, you’ve mastered the basics and core concepts of NocoBase.



We look forward to seeing your next innovation! For any questions, feel free to consult the NocoBase official documentation or join the NocoBase community for discussions.



Keep exploring and unleash endless potential!

1. Sofort-Triage & Abwehrmaßnahmen

SOC Incident Playbook: Vulnerability Remediation & Verification
Syntax validiert (0 Fehler)
title: Detect Exploitation - [Tutorial] Chapter 7: Workflow
id: 96e3d8f9-c483-4f79-8816-3cf476c67acd
status: experimental
description: Automatisch generierte SIEM-Erkennungsregel basierend auf CTI Intelligence
references:
  - https://tsecurity.de/
author: iShareStuff CTI Automated Detection Engine
date: 2026-09-26
logsource:
  category: network_connection
  product: any
detection:
  selection:
      CommandLine|contains:
        - 'exploit'
  condition: selection
falsepositives:
  - Legitime administrative Zugriffe oder Penetrationstests
level: high
tags:
  - attack.initial_access
Syntax validiert (0 Fehler)
rule CTI_Threat_Indicator {
    meta:
        author = "iShareStuff CTI Automated Detection Engine"
        date = "2026-09-26"
        description = "YARA Signature for "
    strings:
        $str = "[Tutorial] Chapter 7: Workflow" ascii wide
    condition:
        any of them
}
Syntax validiert (0 Fehler)
index=security sourcetype IN ("cisco:asa", "pan:traffic", "zeek_conn", "suricata", "WinEventLog:Security")
("Tutorial Chapter 7 Workflow")
| stats count earliest(_time) as first_seen latest(_time) as last_seen by src_ip, dest_ip, dest_host, signature
| eval first_seen=strftime(first_seen, "%Y-%m-%d %H:%M:%S"), last_seen=strftime(last_seen, "%Y-%m-%d %H:%M:%S")
| sort - count
Syntax validiert (0 Fehler)
message: "*Tutorial Chapter 7 Workflow*"
Syntax validiert (0 Fehler)
CommonSecurityLog
| where Message has "Tutorial Chapter 7 Workflow"
| summarize EventCount = count(), FirstSeen = min(TimeGenerated), LastSeen = max(TimeGenerated) by SourceIP, DestinationIP, DestinationPort, Activity
| extend DetectionRule = "iShareStuff-CTI-Compiled"
| sort by EventCount desc

2. Cyber Threat Intelligence & Forensik

🎯
MITRE ATT&CK Matrix Navigator 14 Taktiken
Reconnaissance
-
Resource Development
-
Initial Access
Execution
Persistence
-
Privilege Escalation
Defense Evasion
Credential Access
-
Discovery
-
Lateral Movement
-
Collection
-
Command and Control
Exfiltration
-
Impact
tsecurity.de Cognitive Threat RAG
Fokus-Vektor:

Kognitive Analyse für identifizierte Bedrohung: Erhöhte Bedrohungslage im Bereich [Tutorial] Chapter 7: Workflow.... Basierend auf 368k Vektor-Korrelationen werden sofortige Isolationsmaßnahmen für betroffene Endpunkte empfohlen.

🛡️ Angriffsfläche & Exposure

Netzwerk/Remote-Zugriff ohne Vorauthentifizierung möglich.

⚡ Empfohlene Sofortmaßnahmen
  • 1. Perimeter-Inspektion: Relevante Portfreigaben und exponierte Endpunkte unverzüglich scannen.
  • 2. Patch-Applikation: Hersteller-Hotfix einspielen oder betroffene Daemons in isolierte DMZ-Segmente überführen.
  • 3. Telemetrie & EDR-Alerts: Prozessaufrufe und Child-Processes auf anomale Shell-Spawns überwachen.
🔗 Semantisch verwandte Zero-Days MariaDB 11.7 VEC
Ähnliche Beiträge
🔍 Verwandte News

Auch interessante Nachrichten [Tutorial] Chapter 7: Workflow

Thematisch verwandte Begriffe: Tutorial, Chapter, Workflow · 6 Treffer

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Zum Aktualisieren ziehen
ZERO-DAY CVE-2026-100620 | Capgo CLI (npm package @capgo/cli) through 7.98.2 is affected by an ove…
Advisory →
tsecurity.de Icon
Offline-Lesen, Eilmeldungen & 0ms Ladezeit

Installiere tsecurity.de direkt auf deinen Home-Bildschirm für das ultimative Vollbild-Magazinerlebnis ohne Browser-Leisten.

Nächster Beitrag