Hey, at this point in this project, you have already learned how to use some very important elements
in any new red flow.
For example, you're now looking at the desert 22 flu.
You're familiar with it.
And in it you have seen how to use the inject note.
This one right here, of course, the debug node, the function node, although we're doing a lot more
work with it later on and a few other nodes here as well.
In this in the next few lectures, I want to take you through a series of short presentations and examples
of how to use some of the other common and function nodes.
There's many more, of course, as you can see down here, especially those nodes that have to do with
communications, for example, the quiddity, communications and WebSocket.
But I prefer to show you how to use those particular notes in context as part of the project instead
of in individual lectures.
So let's get started right away with the complete node so you'll find the complete node right here on
the common.
So with the complete note, does is that it links to any other node in the flow and it will fire when
that particular node completes processing an incoming message.
So I've already set it up.
And the way that this works is to tell it which node you'd like it to monitor.
And then as soon as that node completes its operation and the complete node will fire and do something
useful, it will pass whatever message goes into the note that it is monitoring and then you can reuse
it in some other part of your flow.
So here I've set my complete note to look at the test function, which is this function right here,
and when this function completes operation, then the complete note will notice it and pass the message
over to the completed Dipak node.
So deploy it and open up the debug window or configured to show us what's going on in the current flow.
And I'm just going to trigger the test function.
And there you can see the completed debug mode has produced the message that came to it via the complete
note, just noticed that of disabled the message one, two and three debug nodes so that we can get
a more clean output here.
Of course, I can change the note that my complete note is monitoring, let's make it message one,
for example, and I'll have to enable message one.
And then deploy and trigger, and you see that in this case, Miss one is the note that upon completion
triggered the completed node and it's passing through the appropriate message payload one, which is
what came out of this.
OK, let's move on to the next simple note, which is the error note.