00:00:03.409 --> 00:00:05.249 In here, that would be. That would be lovely.
00:00:05.859 --> 00:00:06.419 Oh yeah.
00:00:06.849 --> 00:00:11.058 OK, great. So I have two sites pulled up here. One is CMC's
00:00:11.058 --> 00:00:11.829 prod which?
00:00:12.929 --> 00:00:17.884 Is a kind of hybrid between C3 and C5 and C5 is our new is. Is
00:00:17.884 --> 00:00:22.759 the kind of the newest version and kind of iteration. So Como
00:00:22.759 --> 00:00:27.635 is fully see five but it doesn't have as many jobs running or
00:00:27.635 --> 00:00:32.197 there's a couple succeeded in here, but they're just some
00:00:32.197 --> 00:00:36.679 tests so I wanted to show some internal jobs as well so.
00:00:38.039 --> 00:00:42.319 When you get to this screen now, there are some customizations in
00:00:42.319 --> 00:00:46.404 here that we've made and and go from there. So if I don't know
00:00:46.404 --> 00:00:50.554 if anyone seen the old version of Hangfire, but there were some
00:00:50.554 --> 00:00:52.629 like these batches are here now.
00:00:53.829 --> 00:00:54.879 And.
00:00:53.929 --> 00:00:55.779 Ooh, what's that do?
00:00:56.009 --> 00:01:01.397 Yeah. So the, the, the kind of the older version of the way we
00:01:01.397 --> 00:01:05.159 used to do jobs was you would run a single.
00:01:06.479 --> 00:01:10.150 Single job and inside of that one job there would be a lot of
00:01:10.150 --> 00:01:13.939 a lot of information about here. I think I might even have one.
00:01:16.619 --> 00:01:17.559 Well, that's unfortunate.
00:01:17.859 --> 00:01:20.749 Umm, but let me see if this one has it.
00:01:22.259 --> 00:01:24.669 There we go. That's probably has what we're looking for.
00:01:26.799 --> 00:01:30.091 So for example, here in the inventory sync what we used to
00:01:30.091 --> 00:01:33.774 do was inside the inventory sync we would just do all 2098 active
00:01:33.774 --> 00:01:37.122 stock codes. Now granted in this scenario it's not actually
00:01:37.122 --> 00:01:40.526 outputting anything because nothing was changed because this
00:01:40.526 --> 00:01:43.986 is the stage environment. So let me see if I can find like an
00:01:43.986 --> 00:01:46.329 order sync to see if that doesn't have 0.
00:01:49.849 --> 00:01:50.789 Are you guys still there?
00:01:51.089 --> 00:01:51.739 Yeah, we're here.
00:01:51.819 --> 00:01:55.245 OK, sorry my the other the weekly dev training. Somebody
00:01:55.245 --> 00:01:59.091 removed me so I got the hang up notification sound. Anyway what
00:01:59.091 --> 00:02:02.937 we would do is we would we would run this order sync scepticism
00:02:02.937 --> 00:02:06.482 Pro and the inventory sync and the customer sync and every
00:02:06.482 --> 00:02:10.208 single customer that would need to sync inside of there would
00:02:10.208 --> 00:02:14.115 would run all in one all in one thing and so it would be we just
00:02:14.115 --> 00:02:18.021 need to use these logs to output and the problem was that if one
00:02:18.021 --> 00:02:21.687 job failed we'd have to like aggregate it and then we'd have
00:02:21.687 --> 00:02:23.249 to do all these things to.
00:02:23.339 --> 00:02:26.190 Ensure that the next time it ran, you know it only picked up
00:02:26.190 --> 00:02:29.228 that job or it picked up all of them still, and it only ran, you
00:02:29.228 --> 00:02:30.349 know, do all its checks.
00:02:31.399 --> 00:02:35.713 What we're doing now is batches, and so the idea of the batch is
00:02:35.713 --> 00:02:39.893 that there is an exterior job, an external job that starts the
00:02:39.893 --> 00:02:43.941 whole thing. So we still have a customer sync, but for every
00:02:43.941 --> 00:02:48.122 customer picked up by connect, that says I need to update this
00:02:48.122 --> 00:02:52.302 customer. So for example, let's say the customer sync runs and
00:02:52.302 --> 00:02:56.417 it finds 10 customers that need to run. What it will do is it
00:02:56.417 --> 00:03:00.266 will queue and inner job 10 times for all those different
00:03:00.266 --> 00:03:00.929 customers.
00:03:01.259 --> 00:03:04.516 And what that looks like here in the batches and you can these.
00:03:04.516 --> 00:03:07.112 This is just kind of the progress for all of these
00:03:07.112 --> 00:03:10.216 batches. You can actually come in here and see, OK, seven of
00:03:10.216 --> 00:03:13.218 them have ran, you know, where it four out of 10 if you're
00:03:13.218 --> 00:03:16.272 doing products, you'll see a bigger number. Looks like they
00:03:16.272 --> 00:03:18.969 haven't cleaned this up in a while, but here we are.
00:03:19.289 --> 00:03:23.131 Umm, there are the output though is you'll get more
00:03:23.131 --> 00:03:27.858 individualized things, so this is PA231 sync to HubSpot. Now, I
00:03:27.858 --> 00:03:32.365 don't know CMMC very well, so I don't know exactly what that
00:03:32.365 --> 00:03:37.019 means, but the thought process there is that if you're syncing
00:03:37.019 --> 00:03:41.525 customers, then the inner job could say syncing customer 123
00:03:41.525 --> 00:03:45.736 to two HubSpot, which are 231PA231 to HubSpot. And so if
00:03:45.736 --> 00:03:49.429 this customer sync fails, then in the failed job.
00:03:49.519 --> 00:03:55.504 You can go see why did this this specific one fail and you can
00:03:55.504 --> 00:04:00.729 requeue just that customer or just that job. Yeah, so.
00:03:56.629 --> 00:03:58.509 Oh my God, that's a thing of beauty.
00:04:01.689 --> 00:04:05.674 Kudos to the to the some of the new Connect devs, and I think
00:04:05.674 --> 00:04:09.851 JLR was a big a big key in this one for Sean MC and then brought
00:04:09.851 --> 00:04:12.679 into C5 that this is really we kind of had.
00:04:13.459 --> 00:04:16.949 Sniffs of it here or there and see three. You know, I think on
00:04:16.949 --> 00:04:20.161 GLV actually, or maybe it was mastercutlery. I do it on a
00:04:20.161 --> 00:04:23.318 couple things, but this is really nice because it allows
00:04:23.318 --> 00:04:26.752 for you to see exactly which ones failed and go requeue those
00:04:26.752 --> 00:04:30.020 specifically. So if like for example, this one, no company
00:04:30.020 --> 00:04:33.509 associated the deal, you could go associate the company to the
00:04:33.509 --> 00:04:37.054 deal and then requeue it and it would sync appropriately and it
00:04:37.054 --> 00:04:40.267 would just sync this one. So it allows for you to be more
00:04:40.267 --> 00:04:42.039 granular. Now what that does do.
00:04:42.749 --> 00:04:46.759 Is it adds a lot of a lot of extra jobs in here, right? So
00:04:46.759 --> 00:04:50.973 rather than running, you know the customer sync once an hour.
00:04:50.973 --> 00:04:55.052 If it finds 100 customers that need to sync every hour, now
00:04:55.052 --> 00:04:56.139 you've got 2400.
00:04:56.589 --> 00:04:58.319 Uh, you know jobs for the day.
00:05:00.259 --> 00:05:02.059 But the nice thing is go ahead.
00:05:00.619 --> 00:05:00.919 What?
00:05:02.539 --> 00:05:09.745 What does that do in terms of the resource requirements for an
00:05:09.745 --> 00:05:10.889 end users?
00:05:11.649 --> 00:05:14.179 Set up our client setup.
00:05:13.869 --> 00:05:17.139 Yeah, that's a great question. So the way that the batch works
00:05:17.139 --> 00:05:20.564 and we're gonna kind of get into some the technical aspects of it
00:05:20.564 --> 00:05:20.979 is that.
00:05:22.219 --> 00:05:25.401 It ultimately looks at the number of threads on the
00:05:25.401 --> 00:05:29.134 computer, like the number of threads in the processor and it
00:05:28.209 --> 00:05:28.529 Umm.
00:05:29.134 --> 00:05:32.989 batches it based off of that. So for example, if you have a A4
00:05:32.989 --> 00:05:36.538 core processor, technically there's two virtual cores per
00:05:36.538 --> 00:05:40.210 core and I might be explaining that slightly wrong, but the
00:05:40.210 --> 00:05:43.698 math is still the same. So ultimately you have 8 threads
00:05:43.698 --> 00:05:47.063 and so it will run 8 jobs at a time, whichever it will
00:05:47.063 --> 00:05:50.857 basically queue all these jobs up and it will run 8 at a time
00:05:50.857 --> 00:05:52.509 and so it shouldn't affect.
00:05:52.829 --> 00:05:57.588 The IT shouldn't affect the the resources that much you know,
00:05:57.588 --> 00:05:58.969 unless you've got.
00:06:00.319 --> 00:06:03.353 It would, it would be kind of specific, so it shouldn't
00:06:03.353 --> 00:06:06.225 increase the the resource requirement hardly at all,
00:06:06.225 --> 00:06:09.259 because it will it will. It will kind of self regulate.
00:06:09.919 --> 00:06:14.969 OK. So it'll just kind of queue things until it has enough.
00:06:16.099 --> 00:06:18.411 Does until it doesn't have any threads. Yeah, until it doesn't.
00:06:16.179 --> 00:06:17.029 Bandwidth.
00:06:18.069 --> 00:06:18.429 Yeah.
00:06:18.411 --> 00:06:19.459 Any threads left to use? Yep.
00:06:19.899 --> 00:06:21.009 OK, beautiful.
00:06:21.019 --> 00:06:26.189 And the net result of that, because it's more fault tolerant
00:06:26.189 --> 00:06:31.358 is we've seen it process CMMC faster, more accurately with a
00:06:31.358 --> 00:06:36.274 higher success rate while occupying fewer start to finish
00:06:36.274 --> 00:06:41.189 system resources because you don't have something hung up
00:06:41.189 --> 00:06:42.799 unable to complete.
00:06:44.459 --> 00:06:48.318 Correct. Yeah. So for example, if right, what what Charlie
00:06:44.699 --> 00:06:45.379 OK.
00:06:48.318 --> 00:06:52.308 saying there is that and and in a similar vein, let's say it
00:06:52.308 --> 00:06:54.009 finds those 100 customers.
00:06:55.099 --> 00:06:58.273 Well, the way the old job used to work is that it would find
00:06:58.273 --> 00:07:01.656 those hundred and it would sink them well if one customer failed
00:07:01.656 --> 00:07:04.570 in there to ensure that that customer got gets properly
00:07:04.570 --> 00:07:07.953 synced the next time, it doesn't change its last run date and so
00:07:07.953 --> 00:07:11.179 the next time it runs in the next hour, it will find the past
00:07:11.179 --> 00:07:13.989 two hours worth of customers. And so it will find 200
00:07:13.989 --> 00:07:17.267 customers. And if that one fails again, now you're looking at,
00:07:17.267 --> 00:07:20.546 you know, you understand where I'm going with this, that those
00:07:18.829 --> 00:07:19.489 Ah ha.
00:07:20.546 --> 00:07:23.824 resources, even though we might have checks in there that just
00:07:23.824 --> 00:07:25.229 it's a simple check to say.
00:07:25.539 --> 00:07:28.985 You know has any data change? No, it hasn't. It still has to
00:07:28.985 --> 00:07:32.375 go retrieve that record and do that calculation. And so now
00:07:32.375 --> 00:07:35.256 you're increasing whereas whereas if we queue them
00:07:35.256 --> 00:07:38.815 individually, we can segregate them down to a single thing and
00:07:38.815 --> 00:07:42.091 not prevent other things from succeeding just because one
00:07:42.091 --> 00:07:42.769 piece fails.
00:07:43.819 --> 00:07:44.329 OK.
00:07:45.219 --> 00:07:49.580 So I'm going to pause there and I wanna I I'm gonna pick on some
00:07:49.580 --> 00:07:50.049 people.
00:07:51.469 --> 00:07:53.539 Because I'm a monster, Amy.
00:07:54.309 --> 00:07:55.679 From what you just heard.
00:07:56.879 --> 00:07:57.319 Yes.
00:07:56.919 --> 00:08:01.247 I want you to think about some of the struggles that you've had
00:08:01.247 --> 00:08:05.237 with a couple of projects recently and tell me one of them
00:08:05.237 --> 00:08:07.739 that would have benefited from this.
00:08:09.149 --> 00:08:12.803 Yeah. So one example I can think of is with handy. They're sage
00:08:12.803 --> 00:08:16.115 instance. They have a lot of like duplicate customers and
00:08:16.115 --> 00:08:18.399 incorrect emails and or invalid emails.
00:08:19.159 --> 00:08:22.268 So when we were running the customer sync after Scarlett had
00:08:22.268 --> 00:08:23.899 kind of tweaked it a little bit.
00:08:24.589 --> 00:08:27.755 It was stopping on that first, like when he ran the sink, it
00:08:27.755 --> 00:08:30.921 would stop on the first air and then basically the error was
00:08:30.921 --> 00:08:34.087 that it was an invalid e-mail. So I would like what you just
00:08:34.087 --> 00:08:37.408 explained of like if it runs a whole batch and it can basically
00:08:37.408 --> 00:08:40.678 skip that one so that the next time it runs it doesn't have to
00:08:40.678 --> 00:08:42.079 do that entire batch again.
00:08:42.719 --> 00:08:45.804 So it's like say that the there was like 100 customers at it or
00:08:45.804 --> 00:08:47.829 a customer accounts that it syncing over?
00:08:48.889 --> 00:08:51.823 If that one didn't work that one time then like I guess this
00:08:51.823 --> 00:08:53.169 would kind of benefit there.
00:08:53.819 --> 00:08:56.333 So that that next time it would just sync that one that didn't
00:08:56.333 --> 00:08:57.689 get synced. Does that make sense?
00:08:58.109 --> 00:09:01.488 Well, it wouldn't. It wouldn't necessarily, just it wouldn't
00:09:01.488 --> 00:09:05.033 pick up that one that didn't get synced. What it would do is it
00:09:05.033 --> 00:09:08.522 would pick up the new batch. And so technically you do need to
00:09:08.522 --> 00:09:08.799 well.
00:09:10.539 --> 00:09:14.159 There's kind of two ways to go about it, and I think one is
00:09:14.159 --> 00:09:17.719 preferred over the other, but ultimately it is what it is.
00:09:18.839 --> 00:09:22.645 We typically will e-mail when errors happen and I don't know
00:09:22.645 --> 00:09:26.202 if it's happening on CMMC, but we're actually building a
00:09:26.202 --> 00:09:30.008 feature for core for the core part that when a job fails, it
00:09:30.008 --> 00:09:33.689 will automatically send an e-mail with the exception error
00:09:33.689 --> 00:09:37.620 to whoever. And so if we make this up, we can make the subject
00:09:37.620 --> 00:09:41.613 line error in the customer sync syncing customer 123 right. And
00:09:41.613 --> 00:09:45.169 so when whoever is a CSR, whoever's on receiving on that
00:09:45.169 --> 00:09:48.289 end, they can go in and see what the problem was.
00:09:48.449 --> 00:09:52.472 And then there's kind of two things they can do. Either one,
00:09:52.472 --> 00:09:56.429 they can just go fix the error and the because the customer
00:09:56.429 --> 00:10:00.320 sync runs off of like updated dates if they're in a system
00:10:00.320 --> 00:10:01.639 like let's say Seth.
00:10:02.799 --> 00:10:06.097 Where let's say the customer didn't have. I don't know an
00:10:06.097 --> 00:10:09.452 address for whatever reason, that person could go, the CSR
00:10:09.452 --> 00:10:12.580 could go into CEF and add the add the address for that
00:10:12.580 --> 00:10:16.048 customer and the updated date would modify. So connect would
00:10:16.048 --> 00:10:19.631 pick it up and its next cycle just because it had been updated
00:10:19.631 --> 00:10:23.270 since the last time. The other option and technically both work
00:10:23.270 --> 00:10:25.999 is that you can go in here and see failed jobs.
00:10:26.849 --> 00:10:30.571 And it allows me to see that user not found in Seth. Ohh. OK
00:10:30.571 --> 00:10:34.354 well how do I fix that? It may be my maybe for for CMMC my my
00:10:34.354 --> 00:10:38.014 resolution for user not found in Seth is I just go manually
00:10:38.014 --> 00:10:41.797 create the user in CEF and then I can come back in here and I
00:10:41.797 --> 00:10:45.641 can click check and I can click requeue job and what that does
00:10:45.641 --> 00:10:49.546 now is it will now do the exact same thing it did before except
00:10:49.546 --> 00:10:53.206 now it will probably find the user and stuff which means it
00:10:53.206 --> 00:10:56.806 will succeed. So it's not necessarily that you run 100 and
00:10:56.806 --> 00:10:57.599 if one fails.
00:10:57.699 --> 00:11:01.310 That one automatically gets picked up in the next time it's
00:11:01.310 --> 00:11:05.162 that one fails. You can see why it failed. Go fix the issue and
00:11:05.162 --> 00:11:08.953 then depending on the system, it will either automatically get
00:11:08.953 --> 00:11:12.684 picked up technically as a new update, or you can go manually
00:11:12.684 --> 00:11:14.369 run the old one that failed.
00:11:15.199 --> 00:11:18.339 Ohh OK yeah, the being able to see it like this and where you
00:11:18.339 --> 00:11:21.478 just kind of highlight it and clicked or you didn't click it,
00:11:21.478 --> 00:11:24.567 but you just kind of hovered over that button, but that made
00:11:22.919 --> 00:11:23.439 Uh-huh.
00:11:24.567 --> 00:11:25.529 it much more clear.
00:11:25.919 --> 00:11:29.524 OK, sure. Yeah. So 72,000 is a lot. My guess is that it's some
00:11:29.524 --> 00:11:32.899 of these are probably just getting ready. You know they're
00:11:32.899 --> 00:11:36.275 they're being fixed along the way and probably just redone
00:11:36.275 --> 00:11:39.937 being caught in the succeeded as like a reupdate, Charlie would
00:11:39.937 --> 00:11:43.313 speak more about that, but that's not necessarily specific
00:11:43.313 --> 00:11:47.032 to this call, but theoretically in a perfect world, somebody who
00:11:47.032 --> 00:11:50.522 could be monitoring this or receiving the emails, they could
00:11:50.522 --> 00:11:53.841 just go into all the failed jobs, see why they failed, go
00:11:53.841 --> 00:11:56.129 fix them, requeue them and this failed.
00:11:56.199 --> 00:11:59.518 Has failed. Job list would basically like clean itself out,
00:11:59.518 --> 00:12:00.569 you know regularly.
00:12:02.169 --> 00:12:05.007 There's probably a much more bulk way of doing that for CMMC,
00:12:05.007 --> 00:12:07.249 since there's a lot of integrations that happen.
00:12:08.639 --> 00:12:12.862 So with the error handling that you were talking about and kind
00:12:12.862 --> 00:12:16.622 of sending the emails to the client and curious what the
00:12:16.622 --> 00:12:20.317 actual output of that is, because if you just go into a
00:12:20.317 --> 00:12:24.539 failed job and look at the more details I have specifically had
00:12:24.539 --> 00:12:28.629 clients not very many of them thankfully, but I've definitely
00:12:28.629 --> 00:12:32.390 had them in the past where they're like I can't read the
00:12:32.249 --> 00:12:32.759 Umm.
00:12:32.390 --> 00:12:34.699 gibberish. What does this mean so?
00:12:33.439 --> 00:12:39.925 Yeah, yeah. So ideally so out of box, we just we'll we'll we will
00:12:34.109 --> 00:12:34.469 Umm.
00:12:39.925 --> 00:12:45.920 just send the exception and so it will just be unfortunately
00:12:45.920 --> 00:12:47.689 probably not even.
00:12:49.219 --> 00:12:52.802 This although system exceptions, so it does look like it's this.
00:12:52.802 --> 00:12:55.998 Although this looks fairly custom, the fact that it gives
00:12:55.998 --> 00:12:59.305 the e-mail and the user not found. Most likely it will just
00:12:56.329 --> 00:12:56.789 Mm-hmm.
00:12:59.305 --> 00:13:02.943 say system exception and then at clarity all this and that's what
00:13:02.689 --> 00:13:03.459 Uh-huh.
00:13:02.943 --> 00:13:05.974 they're talking about the gibberish. So the ideal goal
00:13:05.974 --> 00:13:08.841 there is that if there's a system that has a lot of
00:13:08.841 --> 00:13:12.423 variability where there could be a lot of problems, that's where
00:13:12.423 --> 00:13:15.840 customizations come in to be more specific on the failure. So
00:13:15.840 --> 00:13:19.368 for example like this sync, this is probably a line that exists
00:13:19.368 --> 00:13:20.029 in the code.
00:13:20.099 --> 00:13:24.526 Where it says if I get a failure based on the exception type that
00:13:24.526 --> 00:13:28.618 I'm receiving from Seth, I'm going to output e-mail and user
00:13:28.618 --> 00:13:32.777 not found in Seth and there's probably a handful of different
00:13:32.777 --> 00:13:36.935 error handling messages that sends specific things out and so
00:13:36.935 --> 00:13:37.539 like for.
00:13:38.259 --> 00:13:41.206 I've heard IA or GLV I can I know that those are two
00:13:41.206 --> 00:13:44.654 completely different things, but we we had to do that and the
00:13:44.654 --> 00:13:47.991 question was like, well, maybe it's mastercutlery they kept
00:13:47.991 --> 00:13:51.494 saying, well, how do I know how to do XYZ or if this pops up a
00:13:51.494 --> 00:13:54.775 new thing pops up. How do I do it? Well, the problem is we
00:13:54.775 --> 00:13:58.168 can't error handle for every possible thing. One, they don't
00:13:58.168 --> 00:14:01.615 want to pay for that in two, it would be almost impossible to
00:14:01.615 --> 00:14:05.174 know every single failure that comes through. So ideally in the
00:14:03.859 --> 00:14:04.299 Umm.
00:14:05.174 --> 00:14:08.622 UAT process, if you know that the data is not always going to
00:14:08.622 --> 00:14:11.069 be normalized and see the exact same thing.
00:14:11.309 --> 00:14:15.050 You're seeing these errors come across regularly. Then we'll
00:14:15.050 --> 00:14:18.240 probably wanna do a customization where we say, OK,
00:14:18.240 --> 00:14:22.042 when this specific error comes across, let's output this line
00:14:22.042 --> 00:14:26.090 and let's tell all the CSRS that when you see this issue, this is
00:14:26.090 --> 00:14:29.709 how you go fix it. And that is all customizations, because
00:14:29.709 --> 00:14:33.695 again, it's their data and it's problems with their data or it's
00:14:33.695 --> 00:14:36.885 problems with whatever that we need to error handle
00:14:36.885 --> 00:14:40.380 appropriately and tell them so out of box, they just get
00:14:40.380 --> 00:14:41.239 probably this.
00:14:41.989 --> 00:14:42.859 Got it.
00:14:42.229 --> 00:14:45.362 Which they're not gonna know what to do with that. But if we
00:14:45.362 --> 00:14:48.649 see enough of these, that just means that the data is not fully
00:14:48.649 --> 00:14:51.937 normalized or the process isn't, you know, perfect. And we need
00:14:51.937 --> 00:14:55.070 some customization hours to go get better error handling and
00:14:55.070 --> 00:14:55.429 emails.
00:14:55.919 --> 00:14:58.889 So we're gonna pause you again. Hold on, Charlie.
00:14:58.539 --> 00:14:58.809 Hmm.
00:14:59.809 --> 00:15:03.199 Uh, more picking on people, Mickey.
00:15:04.699 --> 00:15:09.372 When talking data normalization and understanding kind of what's
00:15:09.372 --> 00:15:11.529 going on with the failed jobs.
00:15:13.269 --> 00:15:14.009 With.
00:15:14.809 --> 00:15:19.712 80I in particular, do you have any sense of like how they feel
00:15:19.712 --> 00:15:23.914 about reading the error messaging in connect or would
00:15:23.914 --> 00:15:26.949 they benefit from some error handling?
00:15:27.869 --> 00:15:30.659 Definitely think they would benefit for some error handling.
00:15:30.659 --> 00:15:32.579 I mean, they're pretty on top of it, but.
00:15:33.439 --> 00:15:35.049 Yeah, I think that they could.
00:15:36.129 --> 00:15:36.659 So.
00:15:36.509 --> 00:15:37.169 Then for there.
00:15:37.629 --> 00:15:39.939 In terms of that, Eric Lake.
00:15:40.989 --> 00:15:45.389 What would you say just on average for like the most common
00:15:45.389 --> 00:15:50.009 known things that we kind of do? Error handling, custom emails
00:15:50.009 --> 00:15:54.702 and stuff for like this e-mail and user not found if we were to
00:15:54.702 --> 00:15:59.322 get like a list of the common ones that kind of happen and say
00:15:59.322 --> 00:16:01.229 there's about six of them.
00:16:02.549 --> 00:16:06.606 Would you be able to kind of help estimate what the overall
00:16:06.606 --> 00:16:10.865 lift would be to create specific custom error handling for six
00:16:10.865 --> 00:16:11.879 different jobs?
00:16:13.389 --> 00:16:17.791 I mean, if if you're seeing a error consistently where it's
00:16:17.791 --> 00:16:22.046 failing in the same spot, my guess is probably an hour or
00:16:22.046 --> 00:16:22.339 two.
00:16:23.449 --> 00:16:27.150 You know an hour plus or minus to figure out exactly what the
00:16:27.150 --> 00:16:30.790 problem is. You know like, say, plus or minus. And I'm gonna
00:16:30.790 --> 00:16:34.431 keep going back to it could possibly it could be potentially
00:16:34.431 --> 00:16:37.893 much more than that, but if we're gonna ballpark it, it's
00:16:37.893 --> 00:16:41.713 probably an hour to figure out what the issue is. And then once
00:16:41.713 --> 00:16:45.413 you know the issue, writing the custom error handling and the
00:16:45.413 --> 00:16:48.039 custom e-mail based on the failure, that's.
00:16:48.799 --> 00:16:53.089 Half an hour. It's really just once you see the issue.
00:16:50.149 --> 00:16:50.549 OK.
00:16:54.119 --> 00:16:57.606 Figuring out what the problem is and is this a problem with the
00:16:57.606 --> 00:17:00.711 system not doing what it's supposed to do and we need to
00:17:00.711 --> 00:17:04.088 make it. Let's say it's CEF, right? Let's say. Let's say this
00:17:04.088 --> 00:17:07.357 user not found in CEF is some bug in registration that it's
00:17:07.357 --> 00:17:10.517 creating the account, but sometimes it's not creating the
00:17:10.517 --> 00:17:10.789 user.
00:17:12.139 --> 00:17:15.299 And again, this is very just kind of pie in the sky here.
00:17:16.999 --> 00:17:21.098 Is we need to determine OK? Is that something that that on the
00:17:21.098 --> 00:17:25.327 connect side we need to account for or do we need to go into CEF
00:17:25.327 --> 00:17:29.557 and fix that bug, right? And so it's kind of it's, I hate to say
00:17:29.557 --> 00:17:32.029 it's a Gray area, but honestly it is.
00:17:32.489 --> 00:17:32.989 Umm.
00:17:33.169 --> 00:17:37.912 Because the the information just needs to come back out and and
00:17:37.912 --> 00:17:42.063 honestly, that needs to be something that is brought to
00:17:42.063 --> 00:17:42.359 the.
00:17:43.139 --> 00:17:45.369 You know, let's say a junior developer finds, finds that
00:17:45.369 --> 00:17:47.599 issue and they get tasked with going figure out what the
00:17:47.599 --> 00:17:48.029 problem is.
00:17:49.399 --> 00:17:52.586 They need to bring it back to the PM and potentially an
00:17:52.586 --> 00:17:55.716 architecture team member to figure out what's going on
00:17:55.716 --> 00:17:59.416 instead of just like, go fix the problem and they spend 12 hours
00:17:59.416 --> 00:18:02.831 and not sure what's going on, right? So like we need to get
00:18:01.289 --> 00:18:01.789 Uh-huh.
00:18:02.831 --> 00:18:06.473 away from just a bucket of fix the problem. We kind of need two
00:18:06.473 --> 00:18:09.660 phases there for. Have we identified the problem and do
00:18:09.660 --> 00:18:12.904 you know of an easy resolution or do we need to bring in
00:18:12.904 --> 00:18:16.433 somebody who's maybe seen this kind of problem before or just
00:18:16.433 --> 00:18:19.449 another set of eyes to resolve and and again that's.
00:18:20.029 --> 00:18:23.605 Unfortunately, a judgment call that probably you as the PM
00:18:23.605 --> 00:18:27.423 needs to make and the developer needs to make. But you know we
00:18:27.423 --> 00:18:30.998 I'm sure that you guys are tired, you're not thrilled with
00:18:30.998 --> 00:18:34.513 having to give a 12 hour change request because of junior
00:18:34.513 --> 00:18:35.119 developer.
00:18:35.929 --> 00:18:38.252 Spent 12 hours looking at a problem that they should have
00:18:38.252 --> 00:18:40.736 gone to somebody else and said, you know, somebody else could
00:18:40.736 --> 00:18:43.059 been in 15 minutes like ohh yeah, they we just need to do
00:18:43.059 --> 00:18:43.219 XYZ.
00:18:44.729 --> 00:18:46.849 100% so.
00:18:46.139 --> 00:18:46.429 Yep.
00:18:48.509 --> 00:18:50.449 Quick question before we.
00:18:49.729 --> 00:18:50.009 Mm-hmm.
00:18:51.489 --> 00:18:57.039 Move on to the next bits in terms of like accessing this
00:18:57.039 --> 00:18:58.889 obviously with any.
00:18:59.979 --> 00:19:04.307 Project that is a integration project which I think for most
00:19:04.307 --> 00:19:08.634 of us on the call currently, I don't think there's any. Just
00:19:08.634 --> 00:19:08.989 Seth.
00:19:09.819 --> 00:19:13.843 With the exception of maybe Tom's UM, but for any project
00:19:13.843 --> 00:19:18.214 that is an integration project from the developer perspective,
00:19:18.214 --> 00:19:22.239 would it be useful if the PMS had access to this and were
00:19:22.239 --> 00:19:26.749 actually going and grabbing like the error stuff to put into the
00:19:26.749 --> 00:19:30.911 tickets when we're creating that? Or is that just adding an
00:19:30.911 --> 00:19:32.299 additional layer of?
00:19:33.439 --> 00:19:36.409 Extra steps that we don't really need to be taking.
00:19:38.099 --> 00:19:38.719 Umm.
00:19:39.759 --> 00:19:43.869 I would say that the majority of problems found will be found by
00:19:43.869 --> 00:19:47.726 like during the development process like as I'm building the
00:19:47.726 --> 00:19:51.584 integration and testing it, 50% of these are saying user not
00:19:49.559 --> 00:19:49.899 OK.
00:19:51.584 --> 00:19:55.567 found in CEF. Well that sounds like it's maybe on my side, but
00:19:55.567 --> 00:19:59.614 it's probably gonna sounds like it's probably on the side and I
00:19:59.614 --> 00:20:03.535 by my side. I mean connect as a connect developer, right? And
00:20:03.535 --> 00:20:07.392 CEF could be any system in this scenario. But let's say it's
00:20:05.009 --> 00:20:05.409 Umm.
00:20:07.392 --> 00:20:11.249 this OK, well, that means that the user is not found in CEF.
00:20:11.339 --> 00:20:15.445 So what's the problem? Is it that Seth isn't creating the
00:20:15.445 --> 00:20:15.799 user?
00:20:16.499 --> 00:20:20.340 Or is it that connect hasn't synced the user over from the
00:20:20.340 --> 00:20:24.571 ERP and now we need to maybe put in a you know a check that that
00:20:24.571 --> 00:20:28.738 exists and then go maybe go sync the user and between. You know
00:20:28.738 --> 00:20:29.779 there's kind of.
00:20:30.519 --> 00:20:33.502 A bunch of different ways to resolve these things and and I I
00:20:33.502 --> 00:20:36.389 hate to put that out there, but it really is kind of a, you
00:20:36.389 --> 00:20:36.629 know.
00:20:37.549 --> 00:20:40.936 Let's make the judgment call as as we go, but to your original
00:20:40.936 --> 00:20:43.838 question, a lot of these are going to be found during
00:20:43.838 --> 00:20:46.741 development, and this is where it just it's all about
00:20:46.741 --> 00:20:49.967 communication and developer needs to be noting that is that
00:20:49.967 --> 00:20:53.084 something that they have a problem with or is it a system
00:20:53.084 --> 00:20:56.202 issue or what is it then anything after that is typically
00:20:56.202 --> 00:20:59.266 going to be found in like the UAT process and so clients
00:20:59.266 --> 00:21:02.599 should be seeing them that hey, this one didn't sync over and
00:21:02.599 --> 00:21:03.459 I'm seeing that.
00:21:03.699 --> 00:21:07.384 You know, there's this. This has got a problem. Then we can. Then
00:21:07.384 --> 00:21:10.845 we can assess what the problem is from. There is kind of, you
00:21:10.845 --> 00:21:14.362 know, one off and start getting into the root of the issue. So
00:21:14.362 --> 00:21:17.767 you kind of attack it broad to start with at the development
00:21:17.767 --> 00:21:21.005 level is that it's most likely a connect problem like the
00:21:21.005 --> 00:21:24.187 integration problem early on. And then as you get moving
00:21:22.699 --> 00:21:23.139 Umm.
00:21:24.187 --> 00:21:27.648 forward, it's probably leaning more towards the data problem.
00:21:27.648 --> 00:21:31.109 If you've got a 99% success rate of syncing things over, it's
00:21:31.109 --> 00:21:34.403 probably more of like hey we're missing some things on the
00:21:34.403 --> 00:21:36.859 normalization side we just need to do some.
00:21:37.189 --> 00:21:40.409 Quick error handling, so I don't think it's, I don't think.
00:21:41.209 --> 00:21:44.729 That it would be a bad idea to just take a look at it once a
00:21:44.729 --> 00:21:48.306 Sprint if you've got, if you if you know that the the clients
00:21:48.306 --> 00:21:51.422 doing user user acceptance testing on a site and this
00:21:51.422 --> 00:21:54.884 integration is up and running just to peek in there and say
00:21:54.884 --> 00:21:57.019 hey guys, we've got 72,000 failures.
00:21:58.059 --> 00:22:00.798 Like what's going on? If you've got that mini not in a prod
00:22:00.798 --> 00:22:03.765 environment and not CMMC, which has a lot of integrations, well,
00:22:03.765 --> 00:22:06.549 not a lot of integrations, but they're doing a lot of things
00:22:06.549 --> 00:22:07.279 inside of there.
00:22:08.559 --> 00:22:12.379 Then you probably just got up there. There is a bug somewhere,
00:22:12.379 --> 00:22:16.260 but you know if it's like, hey, there's 10 failures because the
00:22:16.260 --> 00:22:20.020 user didn't do XYZ, then you can take those on a case by case
00:22:20.020 --> 00:22:23.900 basis. So I know that was kind of all over the place there. But
00:22:23.900 --> 00:22:26.629 I mean it's not quite as black and white as.
00:22:24.059 --> 00:22:25.369 Yeah, well.
00:22:26.949 --> 00:22:31.069 And I I sort of put you on the spot with that particular
00:22:30.369 --> 00:22:30.989 Yeah.
00:22:31.069 --> 00:22:33.309 question too, in general, what?
00:22:34.839 --> 00:22:39.967 And I I know you've all heard me talk about SEFA on the regular,
00:22:39.967 --> 00:22:44.542 but this was something that would come up with them very,
00:22:44.542 --> 00:22:48.880 very regularly because we actually had three different
00:22:48.880 --> 00:22:53.850 instances of connect throughout their development process. And
00:22:53.850 --> 00:22:58.898 so we were pulling things in and had QA setup one way stage set
00:22:58.898 --> 00:23:03.553 up the same as QA and then their pre prod environment that
00:23:03.553 --> 00:23:05.209 mimicked that and so.
00:23:05.429 --> 00:23:09.485 We were trying to eliminate any differences there and it was
00:23:09.485 --> 00:23:13.341 something that I checked regularly throughout the project
00:23:13.341 --> 00:23:17.529 life cycle. If I continued to see failed results over and over
00:23:17.529 --> 00:23:21.851 again in the same area, I could kind of direct the team of where
00:23:21.851 --> 00:23:23.579 to at least start looking.
00:23:25.149 --> 00:23:29.165 I'm no expert. There's no way that I'm gonna be able to very
00:23:29.165 --> 00:23:32.983 clearly disseminate exactly what's going on from a system
00:23:32.983 --> 00:23:37.196 exception or whatever. Failure message is there, but at least I
00:23:37.196 --> 00:23:40.619 can link them to the job details and be like, look.
00:23:41.719 --> 00:23:45.885 I'm seeing, you know, 25 of these On this date from this
00:23:45.885 --> 00:23:50.050 date range, and it's all the same exception, and this is
00:23:50.050 --> 00:23:54.143 something that we need to resolve. So it's just another
00:23:54.143 --> 00:23:58.308 area for us to kind of help create repro steps, which is
00:23:58.308 --> 00:24:02.913 something that I think as a PM team as a whole, we need to get
00:24:02.913 --> 00:24:06.859 better at and make sure that we are giving all of the
00:24:06.859 --> 00:24:11.609 information in terms of reproing something very specifically so.
00:24:12.389 --> 00:24:15.159 If you can't reproduce it, you can't fix it.
00:24:16.629 --> 00:24:20.352 And so the more information we can provide, just like we do or
00:24:20.352 --> 00:24:23.720 try to do with acceptance criteria, the better off we're
00:24:23.720 --> 00:24:27.147 gonna be. So if you have a project that is an integration
00:24:27.147 --> 00:24:30.870 project and you have not seen this screen before, reach out to
00:24:30.870 --> 00:24:34.179 your team, figure out what the URL is for their connect
00:24:34.179 --> 00:24:37.960 instance and go ahead and just monitor this once a Sprint. Just
00:24:37.960 --> 00:24:41.506 take a look, make sure that things seem like they're on the
00:24:41.506 --> 00:24:45.169 up and up. If you're noticing a pattern because we as PMS are
00:24:45.169 --> 00:24:46.469 trained inherently to.
00:24:46.919 --> 00:24:49.389 Detect patterns and be very detail oriented.
00:24:51.059 --> 00:24:52.689 If you see something, say something.
00:24:55.259 --> 00:24:58.427 Sorry to totally put you on the spot, Eric. I pop, quizzed you
00:24:57.689 --> 00:25:02.432 No, you're good. You're good. And and I do wanna on that note
00:24:58.427 --> 00:24:58.829 as well.
00:25:02.432 --> 00:25:07.252 real quick. So in and of course I have logged in, but there is
00:25:07.252 --> 00:25:12.072 now a login on C5, so you can't just get directly in here. Now
00:25:12.072 --> 00:25:16.509 the username and password are hard coded, not hard coded.
00:25:16.669 --> 00:25:20.212 They're they're set in the app settings just as kind of
00:25:20.212 --> 00:25:24.260 plaintext, but it is at least a a level of security rather than
00:25:24.260 --> 00:25:28.372 just like like CMMC prod. I can just go to, right? I didn't have
00:25:25.049 --> 00:25:25.809 Ah.
00:25:27.939 --> 00:25:28.429 Umm.
00:25:28.372 --> 00:25:32.295 to log into this site, which that's not great, but it is what
00:25:32.295 --> 00:25:35.837 it is. And Charlie, for your benefit, we could probably
00:25:35.837 --> 00:25:39.949 easily put the login on to this and might want to, but go ahead.
00:25:38.769 --> 00:25:43.479 It it's a publicly available security site that's perfect.
00:25:48.609 --> 00:25:49.919 I'll save that for later.
00:25:50.389 --> 00:25:51.299 Yeah, anyway.
00:25:52.499 --> 00:25:56.157 But but there is a login that pops up and so you'll just Clint
00:25:56.157 --> 00:25:59.409 just went through, went through this with his with the.
00:26:00.119 --> 00:26:04.068 Como developer this week? Or maybe it's the end of last week,
00:26:04.068 --> 00:26:08.016 but whenever they stand this up, just just ask them what that
00:26:08.016 --> 00:26:11.964 what that is and put it in the wiki like for example comos is
00:26:11.964 --> 00:26:14.639 in the wiki for clarity or connect login.
00:26:15.679 --> 00:26:17.649 So it does have a level of security now.
00:26:18.829 --> 00:26:22.543 Could these these environments are something that should also
00:26:22.543 --> 00:26:26.318 be in the wiki just as a call out. So if you don't see that in
00:26:24.859 --> 00:26:25.299 Yep.
00:26:26.318 --> 00:26:29.912 your project wiki, that is a perfect time to call it out to
00:26:29.912 --> 00:26:33.806 the developer. Figure out where that environment actually is and
00:26:33.806 --> 00:26:37.580 make sure that that information is updated so that anybody can
00:26:37.580 --> 00:26:38.179 go in and.
00:26:38.859 --> 00:26:39.869 Figure it out.
00:26:41.629 --> 00:26:45.125 And then one more thing I did wanna cover in here real quick.
00:26:45.125 --> 00:26:47.549 So there is a. Can you guys see this page?
00:26:48.789 --> 00:26:49.179 Yes.
00:26:49.379 --> 00:26:50.419 Just hang fire job filter.
00:26:50.919 --> 00:26:51.319 Yep.
00:26:51.719 --> 00:26:55.729 So this is a Chrome extension. I think it only exists on Chrome,
00:26:55.729 --> 00:26:58.629 but it adds this filtered by job name in here.
00:26:59.069 --> 00:26:59.859 No.
00:27:00.399 --> 00:27:04.944 Yeah. So the nice thing about this then is that, let's say, I
00:27:04.944 --> 00:27:09.635 was like, hey, you know, seem MC calls me up and says, hey, CCP
00:27:09.635 --> 00:27:14.326 231 isn't, it's not there. You can come in here and type in CCP
00:27:14.326 --> 00:27:14.619 231.
00:27:15.799 --> 00:27:19.929 And it it's not performant, but it will go find all the times
00:27:19.929 --> 00:27:24.259 that CCP 231 has synced and you can do it in failed as well. Now
00:27:24.259 --> 00:27:27.856 I don't think that the I'll check it. Yeah the filter
00:27:27.856 --> 00:27:28.389 doesn't.
00:27:29.029 --> 00:27:32.785 Transfer across them. This is a very kind of rudimentary search,
00:27:32.785 --> 00:27:36.078 but it will search in here. Now I and again I think that
00:27:36.078 --> 00:27:39.776 unfortunately I don't. If I put like Dash 231, I bet it doesn't
00:27:39.776 --> 00:27:42.549 work. So you'd have to know. Oh, it does. Nice.
00:27:43.369 --> 00:27:43.959 Well, that's cool.
00:27:45.179 --> 00:27:48.779 So you can you can get this filter here and I will give it
00:27:48.779 --> 00:27:50.549 to. I'll ping it to the chat.
00:27:51.359 --> 00:27:54.975 And that will allow you to search for these and and it kind
00:27:51.389 --> 00:27:52.049 Sweet.
00:27:54.975 --> 00:27:58.772 of goes back to the reason for this, the need for this is that
00:27:58.772 --> 00:28:02.267 the reason I said earlier of like if I have 100 customers
00:28:02.267 --> 00:28:05.883 that sync every hour, now I'm queuing 2400 jobs in an hour,
00:28:05.883 --> 00:28:09.740 scrolling through there to find the right one as a pane. So now
00:28:09.740 --> 00:28:13.477 I can just search for it and see OK, that's good. So the same
00:28:13.477 --> 00:28:16.309 thing on the failure side, I can say RPO 3121.
00:28:23.589 --> 00:28:24.079 Waiting.
00:28:27.479 --> 00:28:30.192 OK, well it's thinking, but it will do the same thing on this
00:28:30.192 --> 00:28:32.730 side and and we'll, we'll validate that it actually comes
00:28:32.730 --> 00:28:33.999 up here in a little bit, but.
00:28:35.119 --> 00:28:38.693 That way you can go through and you can see OK when the the last
00:28:38.693 --> 00:28:41.936 one. Why did it fail? And you can click in and see all the
00:28:41.936 --> 00:28:45.235 stuff so it does allow for that level of filtering, whereas
00:28:45.235 --> 00:28:46.389 before like with GLV.
00:28:47.639 --> 00:28:51.714 For example, or yeah, GLV for example, like if in these
00:28:51.714 --> 00:28:52.369 failures.
00:28:53.809 --> 00:28:56.554 I don't really know what was in. I'd have to come in here and
00:28:56.554 --> 00:28:59.077 see, you know, you you really have to kind of dive in to
00:28:59.077 --> 00:29:01.689 figure out what, what the problems were. Now these are all
00:29:01.689 --> 00:29:04.036 because this is the stage environment. These are all
00:29:04.036 --> 00:29:06.781 probably that either Seth was turned off or syspro was turned
00:29:06.781 --> 00:29:07.179 off. But.
00:29:08.759 --> 00:29:13.032 Yeah. So but yeah, that is that's a nice little nice little
00:29:13.032 --> 00:29:15.239 Chrome extension for filtering.
00:29:15.709 --> 00:29:17.079 Ah, that's amazing.
00:29:18.739 --> 00:29:23.762 One last question that tends to come up at least for me a lot is
00:29:23.762 --> 00:29:25.539 the scheduling of jobs.
00:29:27.299 --> 00:29:33.131 What is the sort of out of box expectation and general setup
00:29:33.131 --> 00:29:38.962 for scheduling and is there a way that the client can adjust
00:29:38.962 --> 00:29:39.249 it?
00:29:40.689 --> 00:29:41.459 So.
00:29:42.329 --> 00:29:44.939 I don't see it in here.
00:29:46.419 --> 00:29:50.308 But I know that Jeremy has showed me a way that we can
00:29:50.308 --> 00:29:54.410 modify this screen to update this like live. So right now
00:29:54.410 --> 00:29:58.865 these are app settings and so all you need to say all you need
00:29:58.865 --> 00:30:03.037 to do, but you, the developer would just go to the box and
00:30:03.037 --> 00:30:07.351 then go modify the app setting for the job turned the apples
00:30:07.351 --> 00:30:09.189 off and turn them back on.
00:30:13.199 --> 00:30:13.579 Umm.
00:30:33.989 --> 00:30:34.399 Mm-hmm.
00:30:34.459 --> 00:30:38.369 Because ideally you wouldn't want somebody coming in here and
00:30:38.369 --> 00:30:42.215 changing your Cron to so just so everybody knows what a Cron
00:30:42.215 --> 00:30:46.251 string is. This is just a time, a time run, so it's the minute,
00:30:46.251 --> 00:30:49.908 the hour, the day, the month and the year. And so this is
00:30:49.908 --> 00:30:53.691 scheduled to run at the at midnight on February 31st, which
00:30:53.691 --> 00:30:57.159 ultimately means that it will never run automatically.
00:30:58.559 --> 00:31:01.893 It's kind of a trick, a trick to tell it not to never run, so
00:30:58.899 --> 00:30:59.099 It.
00:31:01.893 --> 00:31:05.119 there's these only are run manually, which we typically do.
00:31:05.119 --> 00:31:08.022 The reason we do that is that you know, we don't want
00:31:08.022 --> 00:31:10.764 sometimes sometimes integrations, especially early
00:31:10.764 --> 00:31:14.044 on in development or even in UAT, we don't want them running
00:31:14.044 --> 00:31:17.324 regularly because they're not ready for that. They just want
00:31:17.324 --> 00:31:20.550 them to run. I wanna come in here and trigger them manually
00:31:20.550 --> 00:31:22.969 to do my testing. So like CMMC, for example.
00:31:24.369 --> 00:31:28.347 You know, this one is scheduled to run process manual CMMC data,
00:31:28.347 --> 00:31:31.529 but then this one is scheduled to run every minute.
00:31:32.359 --> 00:31:35.044 Uh, which that's actually unnecessary cause star just
00:31:35.044 --> 00:31:35.989 means every minute.
00:31:37.229 --> 00:31:40.999 But then this one scheduled to run every 5 minutes, this one
00:31:40.999 --> 00:31:44.831 scheduled to run at 8:00 o'clock on Monday and you kind of go
00:31:44.831 --> 00:31:46.809 from there. You get the picture.
00:31:47.559 --> 00:31:48.119 Awesome.
00:31:47.589 --> 00:31:50.679 There is a there is a Cron.
00:31:51.459 --> 00:31:55.712 Tab dot guru, I think that you can type in something here to
00:31:53.479 --> 00:31:54.009 Umm.
00:31:55.712 --> 00:32:00.104 see like OK, 1*** is at every minute and it will tell you. I
00:32:00.104 --> 00:32:04.357 don't think there's one that will like go backwards, but you
00:32:04.357 --> 00:32:08.471 can come in here and play with these to see kind of how it
00:32:08.471 --> 00:32:08.889 works.
00:32:10.909 --> 00:32:16.327 Very nice. Is there any inherent danger from a customer asking
00:32:16.327 --> 00:32:19.079 for all jobs to sync every hour?
00:32:24.169 --> 00:32:27.212 There's not a yes or no answer there. It depends on their
00:32:27.212 --> 00:32:27.579 volume.
00:32:28.299 --> 00:32:28.919 Umm.
00:32:30.829 --> 00:32:34.874 I would say you mean once an hour as opposed to once a day or
00:32:34.874 --> 00:32:37.809 once an hour. Once opposed to once a minute.
00:32:38.769 --> 00:32:39.299 Or yes.
00:32:40.299 --> 00:32:44.384 Yes, in general, that's a thing that I've had come up a couple
00:32:44.384 --> 00:32:48.275 of times of like can I just have everything sync over every
00:32:48.275 --> 00:32:48.729 minute?
00:32:49.599 --> 00:32:51.729 Yeah, that's absolutely doable.
00:32:51.809 --> 00:32:55.337 Uh, although you there is a little bit of strategic you know
00:32:55.337 --> 00:32:58.344 that when you know we, we we should probably have a
00:32:58.344 --> 00:33:01.987 discussion about that that if they want everything synced once
00:33:01.987 --> 00:33:05.573 a minute we need to we need to confirm that there's not syncs
00:33:05.573 --> 00:33:09.274 that should probably run after the another one like for example
00:33:09.274 --> 00:33:12.744 like a sales order sync maybe that one should run after the
00:33:12.744 --> 00:33:16.214 customer sync because what if the customer creates and they
00:33:16.214 --> 00:33:18.469 create a sales order I blah blah blah.
00:33:18.969 --> 00:33:19.269 Right.
00:33:19.759 --> 00:33:22.317 So those conversations, if the if the clients like I want
00:33:22.317 --> 00:33:25.139 everything to run once a minute, let's have a converse, a quick
00:33:25.139 --> 00:33:26.109 conversation about it.
00:33:27.199 --> 00:33:30.460 It's not the end of the world to run everything once a minute.
00:33:30.460 --> 00:33:33.670 Most likely. What that means is that the job is going to spin
00:33:33.670 --> 00:33:36.724 up, go ask for the, you know, the customers that have been
00:33:36.724 --> 00:33:39.985 updated since the last time it ran, which was a minute ago and
00:33:39.985 --> 00:33:43.090 in 75% of clients that don't have a massive, massive amount
00:33:43.090 --> 00:33:46.507 of volume, it's just going to be like, Yep, nothing to integrate,
00:33:46.507 --> 00:33:48.629 nothing to sync. We're good. Move along.
00:33:49.409 --> 00:33:52.339 And so the resource allocation is is fairly low.
00:33:50.009 --> 00:33:50.429 Awesome.
00:33:54.129 --> 00:33:58.051 You know in Hive in high volume scenarios, it's probably best to
00:33:58.051 --> 00:34:01.731 process everything at like the end of the day. Once you know
00:34:01.731 --> 00:34:05.110 once a day, but it kind of comes down to the individual
00:34:05.110 --> 00:34:08.790 integration like maybe sales orders need to run once an hour
00:34:08.790 --> 00:34:12.652 up until 5:00 PM and then maybe run once in the morning to kind
00:34:12.652 --> 00:34:16.453 of collect everything and then they can run once an hour again
00:34:16.453 --> 00:34:20.254 just so that if an order comes in that purchased for overnight
00:34:20.254 --> 00:34:24.176 shipping, we sync that over and fulfillment has time to ship it,
00:34:24.176 --> 00:34:24.779 but maybe.
00:34:25.129 --> 00:34:28.426 You know product datas that product data that probably isn't
00:34:28.426 --> 00:34:31.776 getting updated that much that could probably just run once a
00:34:31.776 --> 00:34:35.072 day to go get you know the the new description of somebody's
00:34:35.072 --> 00:34:38.099 going in and modifying description. So it is the answer
00:34:38.099 --> 00:34:41.449 is it depends on the client and their volume and their needs.
00:34:42.019 --> 00:34:44.059 Got it. Thank you, Charlie.
00:34:45.319 --> 00:34:51.949 I just find it like I can. I can hear client saying that, but I I
00:34:51.949 --> 00:34:56.269 think that the request has embedded in it.
00:34:57.619 --> 00:35:03.131 A lack of review on the client's part of what the actual business
00:35:00.609 --> 00:35:00.979 Mm-hmm.
00:35:03.131 --> 00:35:07.640 case is, it's hard to imagine a scenario where that's
00:35:07.640 --> 00:35:10.479 appropriate resource utilization.
00:35:10.879 --> 00:35:15.418 Uh, because a lot of data doesn't change every minute. It
00:35:15.418 --> 00:35:18.079 doesn't even change it every day.
00:35:19.159 --> 00:35:23.799 But there are other jobs. If if you kick off a job, that's gonna
00:35:23.799 --> 00:35:25.369 take 5 minutes to run.
00:35:26.159 --> 00:35:29.666 Then you get one minute into that job, you have 80% of the
00:35:29.666 --> 00:35:32.459 job remaining and you're kicking it off again.
00:35:33.559 --> 00:35:39.938 I just if somebody wants to have a flat across the board, let's
00:35:39.938 --> 00:35:45.819 just do this. There's probably a problem to uncover there.
00:35:46.109 --> 00:35:50.449 Yeah, for sure, but I I will caveat that with just a little
00:35:50.449 --> 00:35:54.356 bit so built into the way we build connect, we have a
00:35:54.356 --> 00:35:55.079 basically.
00:35:55.519 --> 00:36:00.481 I don't over overrun yourself attribute that if a job starts
00:36:00.481 --> 00:36:05.606 what it does initially is, it goes and looks is there another?
00:36:05.606 --> 00:36:10.162 Is there another job like me already running and I will
00:36:10.162 --> 00:36:15.042 abort. So like for example if process or Git Moodle updates
00:36:15.042 --> 00:36:15.449 runs.
00:36:16.309 --> 00:36:19.804 And it takes that this is set to run every minute if. If this
00:36:19.804 --> 00:36:23.411 takes 2 minutes to run the next minute when get Moodle updates,
00:36:23.411 --> 00:36:26.737 it will see that Git Moodle updates is already running and
00:36:26.737 --> 00:36:30.062 abort itself so that this one can finish and then the next
00:36:30.062 --> 00:36:33.670 minute it will check again and if this is still running it will
00:36:33.670 --> 00:36:36.939 abort itself until. OK I haven't. I don't see any running
00:36:36.939 --> 00:36:40.377 Git, Moodle updates. I'll go. I'll now go run since the last
00:36:40.377 --> 00:36:43.815 time that this one ran so it will get the last three minutes
00:36:43.815 --> 00:36:45.619 worth. And so that kind of that.
00:36:46.299 --> 00:36:49.461 That type of thing. So let's say for example Git Moodle updates
00:36:49.461 --> 00:36:52.573 is massive, kind of to Charlie's point, where, like let's say,
00:36:52.573 --> 00:36:55.438 we're just thinking sales orders, you probably don't need
00:36:55.438 --> 00:36:58.155 sales orders syncing once a minute. And if you do, you
00:36:58.155 --> 00:37:00.921 probably have some issues because if this job takes, if
00:37:00.921 --> 00:37:04.182 you have a sales order coming in once a minute and this job takes
00:37:04.182 --> 00:37:07.343 X amount of time to run, well, now it takes 5 minutes before it
00:37:07.343 --> 00:37:10.307 goes find the next and now it's gonna take 15 minutes. It's
00:37:10.307 --> 00:37:13.568 finding 5 minutes worth of sales orders. And so we need to either
00:37:13.568 --> 00:37:16.285 up the resources or we need to find a more performance
00:37:16.285 --> 00:37:16.729 solution.
00:37:16.949 --> 00:37:20.702 Most of those problems only occur on Super, super high
00:37:20.702 --> 00:37:25.206 volume clients, but there can be some tuning around around timing
00:37:25.206 --> 00:37:26.229 and whatnot so.
00:37:27.189 --> 00:37:30.039 I you know it is just kind of a let's have a conversation type
00:37:30.039 --> 00:37:32.708 thing. If somebody asks that. But to Charlie's point, he's
00:37:32.708 --> 00:37:35.557 100% right. If somebody comes in and says I need everything to
00:37:35.557 --> 00:37:38.362 run once a minute, you need to say, well, let's unpack that a
00:37:38.362 --> 00:37:38.859 little bit.
00:37:38.729 --> 00:37:39.299 Yep.
00:37:40.709 --> 00:37:42.679 Find out the reasons why.
00:37:44.639 --> 00:37:47.789 The the general motto of the PM. Why?
00:37:49.399 --> 00:37:52.309 Yeah. Or how, yeah.
00:37:51.249 --> 00:37:53.079 Yeah, exactly.
00:37:54.419 --> 00:37:58.849 Any other questions for Sir Weathers? Why we have him?
00:38:09.119 --> 00:38:11.569 All right. Ohh Amy's typing something.
00:38:13.199 --> 00:38:14.869 She's not unmuted, she's thinking.
00:38:13.439 --> 00:38:16.836 Thinking it's OK, I'm I'm hanging out. I'm hanging out
00:38:14.659 --> 00:38:15.859 So sorry, I was thinking.
00:38:16.319 --> 00:38:17.369 What's your favorite color?
00:38:16.836 --> 00:38:19.059 until the end of my favorite color.
00:38:19.219 --> 00:38:20.189 What's your favorite?
00:38:19.269 --> 00:38:19.519 Yeah.
00:38:20.999 --> 00:38:25.314 I I'm a I'm a blue guy. I like blue. Yeah, I know. I know. It
00:38:23.059 --> 00:38:25.289 Below classic.
00:38:25.314 --> 00:38:27.889 was when I was young, it was purple.
00:38:28.499 --> 00:38:33.112 I like purple. I'm here for purple. Umm, sign me up for
00:38:29.579 --> 00:38:31.489 I do like I do like a good purple.
00:38:33.112 --> 00:38:33.689 purple.
00:38:34.009 --> 00:38:37.943 But I find myself if I go look at my closet, there's a lot of
00:38:37.943 --> 00:38:39.719 blue in there, so it's it's.
00:38:38.169 --> 00:38:40.939 Loose. Easy. Yeah, but there's a lot of blue out there.
00:38:41.149 --> 00:38:42.819 Me telling, yeah, for sure.
00:38:42.739 --> 00:38:44.349 A little whole lot of blue out there.
00:38:44.669 --> 00:38:45.239 Yep, Yep.
00:38:47.109 --> 00:38:52.770 Awesome. Well, UM, I I feel like I've drained Eric Eric's brain
00:38:52.459 --> 00:38:55.757 I mean, I'm. I'm hanging out. I'm hanging out for the rest of
00:38:52.770 --> 00:38:53.389 enough.
00:38:55.757 --> 00:38:59.267 the PM training. So, Amy, if you get done thinking and you find a
00:38:59.267 --> 00:39:02.565 question, either feel free to ping it in here or just ask out
00:39:02.565 --> 00:39:03.469 loud. We're good.
00:39:04.039 --> 00:39:05.309 For sure. Thank you.
00:39:05.639 --> 00:39:05.879 Umm.
00:39:05.829 --> 00:39:10.635 All right. So the next part of this is to kind of dive into
00:39:10.635 --> 00:39:15.361 Seth a little bit and this hopefully will help us all kind
00:39:15.361 --> 00:39:20.247 of solidify jobs, run things, get synced over. That's how we
00:39:20.247 --> 00:39:21.689 get data into CEF.
00:39:22.519 --> 00:39:26.659 So we're gonna do a little bit of popcorn style pop quizzy type
00:39:26.659 --> 00:39:30.605 stuff, so hopefully everybody has clicked on the link that I
00:39:30.605 --> 00:39:34.681 put in the chat. Does anybody need credentials for the clarity
00:39:34.681 --> 00:39:35.069 admin?
00:39:40.299 --> 00:39:42.861 Trenton, can you tell me where to find the credentials for
00:39:42.861 --> 00:39:43.469 clarity admin?
00:39:46.099 --> 00:39:46.889 Uh.
00:39:48.339 --> 00:39:52.529 I gotta remember where to find them. They were auto saved on
00:39:52.529 --> 00:39:56.169 here. I think it's in the general teams in the wiki.
00:39:56.699 --> 00:39:58.039 Correct, yes.
00:39:57.669 --> 00:39:58.169 Yes.
00:39:59.169 --> 00:39:59.799 All right.
00:40:01.259 --> 00:40:06.782 I want everybody to be prepared to share your screen when you
00:40:06.782 --> 00:40:08.029 get called on.
00:40:08.749 --> 00:40:09.339 Uh.
00:40:10.149 --> 00:40:11.819 So first and foremost.
00:40:12.519 --> 00:40:14.179 We're going to dive into products.
00:40:14.799 --> 00:40:19.249 Uh, Charlie, picking on you, bud. And I think you know why.
00:40:19.249 --> 00:40:23.700 Can you tell me? Three major reasons why a product will not
00:40:23.700 --> 00:40:25.999 show in SAF in the store front.
00:40:28.649 --> 00:40:33.099 Three major reasons why a product will not show in CEF.
00:40:32.919 --> 00:40:33.609 Show me.
00:40:41.699 --> 00:40:42.029 There.
00:40:42.609 --> 00:40:47.774 So showing you would would cause undue delay to the meeting, but
00:40:43.479 --> 00:40:43.939 OK.
00:40:47.509 --> 00:40:48.289 Tell me where to go.
00:40:47.774 --> 00:40:48.409 I would.
00:40:49.529 --> 00:40:53.959 Umm, so I'd start with so you go to uh products.
00:40:55.289 --> 00:40:55.539 OK.
00:40:55.839 --> 00:40:56.379 View.
00:40:59.219 --> 00:41:03.126 Number one reason that I discussed with Trenton today
00:41:03.126 --> 00:41:07.685 because I discussed with you, I think 3 days ago is that index
00:41:07.685 --> 00:41:09.349 products button up top.
00:41:09.569 --> 00:41:09.919 Umm.
00:41:10.829 --> 00:41:15.262 We can create items, we can import items, we can do many
00:41:15.262 --> 00:41:19.772 things, but if we don't index then essentially elastic is
00:41:19.772 --> 00:41:24.827 unaware of it and so if you had the product URL you could hit it
00:41:24.827 --> 00:41:29.804 directly because it exists, but it does not exist in the search
00:41:29.804 --> 00:41:34.392 which is also what drives categories and essentially every
00:41:34.392 --> 00:41:38.747 other way that a client would use the site UI to find a
00:41:38.747 --> 00:41:39.369 product.
00:41:39.499 --> 00:41:44.582 So index products is a super simple like button click and see
00:41:44.582 --> 00:41:49.992 if it changes anything. The next thing that I would do is go over
00:41:49.992 --> 00:41:53.599 to the right and click on that ellipsis to.
00:41:54.259 --> 00:41:58.129 Open up the product edit menu on any particular product.
00:41:58.459 --> 00:42:01.049 You could just right click too if that saves you some time.
00:42:00.879 --> 00:42:02.439 Oh, that's so much better.
00:42:03.389 --> 00:42:07.149 God, that tiny little spot over there sucks.
00:42:04.969 --> 00:42:06.329 We're learning things, huh?
00:42:07.379 --> 00:42:07.909 Yeah.
00:42:08.899 --> 00:42:12.049 Are we recording this? I just said sucks on a recording.
00:42:12.149 --> 00:42:14.539 I think you'll be fine. Works has been said before.
00:42:15.169 --> 00:42:16.129 Dang it.
00:42:17.519 --> 00:42:23.257 So this screen and it really all of the uh, if you look at the
00:42:23.257 --> 00:42:28.449 NAV bar on the left any any section of that NAV bar that
00:42:28.449 --> 00:42:33.368 renders in red text has a problem with it which which
00:42:33.368 --> 00:42:38.924 could interfere with product display likewise within a given
00:42:38.924 --> 00:42:44.936 screen like when you've selected one of those items if there is a
00:42:44.936 --> 00:42:48.579 field in a red that field is a problem.
00:42:48.709 --> 00:42:53.136 You can import a fragmentary product record successfully and
00:42:53.136 --> 00:42:57.708 you will have loaded the data from the importer, but that does
00:42:57.708 --> 00:43:01.844 not guarantee like the the importer will accept the data
00:43:01.844 --> 00:43:06.053 and will write it to the database, but it does not ensure
00:43:06.053 --> 00:43:09.319 that that is a well formed record that will.
00:43:09.979 --> 00:43:13.929 That will display on the client site, UM the.
00:43:14.899 --> 00:43:21.328 I feel like the big areas that I've run into are missing SEO
00:43:21.328 --> 00:43:21.749 URL.
00:43:22.689 --> 00:43:27.286 And there are also versions of the importer floating around the
00:43:27.286 --> 00:43:31.523 company that I stub my toe on from time to time that don't
00:43:31.523 --> 00:43:35.617 successfully map to long description, and so you'll wind
00:43:35.617 --> 00:43:38.059 up with a blank long description.
00:43:38.519 --> 00:43:43.670 Umm. And so if you put valid data in either of those lots of
00:43:43.670 --> 00:43:46.709 times, that will resolve the issue.
00:43:47.339 --> 00:43:47.779 Nice.
00:43:48.499 --> 00:43:52.656 Can I? Can I follow? Can I real quick on that. So the longest,
00:43:48.519 --> 00:43:49.039 Good job.
00:43:51.259 --> 00:43:51.509 Umm.
00:43:52.656 --> 00:43:56.154 so he's 100% right on the importer that it will just
00:43:56.154 --> 00:43:59.981 import it and as long as there are are only technically a
00:43:59.981 --> 00:44:03.808 handful of required fields in the database that require a
00:44:03.808 --> 00:44:07.701 record to be made. However like what you when you when you
00:44:07.701 --> 00:44:11.858 remove short description there we have validation on the front
00:44:11.858 --> 00:44:15.818 end that short description is required and SEO well I guess
00:44:15.818 --> 00:44:18.589 the SEO URL isn't even required but then.
00:44:19.339 --> 00:44:23.618 But then there are a few fields that are required for the
00:44:23.618 --> 00:44:28.266 indexer and SEO URL is one of them is visible there is visible
00:44:28.266 --> 00:44:33.134 tag. That's another one. If that is is visible false, the indexer
00:44:33.134 --> 00:44:37.635 will not pick it up. However it still will be visible by SEO
00:44:37.635 --> 00:44:41.397 URL. So if you typed in our2022-4.claritydemos.com
00:44:41.397 --> 00:44:45.602 product seo URL equals vinyl mini dinosaurs then it will
00:44:45.602 --> 00:44:49.069 still be able to see the product details page.
00:44:49.259 --> 00:44:51.719 I just won't index and be viewable in the catalog.
00:44:53.279 --> 00:44:57.085 So there are there are technically only a couple, a
00:44:57.085 --> 00:45:01.549 couple checks for the indexer to pick a product up active is
00:45:01.549 --> 00:45:06.160 visible. I think SEO URL and I wanna say maybe product key but
00:45:06.160 --> 00:45:10.331 to to Charlie's point long description you can't come in
00:45:10.331 --> 00:45:14.576 here and save it. You have to add 1 short description you
00:45:14.576 --> 00:45:19.333 can't save you have to add one. I think pricing or purchasing or
00:45:19.333 --> 00:45:22.919 shipping one of those two you need that data to.
00:45:22.989 --> 00:45:26.504 Actually come in here and save it. And so that would be the
00:45:26.504 --> 00:45:30.254 that that would be the kind of the difference between saving it
00:45:30.254 --> 00:45:33.710 and then viewable in the in the store front because of the
00:45:33.710 --> 00:45:34.179 indexer.
00:45:35.309 --> 00:45:35.569 Huh.
00:45:36.849 --> 00:45:37.519 So.
00:45:39.029 --> 00:45:40.869 Who am I going to pick on next?
00:45:40.709 --> 00:45:42.874 Are you gonna ask the same question? Because I have one
00:45:42.874 --> 00:45:44.189 more to add to the same question.
00:45:44.519 --> 00:45:45.179 Yeah, go ahead.
00:45:44.839 --> 00:45:48.019 And what, sorry. Can you go back to the list?
00:45:50.649 --> 00:45:54.007 I would say the main reason that you can't find a product in the
00:45:54.007 --> 00:45:57.106 storefront is if you type in it's skew or its name, and you
00:45:57.106 --> 00:45:59.379 can't find it. That means it doesn't exist.
00:46:01.689 --> 00:46:05.089 So the the product integrate, you know the integration didn't
00:46:05.089 --> 00:46:08.434 bring it over or the importer didn't bring it in or whatever
00:46:08.434 --> 00:46:11.669 it is. So I would start there just can you find it in this
00:46:11.669 --> 00:46:14.959 list and then you can kind of go down the rest of the path?
00:46:15.539 --> 00:46:19.646 There's one more interesting reason of why we wouldn't be
00:46:19.646 --> 00:46:22.549 able to see a product in the storefront.
00:46:23.509 --> 00:46:26.751 Even if everything looks to be filled out correctly at a
00:46:26.751 --> 00:46:27.149 glance.
00:46:29.779 --> 00:46:30.259 With.
00:46:30.999 --> 00:46:32.129 A given product.
00:46:36.049 --> 00:46:38.952 Right I when I was doing my troubleshooting, I was like,
00:46:38.952 --> 00:46:42.262 what if it's not in the category and I changed the categories to
00:46:42.262 --> 00:46:45.267 test that and broke what the client wanted. So even once I
00:46:45.267 --> 00:46:48.526 got it to show up, it showed up wrong because I messed with the
00:46:48.526 --> 00:46:50.869 categories. But you do wanna have a category.
00:46:51.249 --> 00:46:54.659 Yes, you have to exactly.
00:46:51.989 --> 00:46:53.509 You do need to have a category.
00:46:56.079 --> 00:47:00.802 Products well the the category mega menu. No, I'm gonna save
00:47:00.802 --> 00:47:01.189 that.
00:47:02.629 --> 00:47:07.219 Ha ha. Ohm. Who am I gonna pick on Mickey?
00:47:10.239 --> 00:47:11.049 Yes, ma'am.
00:47:10.379 --> 00:47:12.769 Show me. Show me what you got.
00:47:13.719 --> 00:47:15.469 We're going to go to the storefront for you.
00:47:17.929 --> 00:47:19.859 OK, so not here.
00:47:21.249 --> 00:47:27.559 You click on the store front link to the very right of the.
00:47:26.839 --> 00:47:28.849 You know. Ohh, there we go. Sorry.
00:47:28.659 --> 00:47:29.569 Yeah.
00:47:33.659 --> 00:47:36.809 And I would like for you to pull down the product Mega menu.
00:47:37.879 --> 00:47:38.449 Yes, ma'am.
00:47:39.659 --> 00:47:44.066 And kind of filter through that guy. Like Scroll down and see if
00:47:44.066 --> 00:47:45.829 we have any subcategories.
00:47:49.419 --> 00:47:50.449 Automotive lighting.
00:47:49.639 --> 00:47:50.109 Alright.
00:47:51.639 --> 00:47:56.879 OK, so if we have a product that is just under automotive?
00:47:59.269 --> 00:48:02.799 But it's supposed to be under automotive lighting.
00:48:06.849 --> 00:48:08.959 Will it show on the store front at all?
00:48:17.139 --> 00:48:20.287 Ooh yes it should. I mean, if you Click to see all under
00:48:20.287 --> 00:48:23.490 automotive, you should see anything under automotive, not
00:48:21.909 --> 00:48:22.399 Mm-hmm.
00:48:23.490 --> 00:48:26.804 just what's under automotive lighting. So I would say, yes,
00:48:26.804 --> 00:48:29.289 yes, you should see that at the store front.
00:48:27.639 --> 00:48:28.199 Good job.
00:48:29.889 --> 00:48:31.379 Hi if.
00:48:32.209 --> 00:48:33.279 A product.
00:48:34.599 --> 00:48:39.114 Or if a category does not have products, will it display in the
00:48:39.114 --> 00:48:39.819 Mega menu?
00:48:44.589 --> 00:48:45.249 Yes.
00:48:46.139 --> 00:48:46.789 Yes it will.
00:48:48.759 --> 00:48:49.399 Are you sure?
00:48:50.019 --> 00:48:53.269 No, I I'm thinking about Rydell and.
00:48:55.079 --> 00:48:58.755 No, I I'm changing my answer because David told me that it
00:48:58.755 --> 00:48:59.689 would collapse.
00:49:00.439 --> 00:49:04.215 If you didn't have products in the thing, so no, it will not
00:49:00.459 --> 00:49:00.899 Uh-huh.
00:49:04.215 --> 00:49:07.496 show the subcategory if there are no products in the
00:49:07.496 --> 00:49:08.239 subcategory.
00:49:08.919 --> 00:49:11.679 So the mega menu is data-driven.
00:49:12.779 --> 00:49:17.735 If a category exists in CEF admin, but it does not have any
00:49:17.735 --> 00:49:23.105 children or products associated to it, it's not going to display
00:49:23.105 --> 00:49:24.509 in the Mega menu.
00:49:26.289 --> 00:49:26.879 So.
00:49:28.209 --> 00:49:32.204 Can anyone? Well, no, actually, Mickey, let's go back to the
00:49:32.204 --> 00:49:35.740 sense you're sharing your screen. We'll just continue
00:49:35.740 --> 00:49:39.079 picking on you. Can you go back to the Seth Admin?
00:49:36.759 --> 00:49:37.149 OK.
00:49:41.939 --> 00:49:42.289 No.
00:49:44.009 --> 00:49:45.579 I'm sure it can if I.
00:49:46.959 --> 00:49:48.609 Had some sort of level of intelligence.
00:49:47.229 --> 00:49:47.529 Ship.
00:49:51.559 --> 00:49:52.949 And let's go to categories.
00:49:51.909 --> 00:49:52.379 There we go.
00:49:53.739 --> 00:49:54.419 Okie dokie.
00:49:58.609 --> 00:50:04.279 And can you show me how you would associate?
00:50:05.159 --> 00:50:08.339 Electronics to automotive.
00:50:11.169 --> 00:50:11.839 OK.
00:50:21.729 --> 00:50:22.229 Nice.
00:50:23.689 --> 00:50:24.239 Good job.
00:50:25.439 --> 00:50:26.109 So.
00:50:28.039 --> 00:50:32.353 Outside of going through this particular view, what is the
00:50:32.353 --> 00:50:35.789 fastest way to kind of see your category tree?
00:50:45.429 --> 00:50:46.689 I don't know the answer to that.
00:50:47.179 --> 00:50:48.419 OK, no worries.
00:50:49.639 --> 00:50:52.436 So one of the things that tends to happen from the client side,
00:50:52.436 --> 00:50:55.059 and this is something that I've run across in a lot of this
00:50:55.059 --> 00:50:57.069 stuff, trainings that I've done is they they.
00:50:57.869 --> 00:50:59.169 If you have.
00:51:00.719 --> 00:51:04.160 45 different categories and you're trying to kind of
00:51:04.160 --> 00:51:05.199 streamline them?
00:51:06.769 --> 00:51:10.739 It can get very confusing to look at.
00:51:11.729 --> 00:51:15.807 The list view and kind of see where everything is at and so
00:51:15.807 --> 00:51:19.545 and then you're trying to associate products to it and
00:51:19.545 --> 00:51:23.963 it's this whole hot mess. And so one of the simplest things that
00:51:23.963 --> 00:51:28.245 I typically tell clients when I'm kind of training them on how
00:51:28.245 --> 00:51:32.459 to deal with their categories is to think from the bottom up.
00:51:33.659 --> 00:51:38.779 And so I typically will ask them to go to the products tab.
00:51:40.999 --> 00:51:43.229 And use the export.
00:51:45.179 --> 00:51:49.670 And let me see if I can come up with an example. I wanna say it
00:51:49.670 --> 00:51:54.232 was CCS, Cotter, Cotter church. We had synced over a whole bunch
00:51:54.232 --> 00:51:58.442 of their products, but they didn't actually have categories
00:51:58.442 --> 00:52:02.863 associated in their database at the moment. And so they had to
00:52:02.863 --> 00:52:05.319 create the categories, but it was.
00:52:06.299 --> 00:52:10.384 They they have something like I wanna say 75 different
00:52:10.384 --> 00:52:15.136 categories that summer parents I think they have 25 parents and
00:52:15.136 --> 00:52:19.369 then the rest of them are all children or some children.
00:52:20.319 --> 00:52:23.798 And so they're having a hard time kind of creating that. And
00:52:23.798 --> 00:52:27.219 So what I asked them to do was actually go to the products.
00:52:28.079 --> 00:52:34.063 Tab within Seth and export their products and then using that
00:52:34.063 --> 00:52:34.739 export.
00:52:35.839 --> 00:52:40.751 We can't use that export as an import for a product importer,
00:52:40.751 --> 00:52:45.267 but we can grab all of the needed fields and use the the
00:52:45.267 --> 00:52:50.100 import template and just kind of move the data over and from
00:52:50.100 --> 00:52:54.695 there they could fill out in the categories section there
00:52:54.695 --> 00:52:59.290 specific product categories using comma delimited data so
00:52:59.290 --> 00:53:00.399 they could do.
00:53:01.569 --> 00:53:05.321 Uh candles for everyday church use and then candles and
00:53:05.321 --> 00:53:09.608 lighting, and then candle Wicks or whatever. However they do it
00:53:09.608 --> 00:53:13.159 so they have these three different categories, so it
00:53:13.159 --> 00:53:17.580 would be the top one. So you set your parent 1st and then you put
00:53:17.580 --> 00:53:20.729 a comma. You set your child comma subcategory.
00:53:22.789 --> 00:53:25.709 And then using that you can import.
00:53:26.509 --> 00:53:29.787 The spreadsheet that you've just created and that will actually
00:53:29.787 --> 00:53:33.014 create the categories and staff and associate the products for
00:53:33.014 --> 00:53:33.219 you.
00:53:34.179 --> 00:53:37.398 Rather than going in and manually adjusting every
00:53:37.398 --> 00:53:40.875 category to create this tree, does that make sense to
00:53:40.875 --> 00:53:41.519 everybody?
00:53:47.939 --> 00:53:48.619 Umm.
00:53:49.669 --> 00:53:51.099 One call out to that.
00:53:52.649 --> 00:53:57.312 If you have a category that has commas in its title, you're
00:53:57.312 --> 00:53:59.099 gonna have some issues.
00:54:00.619 --> 00:54:04.137 So with that particular client, we ended up having to adjust the
00:54:04.137 --> 00:54:07.600 importer so that it would pick up and start to separate out the
00:54:07.600 --> 00:54:10.685 categories based on a semi colon. So we had to make some
00:54:10.685 --> 00:54:13.608 adjustments for them specifically. So that's just one
00:54:13.608 --> 00:54:17.017 of the things that you're going to want to make sure that your
00:54:17.017 --> 00:54:20.210 clients are aware of when they're doing naming conventions
00:54:20.210 --> 00:54:23.349 for their product categories to display in the Mega menu.
00:54:27.719 --> 00:54:33.218 Let me see. Is there anything else crazy with categories? Ohh
00:54:33.218 --> 00:54:34.459 yeah, can you?
00:54:37.009 --> 00:54:38.769 Go to the content tab.
00:54:42.159 --> 00:54:45.659 And tell me where you think this would display on the storefront.
00:54:50.219 --> 00:54:54.903 I would imagine that this would display on the category landing
00:54:54.903 --> 00:54:55.269 page.
00:54:55.729 --> 00:54:56.289 Correct.
00:54:57.839 --> 00:55:01.029 Is the category landing page turned on out of box?
00:55:02.379 --> 00:55:03.069 No.
00:55:03.729 --> 00:55:04.399 Or act.
00:55:06.979 --> 00:55:10.915 What about the images? Is that gonna display for categories if
00:55:10.915 --> 00:55:13.289 I don't have landing pages turned on?
00:55:14.529 --> 00:55:14.959 Who?
00:55:16.119 --> 00:55:20.509 Umm, I'm gonna go with. No, I don't think so. Was it?
00:55:21.819 --> 00:55:24.249 Available in the mega menu.
00:55:26.129 --> 00:55:29.678 So if you want to do a new tab with the storefront, so if you
00:55:29.678 --> 00:55:33.169 just right click the store front link and open in a new tab.
00:55:35.909 --> 00:55:39.589 It does have an image, yes. So yes, the image would go there.
00:55:43.859 --> 00:55:47.286 But only child images like that's a child category. So like
00:55:47.286 --> 00:55:50.655 automotive without category landing pages doesn't have any
00:55:48.479 --> 00:55:48.859 Mm-hmm.
00:55:50.655 --> 00:55:53.739 images like automotive is just the top of the parent.
00:55:55.299 --> 00:55:57.149 But the automotive lighting would have one.
00:55:55.439 --> 00:55:58.209 So only only, only automotive lighting it.
00:56:01.979 --> 00:56:04.483 Stephanie, do you wanna show an example of the category landing
00:56:04.483 --> 00:56:06.870 page turned on and I can show you where to go for that? Or I
00:56:06.870 --> 00:56:08.239 can tell you where to go for that.
00:56:08.969 --> 00:56:13.639 Ah, who do I have? Category landing pages turned on.
00:56:12.699 --> 00:56:16.039 I I got one. I got one in court is cause we built out a new core
00:56:16.039 --> 00:56:17.169 category landing page.
00:56:18.419 --> 00:56:23.092 If you go to go, go to your new tab there and go to B to
00:56:23.092 --> 00:56:24.649 b.claritydemos.com.
00:56:31.039 --> 00:56:32.569 So this is Ronnie demo site.
00:56:34.649 --> 00:56:36.419 And if you go to products?
00:56:37.559 --> 00:56:39.189 Well, he may not have.
00:56:41.309 --> 00:56:44.329 Let's try it. Go to. I think it's.
00:56:45.639 --> 00:56:46.779 Electronics.
00:56:49.689 --> 00:56:52.049 And just click on electronics. See what see what we get.
00:56:56.779 --> 00:57:00.652 So we've added a if category landing pages are on, there's
00:57:00.652 --> 00:57:04.721 kind of two different steps. There is a category landing page
00:57:04.721 --> 00:57:08.790 and then there is a category catalog with sub Carousel. So if
00:57:08.790 --> 00:57:12.794 the category landing pages are on but you haven't determined
00:57:12.794 --> 00:57:16.732 the level of category landing page, you get the catalog and
00:57:16.732 --> 00:57:20.474 then this carousel on top that shows all of the like the
00:57:20.474 --> 00:57:24.149 subcategories for the category that you've selected on.
00:57:26.289 --> 00:57:28.999 And then if you Scroll down you can see there on the left side
00:57:28.999 --> 00:57:30.719 of the image of the McLaren headphones.
00:57:32.599 --> 00:57:34.709 So that is the sidebar content.
00:57:36.139 --> 00:57:40.239 And then if you go to, I think go up, go scroll up.
00:57:40.989 --> 00:57:43.829 And then click on the audio subcategory.
00:57:46.649 --> 00:57:52.122 So there's your description. So this is the description content
00:57:52.122 --> 00:57:54.089 for the audio category.
00:57:55.359 --> 00:57:58.289 And then Scroll down. Is there a footer comes in on this one too?
00:57:59.769 --> 00:58:01.289 OK, then go scroll up.
00:58:02.869 --> 00:58:05.339 If you go to the the Mega menu drop down.
00:58:07.449 --> 00:58:09.631 And I think he put it in military. If you go to the
00:58:09.631 --> 00:58:10.009 military.
00:58:11.749 --> 00:58:15.139 Yep. So if you Scroll down.
00:58:16.829 --> 00:58:17.389 Uh-huh.
00:58:17.219 --> 00:58:18.799 So there's the footer content.
00:58:22.049 --> 00:58:25.539 And so we'll have to get, we'll have to put some some
00:58:25.539 --> 00:58:27.219 documentation together on.
00:58:28.399 --> 00:58:31.947 On how how you get to these different category landing pages
00:58:31.947 --> 00:58:35.320 and mega menus, but when turned on you can do these these
00:58:35.320 --> 00:58:39.158 headers and sidebars and footers and whatnot and then you can set
00:58:39.158 --> 00:58:42.590 the level for which you get a landing page rather than the
00:58:42.590 --> 00:58:46.079 catalog. So right now we just have it that all category all
00:58:46.079 --> 00:58:49.452 levels get the catalog with the sub carousel, but you can
00:58:49.452 --> 00:58:52.942 technically change it so that the top level category gets a
00:58:52.942 --> 00:58:54.919 landing page without the catalog.
00:58:55.749 --> 00:58:57.049 Umm, it's just not here yet.
00:58:57.849 --> 00:59:02.838 So just to clarify that, so if it's the top level category has
00:59:02.838 --> 00:59:07.432 a landing page instead of showing products, it would show
00:59:07.432 --> 00:59:07.669 us.
00:59:08.429 --> 00:59:08.899 Uh.
00:59:09.609 --> 00:59:13.089 The sub categories and images associated to the.
00:59:13.799 --> 00:59:18.177 Subcategories and then the sub category landing page would show
00:59:18.177 --> 00:59:22.281 the tertiary and then it would get to the catalog like that
00:59:22.281 --> 00:59:23.649 level of drill down.
00:59:23.779 --> 00:59:28.266 It would it depend? Yeah. So if you go back to go to the admin,
00:59:28.266 --> 00:59:30.509 go back to your R2022 for admin.
00:59:32.169 --> 00:59:34.169 And then go to site maintenance and settings.
00:59:39.809 --> 00:59:40.319 Where is it?
00:59:40.399 --> 00:59:44.919 So in send settings.
00:59:46.549 --> 00:59:48.639 Uh, sorry. Yeah. On the left side, click settings.
00:59:46.709 --> 00:59:47.089 On the.
00:59:48.359 --> 00:59:49.309 Oh yeah.
00:59:49.779 --> 00:59:53.073 Yeah, you're good. Does everyone know this screen? Because we
00:59:53.073 --> 00:59:56.367 asked this actually in Dev the dev training last week and not
00:59:56.367 --> 00:59:59.661 everyone did. Has everyone. And sorry, Stephanie, I'm kind of
00:59:59.661 --> 01:00:01.149 hijacking here a little bit.
00:59:59.739 --> 01:00:05.449 No, you go for it. You, you, you do you, you're the CTO.
01:00:04.269 --> 01:00:04.679 OK.
01:00:05.749 --> 01:00:09.845 Sure. So has everyone. Has everyone seen this screen before
01:00:06.649 --> 01:00:07.779 I can't tell you not to.
01:00:09.845 --> 01:00:11.279 or know what this is?
01:00:11.919 --> 01:00:14.129 I don't think I have.
01:00:13.299 --> 01:00:13.709 No.
01:00:14.429 --> 01:00:18.784 OK, so the old way and and I will this is this is one of the
01:00:18.784 --> 01:00:23.067 coolest things I to me that we've done in the past year for
01:00:23.067 --> 01:00:27.565 the CEF product is in order to change app settings. Previously
01:00:27.565 --> 01:00:32.277 we used to have to go to the box that the site was on, change the
01:00:32.277 --> 01:00:36.489 app setting and in some cases rebuild or at the very least
01:00:36.489 --> 01:00:40.772 turn the app pulls off and turn it back on. Kind of what we
01:00:40.772 --> 01:00:43.199 talked about earlier with Kinect.
01:00:44.069 --> 01:00:45.579 With this.
01:00:46.249 --> 01:00:49.367 Umm, we have a hot reload in place so now it's not the
01:00:49.367 --> 01:00:52.825 cleanest UI and you do need to know kind of the key for what
01:00:52.825 --> 01:00:56.339 you're looking for. But all the app settings there are only a
01:00:56.339 --> 01:00:59.967 handful that you wouldn't want to do in here. You can look for,
01:00:59.967 --> 01:01:03.481 change the value and it will update live including turning on
01:01:03.481 --> 01:01:07.166 and off providers. So let's for say for example the mock payment
01:01:07.166 --> 01:01:10.454 providers turned on and you want to turn on and enter the
01:01:10.454 --> 01:01:13.515 credentials for like authorize.net. You could come in
01:01:13.515 --> 01:01:16.519 here and type in in that filter there. Now you have.
01:01:16.589 --> 01:01:20.200 So I will say that again, this is not fully built, it's just
01:01:20.200 --> 01:01:23.338 exists. If you type in the filter it is it will auto
01:01:23.338 --> 01:01:27.067 search, you don't click enter. So you have to be kind of quick
01:01:27.067 --> 01:01:30.738 with it cuz it gives you like a half second of like after you
01:01:30.738 --> 01:01:34.526 press the last button it will go search. So it's again it's not
01:01:34.526 --> 01:01:38.019 great, but if you type in enabled provider or enabled Pro.
01:01:42.219 --> 01:01:45.396 So you see here this. These are the list of the enabled
01:01:45.396 --> 01:01:48.573 providers for for that are currently turned on for this
01:01:48.573 --> 01:01:50.729 site. So if you click enable editing.
01:01:54.369 --> 01:01:57.906 You could theoretically come in here and remove UPS and only
01:01:57.906 --> 01:02:01.560 show FedEx and so you know when you get to the when you get to
01:02:01.560 --> 01:02:04.865 the shipping step in in checkout, it would only find the
01:02:04.865 --> 01:02:08.518 FedEx shipping rates instead of UPS. So you do need to kind of
01:02:08.518 --> 01:02:11.939 know the provider that you're turning on like for example.
01:02:14.369 --> 01:02:17.399 If there's no payment provider specifically in here, it uses
01:02:17.399 --> 01:02:20.430 the mock payment provider, so you would need to know to type
01:02:20.430 --> 01:02:23.311 in authorized net payment provider or whatever the actual
01:02:23.311 --> 01:02:26.441 class name is in the code. But this would allow you to come in
01:02:26.441 --> 01:02:29.521 here and turn it on. So let's say we're turning on authorized
01:02:29.521 --> 01:02:32.501 net. So instead of enabled pro in your app settings, search
01:02:32.501 --> 01:02:35.680 type in authorized, I think it's just authorized authorized for
01:02:35.680 --> 01:02:35.879 now.
01:02:38.749 --> 01:02:41.916 So here you can see the logins. So or not the logins but the
01:02:41.916 --> 01:02:45.083 actual credentials and you can come in here and modify these
01:02:45.083 --> 01:02:48.146 and see if they take take effect. So for example if you're
01:02:48.146 --> 01:02:51.157 in the middle of a call with a client and payments aren't
01:02:51.157 --> 01:02:54.064 working for whatever you could come in here, find these
01:02:54.064 --> 01:02:55.829 credentials and come modify them.
01:02:56.549 --> 01:02:59.143 Directly on the call hit save and when it saves it will
01:02:59.143 --> 01:03:02.014 automatically reload so you can go right back to the front to
01:03:02.014 --> 01:03:03.959 the front end of the site and test again.
01:03:06.219 --> 01:03:07.209 That's so fun.
01:03:08.109 --> 01:03:08.539 If the.
01:03:11.379 --> 01:03:14.314 But it works for any app setting, so as long as you know
01:03:14.314 --> 01:03:17.455 what you're doing and this is the point that we came in here
01:03:17.455 --> 01:03:20.750 for, if you type in, don't type in the full word category, type
01:03:20.750 --> 01:03:22.809 in like category. Just like with the R.
01:03:25.399 --> 01:03:28.673 OK, so you have to find it in here, but if you look about
01:03:28.673 --> 01:03:31.269 three 2/3 of the way down the page, there is.
01:03:32.089 --> 01:03:35.571 Uh clarity dot featureset dot category landing pages dot
01:03:35.571 --> 01:03:36.059 enabled.
01:03:38.419 --> 01:03:42.541 And then cat Clarity dot catalog dot or no, I'm sorry the one
01:03:42.541 --> 01:03:45.998 right above it clarity dot catalog dot show product
01:03:45.998 --> 01:03:50.187 categories for levels up to X. So right now for develop or for
01:03:50.187 --> 01:03:54.243 our 2022.4 category landing pages are off. So you would have
01:03:54.243 --> 01:03:58.631 to turn that on and then you see the one above it is a number. So
01:03:58.631 --> 01:04:00.359 the number corresponds to.
01:04:00.979 --> 01:04:04.547 The the category level that would get a landing page versus
01:04:04.547 --> 01:04:08.234 the catalog. So if you wanted the top level category to get a
01:04:08.234 --> 01:04:11.802 landing page instead of the catalog, you would put a number
01:04:11.802 --> 01:04:15.192 one in there and it would display the landing page which
01:04:15.192 --> 01:04:18.641 would display what Stephanie said. These subcategories in
01:04:18.641 --> 01:04:22.447 that where the catalog is, you have the images and all that, it
01:04:22.447 --> 01:04:26.134 would just display cards where the subcategories and then all
01:04:26.134 --> 01:04:29.940 the extra content around it and then everything else after that
01:04:29.940 --> 01:04:32.973 would get the subcategory carousel and the product
01:04:32.973 --> 01:04:33.449 catalog.
01:04:35.109 --> 01:04:35.569 Ah.
01:04:36.269 --> 01:04:38.079 Ah, it's so cool.
01:04:38.599 --> 01:04:42.521 So so we have on the we have on the on the road map to discuss
01:04:42.521 --> 01:04:46.380 that you can set, you can set the whether or not the category
01:04:46.380 --> 01:04:49.804 gets a landing page versus subcategory carousel at the
01:04:49.804 --> 01:04:53.290 category level. So you could turn certain categories on
01:04:53.290 --> 01:04:57.149 versus like for example let's say you had a top level product
01:04:57.149 --> 01:05:01.009 that has like 5 level depths of subcategories. You could turn
01:05:01.009 --> 01:05:04.682 that one and maybe 2 Childs underneath it to get a landing
01:05:04.682 --> 01:05:08.417 page versus the catalog. But let's say you had one that was
01:05:08.417 --> 01:05:09.039 just like.
01:05:09.969 --> 01:05:13.186 It was just that category you could turn that one off to to
01:05:13.186 --> 01:05:16.509 show the catalog and so that's that's in that's in the works.
01:05:16.509 --> 01:05:18.439 But for now it's just at the level.
01:05:19.829 --> 01:05:24.899 Oh, that's awesome. So fun. So stinking exciting.
01:05:28.629 --> 01:05:31.379 Who am I going to pick on next?
01:05:31.669 --> 01:05:32.919 Can I? But in real quick?
01:05:33.209 --> 01:05:34.169 No. Yes.
01:05:33.769 --> 01:05:34.199 Umm.
01:05:35.179 --> 01:05:40.017 Eric, is there a ballpark? I suspect this would be highly
01:05:40.017 --> 01:05:44.855 variable, but is there a ballpark time frame for how long
01:05:44.855 --> 01:05:49.859 it takes to convert something into an app setting for core?
01:05:50.789 --> 01:05:53.779 Because at 20 hours of work 10:50.
01:05:55.159 --> 01:05:56.649 What do you mean by that? Sorry.
01:05:58.609 --> 01:06:00.589 To like get it to display here.
01:05:58.679 --> 01:05:59.779 To create a new one.
01:06:02.859 --> 01:06:06.680 Yeah, like to create a new, a new control and and map it
01:06:06.680 --> 01:06:07.819 through to there.
01:06:08.509 --> 01:06:11.768 So if I'm gonna repeat back what I think, what I think I'm
01:06:11.768 --> 01:06:15.137 hearing. So for example, let's say we have this feature that
01:06:15.137 --> 01:06:18.561 exists. Let's say it's category landing pages and what you're
01:06:18.561 --> 01:06:21.985 saying is how long would it take to create an app setting and
01:06:21.985 --> 01:06:25.409 wrap the category landing page feature in that app setting so
01:06:25.409 --> 01:06:29.054 that you can turn it on and turn it off. And assuming we have the
01:06:29.054 --> 01:06:30.269 feature already built.
01:06:31.349 --> 01:06:31.919 Correct.
01:06:32.329 --> 01:06:32.829 Yeah.
01:06:34.309 --> 01:06:38.206 It depends on the reach of the feature, like something like
01:06:38.206 --> 01:06:42.362 category landing pages probably is like a medium level in terms
01:06:42.362 --> 01:06:46.129 of just creating the app set, creating an app setting is.
01:06:46.979 --> 01:06:49.009 It should be a 10 to 15 minute.
01:06:49.879 --> 01:06:54.555 Task maximum the implementation of wrapping the thing. If it's
01:06:50.139 --> 01:06:50.359 Hmm.
01:06:51.969 --> 01:06:52.319 OK.
01:06:54.555 --> 01:06:58.563 just like an area. So for example like, let's say the
01:06:58.563 --> 01:07:03.239 shipping step or let's say we create a new payment provider or
01:07:03.239 --> 01:07:06.579 a new payment method and it's called pay by.
01:07:06.939 --> 01:07:11.350 Uh, Bitcoin, right? And so we pay, we create the Bitcoin
01:07:10.539 --> 01:07:11.409 Gift card.
01:07:11.350 --> 01:07:13.129 thing, whatever, right?
01:07:14.389 --> 01:07:18.413 The the method of creating the app, setting and then wrapping
01:07:18.413 --> 01:07:22.178 that that visibility of that component in the app setting
01:07:22.178 --> 01:07:26.332 like that's a 20 minute task to create the app setting and wrap
01:07:26.332 --> 01:07:30.226 it because it's one spot in checkout that you just say hide
01:07:30.226 --> 01:07:31.719 if not whatever, right?
01:07:32.919 --> 01:07:37.577 However, if you have like like a shipping to be able to to modify
01:07:37.577 --> 01:07:42.095 your shipping address, there's a couple places that happens and
01:07:42.095 --> 01:07:43.859 so the implementation is.
01:07:44.479 --> 01:07:47.958 You know 10 minutes times the number of places that it exists,
01:07:47.958 --> 01:07:49.339 so it's not a heavy lift.
01:07:50.559 --> 01:07:56.078 But it is variable depending on how intricate and how, how well,
01:07:56.078 --> 01:07:59.049 how segregated the the feature is.
01:07:59.849 --> 01:08:00.519 Cool. Thanks.
01:08:00.419 --> 01:08:04.434 I was just about to ask. I was actually just about to ask, is
01:08:04.434 --> 01:08:08.642 there any kind of difference in or if you can even create an app
01:08:08.642 --> 01:08:12.009 setting if it has like dependencies or other things
01:08:12.009 --> 01:08:15.959 that have to be done like it's not just as simple on or off.
01:08:15.959 --> 01:08:18.419 I'm thinking like price rules versus.
01:08:18.099 --> 01:08:19.659 Hmm. Yeah, that's great question.
01:08:19.089 --> 01:08:22.659 Uh price points or inventory for multi warehouse versus single
01:08:20.629 --> 01:08:20.989 Yeah.
01:08:22.659 --> 01:08:25.832 warehouse things that are mutually exclusive and things
01:08:25.832 --> 01:08:26.399 like that?
01:08:26.899 --> 01:08:29.712 Yeah, so dependency wise, so if you click micki, if you'll click
01:08:29.712 --> 01:08:32.351 on the one that's like show product categories for levels up
01:08:32.351 --> 01:08:33.649 to X like click on that title.
01:08:35.619 --> 01:08:36.199 Yeah, that one.
01:08:37.479 --> 01:08:41.142 So you see there it says depends on clarity dot featureset dot
01:08:41.142 --> 01:08:44.804 categories dot enabled. So when you go in there and this is an
01:08:44.804 --> 01:08:46.199 interesting one because.
01:08:47.319 --> 01:08:48.919 And I thought this as well but.
01:08:49.539 --> 01:08:52.239 There was there was there was. When we first kind of rolled
01:08:52.239 --> 01:08:54.894 this out, somebody saying, well hey, it's not working this
01:08:54.894 --> 01:08:57.369 specific app setting isn't working. I can't update it.
01:08:58.069 --> 01:09:01.517 Well, the problem is that if an app setting is dependent on
01:09:01.517 --> 01:09:05.194 another one, it doesn't matter what you set it to in the UI, it
01:09:05.194 --> 01:09:08.411 will show it as default. And unfortunately right now it
01:09:08.411 --> 01:09:11.744 doesn't say hey, this one depends on another one which is
01:09:11.744 --> 01:09:14.789 false. So you have to go turn that one on 1st again.
01:09:15.689 --> 01:09:18.760 We're we're it's a work in progress, but if you click on
01:09:18.760 --> 01:09:21.992 that it will show you if it depends on and then there are a
01:09:21.992 --> 01:09:25.063 couple that are mutually exclusive. But I don't know one
01:09:25.063 --> 01:09:28.349 off the top of my head. So we can't find it but it will tell
01:09:28.349 --> 01:09:30.719 you any dependencies or anything like that.
01:09:32.109 --> 01:09:35.578 Price rules versus price points would be mutually exclusive,
01:09:35.578 --> 01:09:35.919 right?
01:09:37.529 --> 01:09:41.161 Yes, but those are providers and while they do have an enabled
01:09:41.161 --> 01:09:44.851 like, they both have an enabled. I don't know if they're set as
01:09:41.179 --> 01:09:41.529 OK.
01:09:44.851 --> 01:09:48.137 mutually exclusive because you would just in the enabled
01:09:48.137 --> 01:09:51.770 providers the one that Mickey first looked at enabled like the
01:09:51.770 --> 01:09:55.402 enabled Pro. You would just put tiered pricing provider or you
01:09:55.402 --> 01:09:59.034 would put price rules pricing provider. You wouldn't put both.
01:09:59.034 --> 01:10:02.493 I don't know if there's good exception handling on the back
01:10:02.493 --> 01:10:06.241 end to like hey, you've got two of them on it might just be like
01:10:06.241 --> 01:10:09.469 whichever one is first in the list is the one it picks.
01:10:10.819 --> 01:10:13.842 I'll have to check in on that, but yeah, it it it, there are
01:10:13.842 --> 01:10:16.666 mutually exclusive things in there. I just don't know. I
01:10:16.666 --> 01:10:19.837 can't give you one on top of my head, not too many. There's not
01:10:19.199 --> 01:10:19.599 OK.
01:10:19.837 --> 01:10:20.679 too many of them.
01:10:20.829 --> 01:10:24.861 And that's probably and that's probably a bad example. I I just
01:10:24.861 --> 01:10:28.703 said it earlier, but we would probably just use price points
01:10:28.703 --> 01:10:32.861 because price points can be used as like a price list, a price, a
01:10:32.861 --> 01:10:36.956 price rule or multi tiered. So I think that was kind of unfair I
01:10:36.956 --> 01:10:40.924 or am I wrong Eric, I feel like price points have been kind of
01:10:40.924 --> 01:10:41.239 like.
01:10:41.909 --> 01:10:44.139 Forgotten about because price points?
01:10:45.099 --> 01:10:47.149 Praise rules have been kind of forgotten about.
01:10:45.429 --> 01:10:45.889 Yeah.
01:10:47.789 --> 01:10:51.119 It depends. It it definitely depends on the the logic and
01:10:51.119 --> 01:10:54.793 that's something that will kind of cover in architecture. But I
01:10:54.629 --> 01:10:56.199 I would love to know that, yeah.
01:10:54.793 --> 01:10:58.524 would say that 80 more than 80% I would, I would guess that more
01:10:58.524 --> 01:11:02.026 than 80 or 90 even 90% of people that come to us with custom
01:11:02.026 --> 01:11:04.839 pricing probably are going to get tired pricing.
01:11:05.769 --> 01:11:09.519 Ohh can I bring this full circle and ask a connect question?
01:11:06.299 --> 01:11:06.759 Gotcha.
01:11:10.049 --> 01:11:10.419 Sure.
01:11:11.319 --> 01:11:15.129 So with price rules or price points.
01:11:16.809 --> 01:11:21.062 Either one is that something that if they already have tiered
01:11:21.062 --> 01:11:24.835 pricing set up in their ERP system that we can build a
01:11:24.835 --> 01:11:28.951 customization for, to pull all of that into the pricing and
01:11:28.951 --> 01:11:30.529 stuff and have it just.
01:11:32.099 --> 01:11:36.454 Kind of work, or would we still need to go in and set up the
01:11:36.454 --> 01:11:39.309 individual price rules or price points?
01:11:39.929 --> 01:11:43.965 Yeah. I'm so it kind of depends on what the the. Yeah, that's my
01:11:43.965 --> 01:11:47.939 answer today a lot is, I don't know, it kind of depends, right.
01:11:48.339 --> 01:11:48.649 Mm-hmm.
01:11:48.799 --> 01:11:53.031 I would say that if done correctly, you should not have
01:11:53.031 --> 01:11:57.490 to do that. You know the the integration could make that I
01:11:57.490 --> 01:12:00.589 would say potentially you could look at.
01:12:00.909 --> 01:12:04.271 You know, let's say for example like like geov and I know I've
01:12:04.271 --> 01:12:07.474 been using Dev a lot in this. You know in this meeting, but
01:12:07.474 --> 01:12:10.889 they have different levels that different accounts are assigned
01:12:10.889 --> 01:12:14.305 to. And so for example they have level 102 hundred, 305 hundred
01:12:14.305 --> 01:12:17.454 and so theoretically you could go in beforehand and create
01:12:17.454 --> 01:12:20.709 those price points, which is those levels and then you would
01:12:20.709 --> 01:12:24.018 just assign those products to those price points if they come
01:12:24.018 --> 01:12:27.434 to us and say yeah, but I create different price points all the
01:12:27.434 --> 01:12:30.582 time, then we could modify the integration to create those
01:12:30.582 --> 01:12:33.785 price points if it doesn't. So like for example let's say a
01:12:33.785 --> 01:12:35.599 product comes in and it's a sign.
01:12:35.669 --> 01:12:39.246 You know it has a pricing that's assigned to level 600, which
01:12:39.246 --> 01:12:43.053 doesn't previously exist. We can modify the integration to create
01:12:43.053 --> 01:12:46.630 the price point level 600 and assign that product to it. So I
01:12:46.630 --> 01:12:50.207 mean connect can ultimately like it is an automation software
01:12:50.207 --> 01:12:54.014 first and foremost and so it can ultimately do whatever we can do
01:12:54.014 --> 01:12:57.129 manually in Seth. We just need to tell it to do that.
01:12:57.549 --> 01:12:58.599 Gotcha. OK.
01:12:59.319 --> 01:13:03.813 Umm, since we're still on the settings and one of the things
01:13:03.813 --> 01:13:08.602 that recently came up for myself as well as Trenton was actually
01:13:08.602 --> 01:13:12.875 setting up price rules for aquas, so I'm not seeing it as
01:13:12.875 --> 01:13:17.443 enabled in this it can I go in or since Mickey's driving have
01:13:17.443 --> 01:13:21.716 her go in and enable that, and then we could walk through
01:13:21.716 --> 01:13:23.779 setting up price rules as a.
01:13:24.469 --> 01:13:26.089 As a pick on Trenton kind of moment.
01:13:27.329 --> 01:13:31.266 Yeah, we can. I'm skin. Yeah. It if you type in, just type in
01:13:29.249 --> 01:13:29.579 Cool.
01:13:31.266 --> 01:13:34.885 price, route price rule probably. Probably don't want to
01:13:34.885 --> 01:13:37.869 type in the full the full pluralization of it.
01:13:39.929 --> 01:13:40.379 Brick.
01:13:43.789 --> 01:13:47.485 Feature set price rules enabled. OK yeah, so set that bad boy to
01:13:47.485 --> 01:13:47.769 true.
01:13:51.899 --> 01:13:52.179 Poop.
01:13:53.649 --> 01:13:56.963 And then this is where this you can click save. Yep. And then
01:13:56.963 --> 01:13:58.459 this is where the secondary.
01:14:00.339 --> 01:14:04.089 Peace comes in. It is the you'll need to go type in that enabled
01:14:04.089 --> 01:14:07.089 provider again like enabled Pro probably will work.
01:14:08.229 --> 01:14:12.024 Get type enabled because enabled there's a bunch of feet. There's
01:14:12.024 --> 01:14:15.762 a bunch of app settings that end with the OR it enabled enabled.
01:14:15.762 --> 01:14:17.199 Sorry with ad on the end.
01:14:20.029 --> 01:14:20.399 There you go.
01:14:20.899 --> 01:14:24.649 Uh, and then add a new one. Ohh well I guess.
01:14:26.709 --> 01:14:32.295 Remove the tiered pricing, fall back provider and then add a I'm
01:14:32.295 --> 01:14:34.099 going to look up the.
01:14:35.049 --> 01:14:39.524 I think it is price rules like Capital P, Capital R, price
01:14:39.524 --> 01:14:39.979 rules.
01:14:42.609 --> 01:14:44.309 Pricing capital P.
01:14:46.109 --> 01:14:47.459 Provider capital P.
01:14:51.409 --> 01:14:54.920 Bonus points if anyone tells me what that casing and naming
01:14:54.920 --> 01:14:55.739 convention is.
01:14:59.819 --> 01:15:00.849 Charlie, I'm looking at you.
01:15:03.329 --> 01:15:06.824 Sorry, I was I was deeply in EP, but I think we're saying
01:15:06.824 --> 01:15:10.259 capitals at the start of every word. That's proper case.
01:15:08.719 --> 01:15:08.959 Yep.
01:15:12.919 --> 01:15:15.252 I heard it got something called really something really weird.
01:15:15.252 --> 01:15:17.474 The other day I think was like Camel case or something like
01:15:17.229 --> 01:15:17.889 Hmm.
01:15:17.474 --> 01:15:17.659 that.
01:15:18.399 --> 01:15:19.209 Isn't that what it is?
01:15:18.439 --> 01:15:21.529 That ones not, that's not Camel case, but.
01:15:18.569 --> 01:15:18.879 Yep.
01:15:19.749 --> 01:15:22.149 It's what's camel case then.
01:15:21.539 --> 01:15:21.939 That was.
01:15:23.159 --> 01:15:23.689 Does anybody know?
01:15:23.599 --> 01:15:24.329 A problem?
01:15:26.769 --> 01:15:30.324 I'm just stuck on how I'm stuck on how Kyle works here and says
01:15:26.999 --> 01:15:27.749 Camel case.
01:15:30.324 --> 01:15:33.712 I heard that something called really weird the other day. It
01:15:33.569 --> 01:15:34.029 Umm.
01:15:33.712 --> 01:15:36.489 was funny. Sorry, sorry Kyle, I couldn't help it.
01:15:36.439 --> 01:15:40.201 I love that Camel case. If you think of like a camel, it's
01:15:40.201 --> 01:15:42.369 starts low in the front and then.
01:15:41.859 --> 01:15:43.009 Oh, got it.
01:15:43.239 --> 01:15:46.247 Camel in the middle so it would be the first word would be
01:15:44.549 --> 01:15:44.909 Uh.
01:15:46.247 --> 01:15:49.459 lowercase, so it would be like price. The P would be lowercase
01:15:49.459 --> 01:15:52.467 and then every the start of every word after that would be
01:15:52.467 --> 01:15:53.079 capitalized.
01:15:53.639 --> 01:15:57.473 Got it. So with this in particular, we have this all
01:15:54.379 --> 01:15:54.849 Interesting.
01:15:55.509 --> 01:15:56.039 The.
01:15:57.473 --> 01:16:02.103 kind of set up the same way. So if we're turning this over to a
01:16:02.103 --> 01:16:06.299 customer to use and we're asking them to kind of do that.
01:16:06.399 --> 01:16:09.949 And I'm assuming in our.
01:16:10.649 --> 01:16:14.320 Documentation we would have the the names of the different
01:16:14.320 --> 01:16:17.929 providers and the different settings and stuff that we're
01:16:17.929 --> 01:16:21.725 gonna need to give them for values so that they can actually
01:16:21.725 --> 01:16:23.529 manipulate this on their own.
01:16:25.259 --> 01:16:27.919 Yeah, I would contend that.
01:16:29.359 --> 01:16:32.149 It while they do have access to this.
01:16:33.469 --> 01:16:36.243 Unless they know what they're doing, they probably shouldn't
01:16:36.243 --> 01:16:38.880 touch this. This would be something we would kind of come
01:16:38.880 --> 01:16:41.835 in and mess with, like we could show them, you know, here's your
01:16:41.835 --> 01:16:44.654 authorized.net. This is how you go in and you know, let's say
01:16:44.654 --> 01:16:47.428 for example, they they change their password or whatever, it
01:16:47.428 --> 01:16:49.519 doesn't work. They could come in and do that.
01:16:50.159 --> 01:16:50.479 OK.
01:16:50.349 --> 01:16:53.845 I would say turning feature sets on and off probably is not a
01:16:53.845 --> 01:16:54.409 good idea.
01:16:55.729 --> 01:16:59.316 And you know, I'm talking a lot about not pipe dreams, but
01:16:59.316 --> 01:17:03.328 product road map stuff here. Our goal is to build a admin version
01:17:03.328 --> 01:17:07.219 in React and we would actually build kind of like what you have
01:17:07.219 --> 01:17:10.319 in WooCommerce with the settings. So where they're
01:17:10.319 --> 01:17:13.845 properly segregated and that's a nice UI for like payment
01:17:13.845 --> 01:17:17.614 provider and you turn on the payment writer and then only the
01:17:17.614 --> 01:17:21.019 settings for that payment provider are display below it
01:17:21.019 --> 01:17:24.119 rather than having to go search for it. Right. So.
01:17:25.079 --> 01:17:29.919 That's that's a road map goal, so for now I would say.
01:17:27.749 --> 01:17:28.099 OK.
01:17:30.869 --> 01:17:33.824 Unless unless we spend some time training them on what they're
01:17:33.824 --> 01:17:36.498 trying to do, just have them explain to you what they're
01:17:36.498 --> 01:17:37.999 trying to do. And then we do it.
01:17:38.569 --> 01:17:42.680 Got it. Got it. Yeah. I'm just thinking in terms of updating my
01:17:42.680 --> 01:17:46.920 CEF training with this as I have not yet included any of it and I
01:17:46.920 --> 01:17:47.819 don't want to.
01:17:47.239 --> 01:17:51.246 Yeah, yeah, I I wouldn't. I would. Only if they ask for it
01:17:51.246 --> 01:17:55.457 like, hey, can I come in here and do this? And yeah, you can.
01:17:55.457 --> 01:17:55.729 But.
01:17:55.929 --> 01:18:02.595 But it's still going to be a risk, so treat this the same way
01:17:56.459 --> 01:17:58.149 It's not on us if you break it.
01:17:59.789 --> 01:18:00.579 Yeah.
01:18:02.595 --> 01:18:08.617 I treat the section for statuses, types and states. Got
01:18:08.609 --> 01:18:12.798 Yeah, I don't. Nobody should really be touching those anyway,
01:18:08.617 --> 01:18:08.939 it.
01:18:12.179 --> 01:18:12.669 Got it.
01:18:12.798 --> 01:18:13.879 in the admin UI.
01:18:14.289 --> 01:18:19.081 Correct. OK. So let's go ahead and save that so I can pick on
01:18:19.081 --> 01:18:19.699 Trenton.
01:18:21.949 --> 01:18:22.869 Yay my turn.
01:18:23.309 --> 01:18:29.091 OK, so theoretically, do we need to refresh or do anything clear
01:18:29.091 --> 01:18:31.759 caches before that is enabled?
01:18:37.059 --> 01:18:37.739 Uh.
01:18:39.489 --> 01:18:41.519 That was a question for Eric, actually.
01:18:41.189 --> 01:18:42.799 OK, I was about to say.
01:18:41.649 --> 01:18:44.775 I'm sorry. Say you did say Trenton, and so I tuned out for
01:18:44.775 --> 01:18:47.159 a second. I was sending him this. Go for it.
01:18:44.909 --> 01:18:49.960 I know you turned out my bad. Do we need to clear caches or do
01:18:49.960 --> 01:18:53.969 anything else before price rules are now enabled?
01:18:55.179 --> 01:18:58.679 It wouldn't be a bad idea to go to UM.
01:18:59.559 --> 01:19:01.519 If you go to other tasks.
01:18:59.819 --> 01:19:00.849 Site maintenance.
01:19:01.829 --> 01:19:02.229 Umm.
01:19:05.099 --> 01:19:08.072 And there at the bottom, and this is an. This is a cool one.
01:19:08.072 --> 01:19:11.094 If you guys don't know this one that and the the translations
01:19:11.094 --> 01:19:13.239 need to be updated. But this cache counter.
01:19:13.899 --> 01:19:19.423 So there unfortunately there are multiple different ways that
01:19:19.423 --> 01:19:24.680 data can be cached. We can either cache it and read it, so
01:19:24.680 --> 01:19:25.749 for example.
01:19:25.829 --> 01:19:29.744 You know, uh, get by ID to to save performance the first time
01:19:29.744 --> 01:19:33.659 it runs, it calls up from the database. But if that same call
01:19:33.659 --> 01:19:37.637 is called again before the Redis cache times out, then it will
01:19:37.637 --> 01:19:41.551 store it and it will just go grab it from there and it's much
01:19:41.551 --> 01:19:45.024 faster. The second one is elastic search. Obviously we
01:19:45.024 --> 01:19:48.370 technically are caching all of the product data into
01:19:48.370 --> 01:19:51.906 Elasticsearch and then the last big one is actually not
01:19:51.906 --> 01:19:55.379 something we do but browser caching. Chrome is really.
01:19:56.339 --> 01:20:00.023 Good or bad at it, depending on your perspective of what you're
01:20:00.023 --> 01:20:03.650 trying to do. It's really good at caching things, but that can
01:20:03.650 --> 01:20:06.988 be bad if you're in like a development environment or you
01:20:06.988 --> 01:20:10.672 know, think you need things to change, right? So what this does
01:20:10.672 --> 01:20:14.299 is similar to what DNN does. The way we bust the browser cache
01:20:14.299 --> 01:20:14.759 and DNN.
01:20:15.509 --> 01:20:19.576 Is that at the end of every git call? So for example, you know
01:20:19.576 --> 01:20:23.319 get by ID, get a page, get styling, get things like that.
01:20:24.779 --> 01:20:29.108 At the end of those, at the end of those URLs, we put a like
01:20:29.108 --> 01:20:33.011 question equals this cache counter so you can see here
01:20:33.011 --> 01:20:37.339 current cache counter one. If you can highlight that Mickey.
01:20:37.949 --> 01:20:40.159 Right above the button the line just above the button.
01:20:41.609 --> 01:20:44.817 Yeah. So there at the end, so that would that translation
01:20:44.817 --> 01:20:48.191 should say current cash counter basically equals one. And So
01:20:48.191 --> 01:20:51.786 what what would do now if you go if you went to the to the front
01:20:51.786 --> 01:20:55.049 end site and you looked in the inspect window, you'd see a
01:20:55.049 --> 01:20:58.312 bunch of like question equals ones or equals ones or under
01:20:58.312 --> 01:21:01.797 score equals something like that on the front end. And So what
01:21:01.797 --> 01:21:04.949 that does is it's the browser sees that. So whenever you
01:21:04.949 --> 01:21:08.323 reload the page, if the browser URL is exactly the same, the
01:21:08.323 --> 01:21:11.199 browser is caching that page and caching that data.
01:21:11.559 --> 01:21:14.228 And it will just basically say, Yep, here you go. I'm not even
01:21:14.228 --> 01:21:17.023 going to make a call to the back end because for performance I've
01:21:17.023 --> 01:21:19.649 already cached that page. Here's the page that you asked for.
01:21:20.899 --> 01:21:23.535 What this does is if you increment that cache counter,
01:21:23.535 --> 01:21:24.349 press the button.
01:21:25.619 --> 01:21:25.889 Micki.
01:21:27.779 --> 01:21:28.639 Beautiful.
01:21:27.929 --> 01:21:31.367 So now it's two. So what happens is that the front end will go
01:21:31.367 --> 01:21:34.805 and read that cache counter and at the end of every single one
01:21:34.805 --> 01:21:38.243 of those git calls, it will say under score equals two or one.
01:21:38.243 --> 01:21:41.244 Again, question equals to whatever it is, and then the
01:21:41.244 --> 01:21:44.191 browser will see that as physically at different URL,
01:21:44.191 --> 01:21:47.629 even though you're asking for the same data, it has that extra
01:21:47.629 --> 01:21:50.958 equals 2 instead of equals one. And it's saying I don't have
01:21:50.958 --> 01:21:54.341 this page in my cache. I'm gonna go ahead and get it from the
01:21:54.341 --> 01:21:57.779 back end. And so typically what you would wanna do is kind of.
01:21:57.839 --> 01:22:01.490 In multiple places is if you've made updates to the site to via
01:22:01.490 --> 01:22:04.399 the back end, whether it's data or whatever it is.
01:22:05.029 --> 01:22:08.434 Kind of a general. Let's clear everything is come and increment
01:22:08.434 --> 01:22:11.573 the counter. This can be done infinite number of times. It
01:22:11.573 --> 01:22:14.712 doesn't matter, it's just a number that gets thrown on the
01:22:14.712 --> 01:22:17.957 end of the URL and then the other one is. If you go to clear
01:22:17.957 --> 01:22:18.329 caches.
01:22:21.739 --> 01:22:23.579 Uh, sorry. On the top, the top left.
01:22:25.569 --> 01:22:26.209 Yep, there you go.
01:22:25.819 --> 01:22:28.869 So Eric, that's essentially the nuke everything button that we
01:22:28.869 --> 01:22:30.369 were talking about for so long.
01:22:30.429 --> 01:22:35.787 It's similar, but it only it, but it only it only busts the
01:22:32.349 --> 01:22:33.059 Essentially.
01:22:35.787 --> 01:22:38.109 browser cache, not Reedus.
01:22:38.179 --> 01:22:39.459 Ah, gotcha. OK.
01:22:39.019 --> 01:22:42.489 Because on on the back end, we still we we ignore that extra
01:22:42.489 --> 01:22:45.845 piece and we just take in the the regular data. So this is
01:22:45.845 --> 01:22:49.257 what you're talking about Kyle. And we don't have that nuke
01:22:49.257 --> 01:22:52.897 everything button right now, but this is how you bust the Redis
01:22:52.897 --> 01:22:56.594 cache. And so for example I was talking about earlier get by ID.
01:22:56.594 --> 01:23:00.235 So let's say we're talking about Git product by ID. If you'd go
01:23:00.235 --> 01:23:02.339 change the description of a product.
01:23:03.979 --> 01:23:07.165 And you're not seeing that update on the product details
01:23:07.165 --> 01:23:10.799 page. If you go to products, the product section here and I will
01:23:10.799 --> 01:23:14.376 admit that I do this as well. I just go click every button, but
01:23:14.376 --> 01:23:17.953 theoretically you should just be able to click the products one
01:23:14.929 --> 01:23:15.369 Uh-huh.
01:23:15.199 --> 01:23:16.349 Yeah, yeah.
01:23:17.953 --> 01:23:19.239 the third button there.
01:23:20.739 --> 01:23:24.448 What that will do is that will go into Redis and it will clear
01:23:24.448 --> 01:23:28.216 everything that you know all of the Redis cache calls that have
01:23:28.216 --> 01:23:31.984 the products schema or table in there, and what that will do is
01:23:31.984 --> 01:23:35.517 clear it out. So the next time it requests it, Seth will go
01:23:35.517 --> 01:23:38.990 look and see has this key for this URL and this query been
01:23:38.990 --> 01:23:42.758 requested before? No, it hasn't. I'm gonna go get it. I'm gonna
01:23:42.758 --> 01:23:46.291 go get it from the database, which is a slower call, but it
01:23:46.291 --> 01:23:49.529 goes and gets everything from the database. Does that.
01:23:49.659 --> 01:23:52.705 Anybody have any questions on the difference between Redis
01:23:52.705 --> 01:23:54.099 cache versus browser cache?
01:23:58.409 --> 01:23:58.759 Cool.
01:23:58.649 --> 01:23:59.539 I don't believe you.
01:24:00.139 --> 01:24:04.128 OK, but what I would tell you is until you kind of see a pattern
01:24:00.399 --> 01:24:00.839 Yeah.
01:24:04.128 --> 01:24:07.932 between which ones are which it's, it would be, it's not that
01:24:07.932 --> 01:24:11.492 extra that much extra to go to other tasks clear to cache
01:24:11.492 --> 01:24:15.358 counter and then come in here and just if you updated products
01:24:15.358 --> 01:24:19.101 and you're not seeing product data update, just go click the
01:24:19.101 --> 01:24:22.967 buttons and you're done in 30 seconds and then go hard refresh
01:24:22.967 --> 01:24:23.519 the page.
01:24:29.449 --> 01:24:29.799 Hey.
01:24:31.249 --> 01:24:32.559 Let's pick on.
01:24:33.299 --> 01:24:33.849 Trenton.
01:24:35.939 --> 01:24:36.679 My turn.
01:24:35.999 --> 01:24:40.209 You are up. You are up. Drive. Show me what you got.
01:24:41.439 --> 01:24:46.209 I would like for you to set up a price rule on.
01:24:47.189 --> 01:24:48.199 A product.
01:24:49.249 --> 01:24:50.439 Probably the dinosaur.
01:24:51.559 --> 01:24:53.029 The Vinyl mini dinosaur.
01:24:53.319 --> 01:24:54.299 He needs a price rule.
01:24:56.339 --> 01:24:57.229 OK.
01:25:01.239 --> 01:25:02.789 Me. Remember how to do this.
01:25:03.859 --> 01:25:08.007 Yeah. So this is where I said in the hard doing, the hard
01:25:08.007 --> 01:25:10.009 refresh. So if you hit F-12?
01:25:13.139 --> 01:25:15.789 And then right click and Yep, them to cash Hardy load. Cool.
01:25:16.959 --> 01:25:17.749 Now go to pricing.
01:25:19.659 --> 01:25:22.289 Uh, did you save that price? Rose pricing provider Mickey?
01:25:23.219 --> 01:25:26.659 The chance when you change the setting.
01:25:30.979 --> 01:25:33.629 Sorry, I lost. Maybe you button. Yes I did click save.
01:25:34.429 --> 01:25:36.559 So it's now enabled in the top.
01:25:37.319 --> 01:25:41.239 So in the in the drop down, if you go to the top level.
01:25:42.189 --> 01:25:45.309 So it it wasn't there before.
01:25:45.949 --> 01:25:48.379 So let's go into price rules under accounts.
01:25:48.039 --> 01:25:48.349 Back.
01:25:49.339 --> 01:25:50.129 There it is. Yep.
01:25:50.859 --> 01:25:51.669 Well, that's the.
01:25:51.909 --> 01:25:55.265 Yeah. The only thing that shows up under the pricing tab of the
01:25:55.265 --> 01:25:58.620 product editor is price points. Price rules are set up a little
01:25:56.729 --> 01:25:57.259 That's right.
01:25:58.620 --> 01:25:59.459 bit differently.
01:25:59.269 --> 01:26:00.389 Ah, OK.
01:26:00.099 --> 01:26:01.279 Good talk, good cough.
01:26:02.999 --> 01:26:04.369 OK, well I do have.
01:26:05.359 --> 01:26:07.986 Yep, that's fine. This is what we're looking for. No, this is
01:26:06.059 --> 01:26:08.069 Another project open OK.
01:26:07.986 --> 01:26:09.299 this is what we're looking for.
01:26:09.699 --> 01:26:13.719 That's fine. So go ahead and let's edit that guy.
01:26:11.219 --> 01:26:11.489 Cool.
01:26:17.449 --> 01:26:19.179 That percent off for new customers.
01:26:24.859 --> 01:26:25.349 OK.
01:26:26.449 --> 01:26:27.719 It's a little different.
01:26:27.959 --> 01:26:29.349 Yeah, it is a little different.
01:26:29.769 --> 01:26:31.749 That's OK. Let's walk through it.
01:26:33.449 --> 01:26:36.529 OK. So if we wanted to set one that had.
01:26:34.079 --> 01:26:34.869 So you can.
01:26:35.639 --> 01:26:38.776 You can think of a price rule as pretty much a discount. Have you
01:26:38.776 --> 01:26:40.629 ever set up a discount before in Seth?
01:26:41.669 --> 01:26:45.931 I was setting some of these price rules up, but I was doing
01:26:45.931 --> 01:26:49.980 it in a like on a different window earlier this week, so
01:26:48.889 --> 01:26:49.549 Yeah, it was.
01:26:49.980 --> 01:26:54.383 this is just it looks similar but slightly different. So like
01:26:52.889 --> 01:26:56.889 Yeah, we were working in Aqua. That's an older project.
01:26:54.383 --> 01:26:56.159 if you were buying, yeah.
01:26:57.149 --> 01:27:01.967 If you are buying somewhere between 25 and 50 of these, then
01:27:01.967 --> 01:27:02.599 you get.
01:27:04.739 --> 01:27:07.609 Is this OK? This is a 1%. That's what this is saying, right?
01:27:07.919 --> 01:27:08.299 Mm-hmm.
01:27:08.659 --> 01:27:10.659 OK, then you get say a.
01:27:11.839 --> 01:27:13.339 10% discount.
01:27:14.849 --> 01:27:20.002 Uh, and then that can go from any date. So we say start today.
01:27:20.002 --> 01:27:21.719 Nope, that's January.
01:27:24.029 --> 01:27:24.729 Start.
01:27:26.239 --> 01:27:27.189 Today.
01:27:27.989 --> 01:27:29.659 And then uh.
01:27:30.289 --> 01:27:33.349 If you leave this blank, it goes just forever, yeah.
01:27:36.689 --> 01:27:37.529 I think so.
01:27:37.839 --> 01:27:38.319 OK.
01:27:39.139 --> 01:27:40.869 But let's say we wanna end it on.
01:27:40.049 --> 01:27:41.579 That I'd need to confirm.
01:27:42.059 --> 01:27:44.059 Say April 21st for laughs.
01:27:44.939 --> 01:27:45.589 Uh.
01:27:46.429 --> 01:27:49.039 And then unit of measure that's a, that's a new one.
01:27:52.849 --> 01:27:57.309 Umm, what is this asking about? Is this just like each?
01:27:55.829 --> 01:27:56.539 So.
01:27:58.639 --> 01:28:00.709 Yes, that's one of the values.
01:27:59.299 --> 01:28:00.509 That is fascinating.
01:28:01.569 --> 01:28:02.239 Umm.
01:28:01.589 --> 01:28:01.999 OK.
01:28:07.469 --> 01:28:09.219 OK and.
01:28:10.919 --> 01:28:15.112 Wait, what is that technically used for Eric for the unit of
01:28:15.112 --> 01:28:19.235 measure is that for like if it was for a pack or for a, you
01:28:19.235 --> 01:28:19.579 know?
01:28:20.009 --> 01:28:20.739 Curl down.
01:28:21.109 --> 01:28:26.083 Yeah, I'd have to so that I will, I will 100% admit that
01:28:26.083 --> 01:28:26.519 this.
01:28:27.839 --> 01:28:31.233 Price rules kind of in general, needs some good, thorough
01:28:31.233 --> 01:28:34.569 testing across all of them. But that would be what what?
01:28:37.519 --> 01:28:42.436 What the ideal scenario there is is that so any products that
01:28:42.436 --> 01:28:47.274 have a unit of measure of each would get this price rule. So
01:28:47.274 --> 01:28:51.874 you could have like you know instead of a instead of a 1%
01:28:51.874 --> 01:28:56.712 markdown maybe for a pack you get a 15 or so. .1 is actually
01:28:56.712 --> 01:28:57.029 10%.
01:28:58.289 --> 01:29:00.903 But you know, maybe you get a 15% discount if you buy a pack
01:29:00.903 --> 01:29:03.603 of four or whatever. And so you could put that unit of measure
01:29:03.219 --> 01:29:03.459 But.
01:29:03.603 --> 01:29:03.989 in there.
01:29:04.549 --> 01:29:06.459 So the the .1.
01:29:04.699 --> 01:29:06.808 And she said, yeah, I thought that would be a different
01:29:06.808 --> 01:29:07.109 product.
01:29:07.119 --> 01:29:11.299 Down down here it says the combinable 0.1% markdown.
01:29:14.089 --> 01:29:17.189 So should this be 10 if we wanted 10%?
01:29:17.379 --> 01:29:17.929 Yeah.
01:29:24.369 --> 01:29:26.049 Oh yeah, because it is percentage cool.
01:29:30.409 --> 01:29:31.839 So we'll give it a currency.
01:29:34.639 --> 01:29:35.889 U.S. dollars.
01:29:36.809 --> 01:29:38.519 Umm. And then.
01:29:39.649 --> 01:29:42.104 What is? What's the difference between combinable and
01:29:42.104 --> 01:29:42.559 exclusive?
01:29:42.889 --> 01:29:44.099 I was just going to ask you.
01:29:45.279 --> 01:29:45.769 Oh.
01:29:47.169 --> 01:29:47.889 Uh.
01:29:50.299 --> 01:29:51.529 From pineapple.
01:29:52.339 --> 01:29:55.959 Would be if you could combine it with any other discounts versus
01:29:55.959 --> 01:29:59.468 exclusive would be. If you get this discount you cannot use it
01:29:56.199 --> 01:29:56.499 App.
01:29:59.468 --> 01:30:02.809 for or you cannot use any other discount codes or anything.
01:30:03.979 --> 01:30:08.456 It's not really a discount code, but you can't combine that with
01:30:08.456 --> 01:30:12.313 other price rules if it's exclusive, and I believe that
01:30:12.313 --> 01:30:16.238 that is dependent on the priority. So if there are price
01:30:16.238 --> 01:30:20.164 rules set across multiple products and they have both of
01:30:20.164 --> 01:30:24.365 those in the cart, whichever one has the highest priority is
01:30:24.365 --> 01:30:28.291 going to take effect. If it's set for exclusive. If it's
01:30:27.689 --> 01:30:31.565 Well, if it's, if it's different products though, then it will,
01:30:28.291 --> 01:30:29.599 combined, go ahead.
01:30:31.565 --> 01:30:35.380 then the price will sell. Like if you had two price rules, one
01:30:35.380 --> 01:30:38.953 for product A and one for product B, the exclusivity there
01:30:38.953 --> 01:30:42.890 wouldn't matter because product A would have product A would get
01:30:42.890 --> 01:30:46.342 product A's price and then product B would get product's
01:30:44.589 --> 01:30:44.929 Mm-hmm.
01:30:46.342 --> 01:30:50.217 price. But let's say for example for product a, you had a price
01:30:50.217 --> 01:30:53.669 rule that said anybody from the United States gets a 10%
01:30:53.449 --> 01:30:54.609 Ohh.
01:30:53.669 --> 01:30:57.242 discount and then you have a separate price rule that says
01:30:57.242 --> 01:30:59.059 anybody that is the user role.
01:31:00.369 --> 01:31:04.090 Affiliate Admin gets a 20% discount on product A.
01:31:04.090 --> 01:31:08.704 Combinable means that if if I'm both a affiliate admin and in
01:31:08.704 --> 01:31:13.541 the United States, I would get a 10% and then what did I say 20%
01:31:13.541 --> 01:31:18.378 on top of that? Exclusive means that correct the priority if the
01:31:18.378 --> 01:31:20.759 10% for United States is higher.
01:31:21.599 --> 01:31:26.811 Then let's say the priority on that is 100, whereas the one for
01:31:26.811 --> 01:31:31.778 affiliate admin is 50. Then it would get the 100 so it would
01:31:31.659 --> 01:31:35.959 OK. So that a higher priority, uh number would go first.
01:31:31.778 --> 01:31:32.429 get the.
01:31:36.189 --> 01:31:36.699 Correct.
01:31:36.859 --> 01:31:37.349 Mm-hmm.
01:31:36.989 --> 01:31:37.309 OK.
01:31:39.949 --> 01:31:44.518 A good use case that I've seen this on is where I I ran into
01:31:40.229 --> 01:31:41.409 To set that as 100.
01:31:44.518 --> 01:31:49.312 some clients that have multiple price lists associated with one
01:31:49.312 --> 01:31:53.956 customer, meaning yeah, exactly ADI. And basically we have to
01:31:50.339 --> 01:31:51.689 80I.
01:31:53.956 --> 01:31:58.450 set up priority on it to say ohh for this customer and this
01:31:58.450 --> 01:32:02.719 product out of these nine different prices they have for
01:32:02.719 --> 01:32:06.539 that product go select the highest priority price.
01:32:09.479 --> 01:32:13.236 Yeah. And that's where price rules. You can get a lot more
01:32:13.236 --> 01:32:17.375 specific with what you're with, what you want typically on price
01:32:17.375 --> 01:32:21.323 points, it's that it's a lot more simple, but that means it's
01:32:21.323 --> 01:32:24.888 also a little bit more performant, whereas price rules,
01:32:21.779 --> 01:32:22.119 Mm-hmm.
01:32:24.888 --> 01:32:26.289 you can be a lot more.
01:32:27.589 --> 01:32:31.370 Picky and you can set up a lot of very intricate pricing rules,
01:32:31.370 --> 01:32:35.151 but the more price rules you set and the more complex the rules
01:32:35.151 --> 01:32:37.159 are, the lower their performance.
01:32:38.569 --> 01:32:39.229 Got it.
01:32:38.639 --> 01:32:41.369 Because I mean, you have to analyze all that data.
01:32:41.499 --> 01:32:46.389 So that OK, I'm gonna get very quiet specific.
01:32:43.709 --> 01:32:45.479 Now that makes sense.
01:32:47.719 --> 01:32:48.509 So.
01:32:49.739 --> 01:32:54.761 With lumber in particular, I think we had a performance issue
01:32:54.761 --> 01:32:57.839 between price points and price rules.
01:32:58.949 --> 01:33:03.674 And we were originally using price rules and it was causing
01:33:03.674 --> 01:33:08.635 issues with connect and so we moved them over to price points,
01:33:08.635 --> 01:33:10.919 which is the simpler version.
01:33:11.829 --> 01:33:12.749 Correct.
01:33:11.989 --> 01:33:16.177 Yeah. And like I said, 90% of our customers or potentially
01:33:16.177 --> 01:33:20.791 more are probably gonna be just fine with price points or tiered
01:33:20.791 --> 01:33:21.359 pricing.
01:33:23.429 --> 01:33:27.039 Or price lists, that kind of you can kind of consider all of
01:33:27.039 --> 01:33:30.648 those about the same and they can be done through the tiered
01:33:27.569 --> 01:33:28.199 Mm-hmm.
01:33:30.648 --> 01:33:34.317 pricing provider where you have a lot of very specific like I
01:33:34.317 --> 01:33:37.986 can't really put customers all in the same price list. I need
01:33:37.986 --> 01:33:41.358 some custom, it's all kind of dependent. You can see the
01:33:41.358 --> 01:33:45.086 different things in there. So categories, manufacturer stores,
01:33:45.086 --> 01:33:48.814 vendors, product types, account types, et cetera, where I need
01:33:48.814 --> 01:33:49.169 to be.
01:33:49.449 --> 01:33:52.509 You know, the more complex. That's where price rules comes
01:33:52.509 --> 01:33:55.672 into play. So I would always tend toward tiered pricing, but
01:33:53.349 --> 01:33:53.869 Got it.
01:33:55.672 --> 01:33:58.938 then go price rules. But that's that's probably something that
01:33:56.499 --> 01:33:56.989 Umm.
01:33:58.938 --> 01:34:02.101 we're gonna figure out in our in during the new architecture
01:34:02.101 --> 01:34:05.213 process. So not something too much that you'd have to worry
01:34:05.213 --> 01:34:08.272 about. But like in the discovery process, when we're going
01:34:08.272 --> 01:34:11.280 through there before the architecture person sees it, you
01:34:11.280 --> 01:34:14.183 would probably learn more towards tiered pricing. And I
01:34:14.183 --> 01:34:17.346 guess Kyle, that's kind of more for you specifically on this
01:34:17.346 --> 01:34:19.939 call because you're doing the original estimates.
01:34:20.489 --> 01:34:23.950 Yeah. No, that definitely makes sense. I mean, I I knew kind of
01:34:23.950 --> 01:34:27.302 the difference between I knew they basically operated kind of
01:34:27.302 --> 01:34:28.059 the same, but.
01:34:29.259 --> 01:34:32.902 That definitely makes sense. Where this is kind of more of
01:34:32.902 --> 01:34:36.731 like if you needed to have more complex logic like we do with
01:34:36.731 --> 01:34:40.621 discounts, I would go with price rules, where if it's just one
01:34:40.621 --> 01:34:44.265 price for these customers or it's just like 1 pricing tier
01:34:44.265 --> 01:34:48.093 for the customers, I can use price points. I don't need rules
01:34:48.093 --> 01:34:48.649 for that.
01:34:48.999 --> 01:34:53.292 Got it. So Trenton, just to give you a little clarification on
01:34:53.292 --> 01:34:56.359 Aqua it, we are actually using price points.
01:34:56.659 --> 01:34:57.149 Yeah.
01:34:59.309 --> 01:35:02.579 So that was where we were running into an issue.
01:35:03.419 --> 01:35:08.586 Where we couldn't put the same price points on multiple
01:35:08.586 --> 01:35:10.339 different products.
01:35:11.619 --> 01:35:14.559 Right. I think that's just because.
01:35:15.289 --> 01:35:18.314 It was like trying to use the same like we were going with
01:35:18.314 --> 01:35:21.494 just that one test price point and we didn't have the ability
01:35:21.494 --> 01:35:22.519 to create a new one.
01:35:22.879 --> 01:35:23.339 Umm.
01:35:23.969 --> 01:35:27.862 So that's why we need the developer assist there from Sur
01:35:27.862 --> 01:35:31.419 la rose to get that updated so that we can actually.
01:35:32.729 --> 01:35:33.569 Create the new ones.
01:35:34.019 --> 01:35:34.529 Gotcha.
01:35:35.089 --> 01:35:39.203 We are over and I could continue down this rabbit hole for days
01:35:39.203 --> 01:35:43.445 on end so we will continue this, but the big call out that I want
01:35:43.445 --> 01:35:47.623 everybody to take away from this is that I would like for all of
01:35:47.623 --> 01:35:51.672 you to spend a little time in here and kind of dig around, see
01:35:51.672 --> 01:35:55.529 what makes sense and there's going to be questions. There's
01:35:55.529 --> 01:35:59.771 going to be a ton of things that all of you are going to be like.
01:35:59.771 --> 01:36:03.628 I don't really understand how this relates or how does this
01:36:03.628 --> 01:36:04.399 sales order.
01:36:04.679 --> 01:36:09.079 Translate to. You know this quote or whatever. Take some
01:36:09.079 --> 01:36:13.169 time, go through stuff admin, click all the buttons.
01:36:13.879 --> 01:36:17.453 And if something does not make sense to you, write it down so
01:36:17.453 --> 01:36:21.257 that we can take these questions back and continue this series of
01:36:21.257 --> 01:36:24.830 training as well as getting with me individually or some time
01:36:24.830 --> 01:36:28.519 with Eric or whatever so that we can get you guys, you know, as
01:36:28.519 --> 01:36:30.709 comfortable as you want to be in CEF.
01:36:31.169 --> 01:36:35.590 Umm, I would like for you all to just kind of run through this
01:36:35.590 --> 01:36:40.011 over the next two weeks and I want to have a list of questions
01:36:40.011 --> 01:36:43.309 by the time we have our next training session.
01:36:46.109 --> 01:36:46.539 You're here.
01:36:47.689 --> 01:36:48.059 Cool.
01:36:47.719 --> 01:36:48.549 Do you time logs?
01:36:49.179 --> 01:36:49.679 You're here.
01:36:49.849 --> 01:36:51.779 I was just about to tell you that.
01:36:54.099 --> 01:36:55.889 Needs reallocation.
01:36:56.049 --> 01:36:58.309 I'm logs needs reallocation.
01:36:59.009 --> 01:36:59.579 Yes.
01:36:59.759 --> 01:37:00.619 Sprint goals.