Skip to main content

Workflow Designer

The Workflow Designer allows users to create automated business processes by connecting workflow components using a visual drag-and-drop interface.


Workflow Overview​

A workflow starts with a Trigger, evaluates optional Conditions, and performs one or more Actions such as Email or SMS notifications.


Available Components​

Trigger​

The Trigger node defines how the workflow starts.

info

Every workflow must contain exactly one Trigger node.

Examples

  • Machine Alarm Generated
  • Production Target Achieved
  • Machine Downtime Detected
  • Maintenance Due

If Condition​

The If Condition node evaluates a rule before proceeding to the next workflow step.

Example

Temperature > 80°C

If the condition evaluates to True, the workflow follows one path; otherwise, it follows an alternative path.


Email​

The Email node sends automated email notifications.

Common Uses

  • Maintenance reminders
  • Alarm notifications
  • Production reports
  • Escalation alerts

SMS​

The SMS node sends text message notifications.

Common Uses

  • Critical machine alarms
  • Emergency notifications
  • Production stoppages

Creating a Workflow​

Step 1 — Add a Trigger​

Drag a Trigger component onto the workflow canvas.

Step 2 — Add Workflow Actions​

Drag required nodes such as:

  • If Condition
  • Email
  • SMS

Step 3 — Connect Nodes​

Connect nodes to define the execution path.

Example:

Trigger
↓
Condition
↓
Email

Step 4 — Configure Nodes​

Select a node and configure its settings.

Node TypeConfiguration
TriggerEvent source
ConditionRule expression
EmailRecipients, Subject, Message
SMSPhone Number, Message

Step 5 — Save Workflow​

Save the workflow once all required nodes are connected and configured.


Example Workflow​

Machine Temperature Monitoring​

Result​

When the machine temperature exceeds 80°C:

  1. An SMS alert is sent.
  2. An Email notification is generated.
  3. Responsible users are informed immediately.

Workflow Validation​

Before saving, verify the following:

  • Trigger node is configured
  • All nodes are connected
  • Required fields are completed
  • Email recipients are specified
  • SMS recipients are specified
  • No disconnected nodes exist

Best Practices​

tip

Keep workflows simple and easy to maintain.

tip

Use meaningful condition rules to avoid unnecessary notifications.

tip

Test workflows before enabling them in production.


Common Use Cases​

ScenarioAction
Machine AlarmSend Email and SMS
Maintenance ReminderSend Email
Production CompletionNotify Supervisor
Machine DowntimeEscalate Alert
Quality FailureTrigger Corrective Action

Benefits​

  • Automated business processes
  • Faster response to machine events
  • Reduced manual intervention
  • Improved operational visibility
  • Consistent notification management
  • Better production monitoring