| Topic | Presenter | Summary | Duration |
| -------------------------------- | ------------ | ------------------------------------------------------------ | -------- |
| C4: Common Types of Nodes Part 1 | Johnathan L. | This video goes over some of the more common types of nodes. | 5:32 |00:00:07.850 --> 00:00:10.181 In this video I'm just going to go over00:00:10.181 --> 00:00:12.506 some of the more common types of nodes.00:00:12.510 --> 00:00:15.246 So probably the most common one is going,00:00:15.250 --> 00:00:18.326 or ones are going to be. We get node,00:00:18.326 --> 00:00:20.720 which as discussed in the previous video,00:00:20.720 --> 00:00:22.430 it will take its input.00:00:22.430 --> 00:00:25.058 It will use its its path parameter and pull00:00:25.058 --> 00:00:27.898 off this particular property from its input.00:00:27.900 --> 00:00:30.978 Then just send it along with your top hits.00:00:33.540 --> 00:00:34.792 The next most common,00:00:34.792 --> 00:00:37.560 though it is going to be field field,00:00:37.560 --> 00:00:39.905 so field field is a template node,00:00:39.910 --> 00:00:42.192 meaning that it actually takes other types00:00:42.192 --> 00:00:44.259 as parameters and you instantiate it.00:00:44.260 --> 00:00:46.786 So in this case the field00:00:46.786 --> 00:00:49.436 field node is actually taking a00:00:49.436 --> 00:00:52.064 Shopify order and an ECS order.00:00:52.070 --> 00:00:53.995 Now, in the case of field field,00:00:54.000 --> 00:00:55.398 this means that he will take00:00:55.398 --> 00:00:57.467 in a shot of order and it will00:00:57.467 --> 00:00:59.485 output and ECS order based on the00:00:59.485 --> 00:01:00.897 mapping stored in database.00:01:03.010 --> 00:01:06.195 This node requires no inputs are no00:01:06.195 --> 00:01:07.560 configuration variables whatsoever.00:01:10.000 --> 00:01:13.483 And so the way that this works is it00:01:13.483 --> 00:01:17.186 will attempt to use the it's into port.00:01:17.190 --> 00:01:20.110 To place the values onto.00:01:20.110 --> 00:01:21.762 However, if there is no end to00:01:21.762 --> 00:01:23.518 it will create just a new new00:01:23.518 --> 00:01:25.000 version of whatever is output is00:01:25.055 --> 00:01:27.071 in this case in ECS order and then00:01:27.071 --> 00:01:29.720 start mapping its inputs onto a.00:01:29.720 --> 00:01:31.496 You might use this, for example,00:01:31.500 --> 00:01:34.041 if you wanted to make sure that00:01:34.041 --> 00:01:35.930 certain values are preserved.00:01:35.930 --> 00:01:38.324 So you only create you only set00:01:38.324 --> 00:01:40.500 them on creation but not update.00:01:40.500 --> 00:01:43.146 So you would take the existing objects,00:01:43.150 --> 00:01:46.166 sending the inputs and then map on that.00:01:49.860 --> 00:01:51.210 The control part is typically only00:01:51.210 --> 00:01:52.680 used for errors in finding the00:01:52.680 --> 00:01:54.456 mappings in the database, so you don't00:01:54.456 --> 00:01:56.150 have to worry about that too much.00:01:59.120 --> 00:02:01.325 Another common one is the print node,00:02:01.330 --> 00:02:03.922 so the print node takes things value and it00:02:03.922 --> 00:02:06.370 will always output the exact same value.00:02:06.370 --> 00:02:08.830 So you can actually just insert00:02:08.830 --> 00:02:10.470 this anywhere to pipeline.00:02:10.470 --> 00:02:12.478 So for example, I might want to take.00:02:15.700 --> 00:02:17.030 I'll make another one of these guys.00:02:19.720 --> 00:02:21.952 Let's say that I wanted to know what00:02:21.952 --> 00:02:24.040 the value of that customer ID was.00:02:24.040 --> 00:02:26.791 Smooth these guys over so you see00:02:26.791 --> 00:02:30.989 doesn't look too bad. Then we could.00:02:30.990 --> 00:02:35.560 Disconnected us he kept it's. Two here.00:02:41.380 --> 00:02:43.189 Looking oatmeal hippie.00:02:46.370 --> 00:02:51.459 Now for exactly no change in functionality.00:02:51.460 --> 00:02:53.280 It will take the customer ID and00:02:53.280 --> 00:02:55.278 print it out to the console ends,00:02:55.280 --> 00:02:56.918 also appearing in the debug logs.00:02:56.920 --> 00:02:59.660 If you have configured.00:02:59.660 --> 00:03:01.270 Ends keep on passing through.00:03:03.700 --> 00:03:07.580 So this has something that you can configure.00:03:07.580 --> 00:03:09.604 And this is going to get a little00:03:09.604 --> 00:03:11.238 bit further into the programming00:03:11.238 --> 00:03:13.522 aspect of things. So the trick?00:03:13.522 --> 00:03:16.786 No, it allows you to configure whether or00:03:16.786 --> 00:03:19.936 not you want to turn its input into Jason.00:03:19.940 --> 00:03:22.579 It allows you to configure a regular00:03:22.579 --> 00:03:24.511 expression to match against either00:03:24.511 --> 00:03:27.073 the Jason or the two string value.00:03:29.120 --> 00:03:32.108 It allows you to specify a00:03:32.108 --> 00:03:33.602 handlebar style template.00:03:33.610 --> 00:03:36.634 Can you still allows you to specify?00:03:36.640 --> 00:03:40.208 Obviously the value the.00:03:40.210 --> 00:03:43.948 Heavy level to which are bubble of00:03:43.948 --> 00:03:48.167 log to use when logging into R0.00:03:48.170 --> 00:03:50.067 Sounds what control you want to output.00:03:59.890 --> 00:04:01.850 So for example, if I wanted to,00:04:01.850 --> 00:04:04.090 let's say that I was, let's say I'm00:04:04.090 --> 00:04:06.050 not taking the customer ID in here.00:04:06.050 --> 00:04:08.426 I'm just taking a customer itself.00:04:08.430 --> 00:04:10.620 Or actually even even better example.00:04:20.740 --> 00:04:22.335 Let's say that I didn't00:04:22.335 --> 00:04:23.930 have this git node here.00:04:23.930 --> 00:04:25.748 And that I just wanted to00:04:25.748 --> 00:04:27.741 take the customer ID off of00:04:27.741 --> 00:04:28.809 this thing directly.00:04:28.810 --> 00:04:29.740 I can do a value in.00:04:32.870 --> 00:04:34.118 Add my format string.00:04:36.960 --> 00:04:41.589 And say that I want the. Customer that ID.00:04:43.740 --> 00:04:45.396 Maybe a little prettiness around it.00:05:00.950 --> 00:05:03.356 So now when this node executes,00:05:03.360 --> 00:05:06.958 it will take in the order object.00:05:06.960 --> 00:05:10.866 It will then run through its format.00:05:10.870 --> 00:05:13.145 It will replace the part and handlebars00:05:13.145 --> 00:05:15.802 here ID with the ID of the order and00:05:15.802 --> 00:05:17.819 then the other part in handlebars.00:05:17.820 --> 00:05:20.324 Customer ID with the customer of that order00:05:20.324 --> 00:05:22.879 and then take the idea of that customer.