A simple flow for beginners, which shows basic functionality of some components.
Let us explain how this workflow works: This workflow consists of three individual small workflows.
Why do we need three different small workflows here? On the one hand to show you what Exolink can do and on the other hand to show you three different ways of data processing. In the first workflow, the data is only counted. In the second workflow, the data is converted before it is processed further and in the third workflow, the data is collected up to a certain number before it is processed.
Workflow 1 and 2 are triggered by the "Hello world" component.
Click on the square icon below the component to trigger the workflow manually. Of course, you don't have to manually trigger every workflow in the future, but in this case we wanted you to have something to do as well. 😉
When triggering one of the "Hello world" components, a string is send on the output side. In this case it is "Hello world". By double-clicking on the component, the sample data can be replaced.
The output of the first trigger is passed on to two other components: First, the output of the trigger component is passed on to the input of the debug component. The second output leads to a counter component that increases a counter whenever data is received. The counter is displayed above the component.
The debug component displays the transmitted data in the console, which can be found in the sidebar.
Let's move to the second workflow and look at the trigger component. The second trigger component sends its output to a code component: Upper case.
In this case, the incoming data ("Hello world") is converted into capital letters.
Let us now look at the third workflow. This one is started time-controlled, which means it is automatically triggered (here: every five seconds). No static text is stored, as in the two trigger components above, but a code component dynamically generates its output on the basis of the current date. In short: This component throws out the current date.
The code component passes its output to two components: Once to the merge component and to another debug component. The merge component collects the incoming data until a certain counter is reached. This number is stored in the merge component and has been set here beforehand. In this case, five times data is collected and afterwards the merge component passes them on to the debug component. That´s it – have fun testing! 😊
We get back to you as soon as possible.