1
00:00:00,480 --> 00:00:07,900
Hey, at this point in this project, you have already learned how to use some very important elements

2
00:00:07,950 --> 00:00:10,260
in any new red flow.

3
00:00:10,710 --> 00:00:14,760
For example, you're now looking at the desert 22 flu.

4
00:00:14,760 --> 00:00:15,720
You're familiar with it.

5
00:00:15,900 --> 00:00:20,390
And in it you have seen how to use the inject note.

6
00:00:20,430 --> 00:00:26,550
This one right here, of course, the debug node, the function node, although we're doing a lot more

7
00:00:26,550 --> 00:00:31,290
work with it later on and a few other nodes here as well.

8
00:00:31,650 --> 00:00:38,700
In this in the next few lectures, I want to take you through a series of short presentations and examples

9
00:00:38,700 --> 00:00:42,240
of how to use some of the other common and function nodes.

10
00:00:42,510 --> 00:00:48,690
There's many more, of course, as you can see down here, especially those nodes that have to do with

11
00:00:48,690 --> 00:00:53,550
communications, for example, the quiddity, communications and WebSocket.

12
00:00:53,820 --> 00:01:01,560
But I prefer to show you how to use those particular notes in context as part of the project instead

13
00:01:01,560 --> 00:01:04,270
of in individual lectures.

14
00:01:04,740 --> 00:01:13,350
So let's get started right away with the complete node so you'll find the complete node right here on

15
00:01:13,350 --> 00:01:13,980
the common.

16
00:01:14,340 --> 00:01:21,420
So with the complete note, does is that it links to any other node in the flow and it will fire when

17
00:01:21,420 --> 00:01:25,620
that particular node completes processing an incoming message.

18
00:01:26,250 --> 00:01:27,930
So I've already set it up.

19
00:01:27,930 --> 00:01:35,540
And the way that this works is to tell it which node you'd like it to monitor.

20
00:01:35,790 --> 00:01:43,680
And then as soon as that node completes its operation and the complete node will fire and do something

21
00:01:43,680 --> 00:01:52,200
useful, it will pass whatever message goes into the note that it is monitoring and then you can reuse

22
00:01:52,200 --> 00:01:54,060
it in some other part of your flow.

23
00:01:56,400 --> 00:02:03,260
So here I've set my complete note to look at the test function, which is this function right here,

24
00:02:04,590 --> 00:02:12,450
and when this function completes operation, then the complete note will notice it and pass the message

25
00:02:12,450 --> 00:02:15,510
over to the completed Dipak node.

26
00:02:16,140 --> 00:02:24,540
So deploy it and open up the debug window or configured to show us what's going on in the current flow.

27
00:02:24,810 --> 00:02:27,420
And I'm just going to trigger the test function.

28
00:02:29,160 --> 00:02:36,870
And there you can see the completed debug mode has produced the message that came to it via the complete

29
00:02:36,870 --> 00:02:43,920
note, just noticed that of disabled the message one, two and three debug nodes so that we can get

30
00:02:43,920 --> 00:02:46,070
a more clean output here.

31
00:02:48,860 --> 00:02:57,140
Of course, I can change the note that my complete note is monitoring, let's make it message one,

32
00:02:57,140 --> 00:03:00,290
for example, and I'll have to enable message one.

33
00:03:01,310 --> 00:03:11,090
And then deploy and trigger, and you see that in this case, Miss one is the note that upon completion

34
00:03:11,090 --> 00:03:18,500
triggered the completed node and it's passing through the appropriate message payload one, which is

35
00:03:18,500 --> 00:03:19,370
what came out of this.

36
00:03:22,430 --> 00:03:27,170
OK, let's move on to the next simple note, which is the error note.