Component overview
This page provides a short recap of the components with links to the in-depth documentation.
Input Nodes​
CSV Input​
Read a line from a CSV input file and place it into memory whenever the node executes and there is data available. The data identifier is a name that can be specified for shared access of the same datasource from different locations in a diagram.
Workflow continuation (following decision): 'next' or 'end reached'
User input​
Allows to collect input from a user. The user may be asked to fill in multiple fields to continue. This node will pause the workflow until either a user entered the requested data or a timeout occurs.
Excel Input​
This feature is planned but not yet supported.
Output Nodes / Collect Data from workflow​
CSV Output​
Appends selected variables from the workflow to a comma-separated values file.
Workflow continuation (following decision): 'next'
Action Nodes​
Send E-Mail​
Sends an E-Mail via the SMTP protocol uses the variables in the memory to perform text replacements in subject, text and html content of the message.
Receive E-Mail​
Receives an E-Mail via the IMAP protocol and stores the message into memory for further processing.
Move E-Mail​
With IMAP you can move a received mail to another folder, e.g. if a condition was met in one of the previous decisions.
Question Answering (AI text prompting)​
Uses an artificial intelligence API endpoint to perform topic based text generation and stores the result in a variable for further processing ..more details.
Text Analysis Nodes​
Sentiment detection​
Detects positive, negative or neutral sentiment in a text depending on the selected algorithm, and stores the result in a variable for further processing ..more details
Decision​
UML-Decision​
A regular decision node that can switch modes of operation;
-
Activity based uses information from the previous action to determine workflow continuation
-
Regular expression a regular expression matcher on a certain variable
-
Spring expression language (SpEL) allows to evaluate variables in the current memory context.
Click response​
Special decision node used after a [send e-mail activity](actions/E-Mail/Send E-Mail.md). It decides which outgoing edge the control flow should take based on the selection of the user/e-mail receiver who is able to click on a link.
The creation of an outgoing edge specifies a discrete response. It is used to create a link in the editor of the message being sent .
Events​
Scheduled Timer event​
Register a regular occurring event that always triggers the execution of the workflow in a certain time interval.
Fetch E-Mail event​
Registers an event that triggers upon an incoming E-Mail.
Concurrency​
Fork​
A UML fork node is used to split a single incoming control flow into multiple concurrent outgoing flows, allowing for parallel execution of activities or actions in an activity diagram. It is a fundamental element for representing concurrent behavior in UML diagrams, but it does not involve synchronization or waiting for conditions like a UML join node does.
Join​
With this node several processes can be joined. A workflow only continues when the last execution arrived at the join node. That way it acts as a barrier synchronization point. The node is also useful in combination with events since it allows to keep up the registration, see the event details for an example.
Final Node​
The final node is used to denote the end of a specific flow within an activity diagram. It indicates the successful completion or termination of that particular flow, but it doesn't mean the termination of the entire activity, (see the end node for this).
See also details on final and end node.
Event Node​
Event nodes are used to model points in a system's behavior where an event triggers an action or transitions occur based on specific events.
Other​
UML Start​
Indicates a workflow start.
UML End​
The UML end node represents the termination of the entire activity or behavior within an activity diagram. It indicates the successful completion of the entire process or workflow.
When the control flow of an activity diagram finishes as an end node is reached, all event registrations are cleared.
See also details on final and end node.
UML Note​
May be used to textually describe a particular node further. ..more details
Python script​
Execute a custom python script. Use variables and optionally create a result and also determine which branch to take on a decision node.
Add variable​
Allows to combine several variables or extract a text via a regular expression and set it as a new variable.