| Topic | Presenter | Summary | Duration |
| --------------------------------------------------- | ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- |
| Displaying Medical Questionnaire as a Slider/Wizard | Danny P. Michael P. Patrick W. | The medical questionnaire is presented to users as a step during registration. Because it will have around 10-20 questions, the task was to display it as a slider/wizard, where each question is displayed one at a time, so as to provide a better user experience than listing out all of the questions at once. | 1:53:33 |00:00:07.130 --> 00:00:12.877 So I've got a message be this
00:00:12.877 --> 00:00:17.880 medical questionnaire. And uhm.
00:00:17.880 --> 00:00:21.460 Trying to figure out how to get this set up.
00:00:21.460 --> 00:00:24.590 The task that I have.
00:00:24.590 --> 00:00:27.218 Says create placeholder questions.
00:00:27.218 --> 00:00:29.189 I've done that.
00:00:29.190 --> 00:00:31.185 But when a user answers these questions,
00:00:31.190 --> 00:00:33.326 the information that they answer the
00:00:33.326 --> 00:00:35.610 question we will need to be edited.
00:00:35.610 --> 00:00:37.619 By the user at a later date.
00:00:37.620 --> 00:00:40.005 So it just needs to be saved to the
00:00:40.005 --> 00:00:42.247 user and the user will need to be
00:00:42.247 --> 00:00:45.820 able to view these later, same thing.
00:00:45.820 --> 00:00:48.025 Name must answer all these
00:00:48.025 --> 00:00:50.230 questions before leaving this step.
00:00:50.230 --> 00:00:51.860 So, uhm.
00:00:55.130 --> 00:00:58.196 Right now every question or every
00:00:58.196 --> 00:01:01.136 answer input has this next button
00:01:01.136 --> 00:01:04.328 and we were going to try to put
00:01:04.430 --> 00:01:07.216 this in like sort of a slider.
00:01:07.220 --> 00:01:11.994 So that, uh, you know you display.
00:01:12.000 --> 00:01:14.856 You type in the answer you click next.
00:01:14.860 --> 00:01:19.780 It saves it. And then come.
00:01:19.780 --> 00:01:22.412 You go into the next one and then
00:01:22.412 --> 00:01:24.367 after you've done all of them,
00:01:24.370 --> 00:01:27.058 then you can confirm and go on to
00:01:27.058 --> 00:01:29.810 the next step in the registration.
00:01:29.810 --> 00:01:32.414 Uhm, I'm I asked the PM if
00:01:32.414 --> 00:01:34.580 that's what they want to do.
00:01:34.580 --> 00:01:37.516 I haven't gotten an answer yet on that,
00:01:37.520 --> 00:01:40.448 so I just until that's kind of decided.
00:01:40.450 --> 00:01:43.386 I just wanted to figure out the answer.
00:01:43.390 --> 00:01:47.390 Saving piece. And so.
00:01:47.390 --> 00:01:52.600 Here is a kind of what got so far we've got.
00:01:52.600 --> 00:01:56.289 This directive that I took from RX1,
00:01:56.290 --> 00:01:59.299 uhm medical question?
00:01:59.300 --> 00:02:00.950 And it's got a bum.
00:02:03.360 --> 00:02:06.400 This controller.
00:02:06.400 --> 00:02:09.298 And so that will display the
00:02:09.298 --> 00:02:12.010 question and it's iterating through.
00:02:12.010 --> 00:02:14.992 Uhm, the questions that are in
00:02:14.992 --> 00:02:18.250 here which are being called from.
00:02:18.250 --> 00:02:21.902 From the back end.
00:02:21.902 --> 00:02:29.430 Through this CVAP contacts. So that is.
00:02:29.430 --> 00:02:31.800 Working, it's pulling in the questions,
00:02:31.800 --> 00:02:36.480 but then I need to be able to.
00:02:36.480 --> 00:02:39.536 You know, type in an answer, save it.
00:02:39.536 --> 00:02:42.320 And then go on to the next one,
00:02:42.320 --> 00:02:44.996 typing an answer or save it.
00:02:45.000 --> 00:02:48.330 And uhm, I guess for now, you know,
00:02:48.330 --> 00:02:51.235 have this next button saving the answers.
00:02:53.280 --> 00:02:56.076 It's set up. As like a.
00:02:59.960 --> 00:03:03.719 As like an array of this user
00:03:03.719 --> 00:03:07.428 answer model. So each answer. Uhm?
00:03:11.560 --> 00:03:16.100 Each answer comes in as.
00:03:16.100 --> 00:03:17.548 This user answer model.
00:03:17.548 --> 00:03:19.720 And then they all get saved
00:03:19.793 --> 00:03:21.749 as a survey and this is
00:03:21.749 --> 00:03:23.700 supposed to get pushed back to.
00:03:25.790 --> 00:03:27.980 It's a create user answer.
00:03:31.350 --> 00:03:34.622 So. That's where I'm at,
00:03:34.622 --> 00:03:36.410 and this is the problem that
00:03:36.479 --> 00:03:38.910 I'm having right now, is that?
00:03:38.910 --> 00:03:42.360 Because it's iterating through the questions,
00:03:42.360 --> 00:03:46.140 it's like 1 field here.
00:03:46.140 --> 00:03:47.736 That's. You know, yeah,
00:03:47.736 --> 00:03:51.358 I was looking at a little bit at the
00:03:51.358 --> 00:03:54.032 code and it looked like your answers
00:03:54.122 --> 00:03:57.378 were all being saved as the same string.
00:03:57.380 --> 00:03:59.996 Uhm, no. I saw that on.
00:04:00.000 --> 00:04:02.568 I think that Ng model right
00:04:02.568 --> 00:04:04.790 there that are register step.
00:04:04.790 --> 00:04:06.077 Customer control answer.
00:04:06.077 --> 00:04:09.590 Yeah OK yeah that makes that makes sense.
00:04:09.590 --> 00:04:15.062 I think what we might want to do is.
00:04:15.070 --> 00:04:16.060 Can we do?
00:04:18.820 --> 00:04:20.996 So I see there's a question ID could
00:04:20.996 --> 00:04:23.042 we could we somehow link this to
00:04:23.042 --> 00:04:25.650 a question ID? Uhm yeah, like 16.
00:04:28.240 --> 00:04:30.700 Yeah no, I thought question ID
00:04:30.700 --> 00:04:33.818 was there. Could we concatenate?
00:04:33.818 --> 00:04:36.340 The answer. And then, uh.
00:04:44.650 --> 00:04:50.404 Thinking. We might be able to escape.
00:04:50.410 --> 00:04:57.700 In that energy model. Miller and then.
00:04:57.700 --> 00:05:01.258 And question ID with the JavaScript.
00:05:01.260 --> 00:05:03.890 In that inside that escape.
00:05:03.890 --> 00:05:06.198 To differentiate each question.
00:05:10.610 --> 00:05:12.642 So is the goal we're trying to go
00:05:12.642 --> 00:05:14.790 for right now is just to get it to
00:05:14.790 --> 00:05:16.588 where when he puts in an answer.
00:05:16.590 --> 00:05:17.726 It's not for everyone,
00:05:17.726 --> 00:05:19.857 it's just for the one that he's
00:05:19.857 --> 00:05:21.297 actually trying to answer.
00:05:21.300 --> 00:05:22.808 So we're trying OK.
00:05:31.720 --> 00:05:33.868 Yeah, they the answer.
00:05:38.410 --> 00:05:40.270 Banking info for each question
00:05:40.270 --> 00:05:42.910 as an answer as a string C.
00:06:10.700 --> 00:06:11.530 So.
00:06:15.260 --> 00:06:17.310 Instead of.
00:06:24.360 --> 00:06:26.565 I'm thinking that string right there or
00:06:26.565 --> 00:06:29.370 answer is a string is where it's sort of.
00:06:29.370 --> 00:06:31.926 Keeping everything be the same answer.
00:06:31.930 --> 00:06:34.905 Yeah, it's all. It's all linked there.
00:06:34.910 --> 00:06:37.460 Could we instead make that a?
00:06:39.590 --> 00:06:40.400 Like a.
00:06:42.640 --> 00:06:44.488 I'm wanting to make it an array,
00:06:44.490 --> 00:06:47.580 but I'm trying to figure out how we know how
00:06:47.656 --> 00:06:50.536 many questions we have to fill the array.
00:06:50.540 --> 00:06:53.360 And you know what position wearing?
00:06:53.360 --> 00:06:57.910 Yeah. Well, here's what it looks like.
00:06:57.910 --> 00:07:01.230 In their database fairs.
00:07:01.230 --> 00:07:05.916 Uh, context. User Answer This is
00:07:05.916 --> 00:07:09.970 the contacts user question table.
00:07:09.970 --> 00:07:11.242 Although this another piece
00:07:11.242 --> 00:07:12.514 that's kind of weird.
00:07:12.520 --> 00:07:15.180 So here's the questions, right?
00:07:15.180 --> 00:07:17.500 And here's the text of all the questions,
00:07:17.500 --> 00:07:19.240 ideas or credit out of order.
00:07:19.240 --> 00:07:22.660 But they do have this custom key somd Q.
00:07:22.660 --> 00:07:25.643 You know, through like that, so we can.
00:07:25.643 --> 00:07:29.189 It can go by question ID.
00:07:29.190 --> 00:07:30.810 That probably goes by question idea.
00:07:30.810 --> 00:07:34.360 I don't know what their custom key is, but.
00:07:34.360 --> 00:07:35.070 Uhm?
00:07:37.220 --> 00:07:40.097 So you know you could say like
00:07:40.097 --> 00:07:42.739 the answer for question ID one
00:07:42.739 --> 00:07:45.805 for this user is whatever and it
00:07:45.904 --> 00:07:48.916 has this table which is contacts.
00:07:48.920 --> 00:07:50.408 That user question.
00:07:53.410 --> 00:07:57.428 Now. Where are they getting that customer?
00:07:59.940 --> 00:08:01.540 That's that's that's not it.
00:08:01.540 --> 00:08:03.130 This. This is the one.
00:08:03.130 --> 00:08:05.038 This is the contact user answer.
00:08:05.040 --> 00:08:07.368 So there's like you know if user one
00:08:07.368 --> 00:08:09.828 comes in and answers question ID one,
00:08:09.830 --> 00:08:12.740 then their answer gets stored there.
00:08:12.740 --> 00:08:15.218 And like when they pull up their
00:08:15.218 --> 00:08:17.613 user dashboard, it'll pull up.
00:08:17.613 --> 00:08:20.979 Like you know the all the
00:08:20.979 --> 00:08:24.184 answers for that user ID. And.
00:08:24.184 --> 00:08:27.388 But the the weird thing is,
00:08:27.390 --> 00:08:31.457 so this is contacts dot user answer.
00:08:31.460 --> 00:08:34.480 If we go back.
00:08:34.480 --> 00:08:37.427 To here to the create user answer.
00:08:39.460 --> 00:08:45.038 Uhm? This says contacts.
00:08:45.040 --> 00:08:46.470 User answer create Oh no,
00:08:46.470 --> 00:08:47.890 I guess that is right.
00:08:52.860 --> 00:08:54.555 OK, never mind.
00:08:54.555 --> 00:08:58.510 So that this is going to create
00:08:58.632 --> 00:09:02.598 an entry in contacts user answer.
00:09:02.600 --> 00:09:04.368 Right, yeah, post it.
00:09:06.510 --> 00:09:08.778 So that's sending it to URL.
00:09:12.430 --> 00:09:15.181 They're doing this that route URL slash
00:09:15.181 --> 00:09:17.379 contact slash user is such great,
00:09:17.380 --> 00:09:20.047 so they're sending it to that URL.
00:09:20.050 --> 00:09:22.630 They're doing a post and
00:09:22.630 --> 00:09:24.694 they're doing route params.
00:09:24.700 --> 00:09:27.170 Miller route Bramson.
00:09:27.170 --> 00:09:29.480 Guessing is what we feed inside.
00:09:29.480 --> 00:09:30.638 Create user answer.
00:09:40.000 --> 00:09:40.690 OK.
00:09:42.770 --> 00:09:43.780 Uhm?
00:09:52.490 --> 00:09:53.918 So do we have?
00:09:57.990 --> 00:10:01.441 So I think you're right that it
00:10:01.441 --> 00:10:04.864 does need to save the. Question ID.
00:10:04.864 --> 00:10:08.160 So here when you click the button it
00:10:08.251 --> 00:10:11.131 does this create answer record function
00:10:11.131 --> 00:10:15.156 and passes in the question ID of the
00:10:15.156 --> 00:10:18.186 current question that is iterating serve.
00:10:18.190 --> 00:10:19.798 So that's how it knows which
00:10:19.798 --> 00:10:20.870 question you just answered.
00:10:20.870 --> 00:10:24.263 So all the answers are just going to be.
00:10:24.270 --> 00:10:27.140 Share the end point is going to
00:10:27.140 --> 00:10:30.015 be shared is a. What I'm saying.
00:10:30.015 --> 00:10:33.770 OK, so if you're doing a slider then.
00:10:33.770 --> 00:10:36.594 Uhm, imagine like a sort of like a
00:10:36.594 --> 00:10:38.885 slideshow for each question, possibly,
00:10:38.885 --> 00:10:42.210 although you said that's still in question.
00:10:42.210 --> 00:10:46.260 Uh-huh you know if you continue on with
00:10:46.260 --> 00:10:48.806 the slider then I could see some what a.
00:10:48.810 --> 00:10:51.114 Of a way that we could do this if
00:10:51.114 --> 00:10:53.320 it just shows one question at a
00:10:53.320 --> 00:10:55.864 time on that Ng click, it submits.
00:10:55.864 --> 00:10:57.849 But you could also possibly.
00:10:57.850 --> 00:11:00.230 Have that input cleared.
00:11:00.230 --> 00:11:06.170 For the next question. Miller OK.
00:11:06.170 --> 00:11:08.456 But that's only if we keep the slider up.
00:11:08.460 --> 00:11:12.360 If we keep it as a list like this, then.
00:11:12.360 --> 00:11:16.900 And yeah, well, I had to. Come up with.
00:11:16.900 --> 00:11:22.767 Separating each inputs with an ID. Alright.
00:11:22.767 --> 00:11:27.156 Right, so if it's a slider though.
00:11:27.160 --> 00:11:30.445 Then it will work because there is only one.
00:11:30.450 --> 00:11:33.544 There will only be one input in
00:11:33.544 --> 00:11:35.979 this particular view at the time.
00:11:35.980 --> 00:11:37.363 Yeah, yeah, right.
00:11:37.363 --> 00:11:40.129 Yeah, that's that's what I'm imagining.
00:11:40.130 --> 00:11:41.066 Sort of a.
00:11:41.066 --> 00:11:43.250 I don't know if that's the correct
00:11:43.322 --> 00:11:44.637 way to go about it,
00:11:44.640 --> 00:11:46.968 so it's more of a hacky way the
00:11:46.968 --> 00:11:49.158 way it popped up on my end.
00:11:49.160 --> 00:11:51.560 But yeah, no on that next button click,
00:11:51.560 --> 00:11:54.881 we could empty out inputs so that it looks
00:11:54.881 --> 00:11:58.400 like it's fresh input for the next question.
00:11:58.400 --> 00:11:59.390 Right?
00:11:59.390 --> 00:12:00.380 OK.
00:12:03.410 --> 00:12:07.456 OK, so you click the next button.
00:12:07.460 --> 00:12:12.840 It calls this create answer record. Which.
00:12:16.330 --> 00:12:20.378 Console logs this questions.
00:12:20.380 --> 00:12:23.076 Since 4. Solacing, Sir.
00:12:23.076 --> 00:12:27.998 Is there OK? There's question ID.
00:12:28.000 --> 00:12:30.870 Yeah, so it. Here's the user answer,
00:12:30.870 --> 00:12:34.970 which is based off this model and it puts in.
00:12:34.970 --> 00:12:37.122 It includes the question
00:12:37.122 --> 00:12:39.274 ID you're passing in.
00:12:39.280 --> 00:12:41.076 It includes the answer,
00:12:41.076 --> 00:12:44.249 which is the sharing has to be
00:12:44.249 --> 00:12:47.377 active and it has to be created date.
00:12:47.380 --> 00:12:49.780 Uhm, those are required fields
00:12:49.780 --> 00:12:52.788 on that table and then it
00:12:52.788 --> 00:12:54.820 calls create user answer.
00:12:56.930 --> 00:13:01.560 And then you're saying, uhm?
00:13:01.560 --> 00:13:06.528 Clear that input when it when you click next.
00:13:06.530 --> 00:13:10.820 So creative. Would there be a
00:13:10.820 --> 00:13:14.060 directive like on this on this button?
00:13:14.060 --> 00:13:16.435 So that's another function create
00:13:16.435 --> 00:13:19.284 answer record that I think we
00:13:19.284 --> 00:13:21.654 were just looking at second ago,
00:13:21.660 --> 00:13:22.554 creating centered,
00:13:22.554 --> 00:13:24.789 so that's like after discussion.
00:13:24.790 --> 00:13:28.804 Yeah, I would do like this dot CVAP dot.
00:13:31.130 --> 00:13:34.520 Contacts dot answer.
00:13:38.140 --> 00:13:39.690 Uh, that's not an option.
00:13:39.690 --> 00:13:42.516 It looks like is it probably.
00:13:42.520 --> 00:13:45.190 Right after the CV API maybe?
00:13:47.890 --> 00:13:50.644 No, it would have to be after contact some.
00:13:54.210 --> 00:13:55.908 What I was saying is this,
00:13:55.910 --> 00:13:57.620 where you would clear the input?
00:13:57.620 --> 00:14:00.077 Yeah, that's a that's sort of what I was
00:14:00.077 --> 00:14:02.160 trying to lead you to getting answer.
00:14:02.160 --> 00:14:05.862 Just be an empty string again. Uhm?
00:14:05.862 --> 00:14:11.948 Oh, OK. Ping. Well, the answer is.
00:14:17.900 --> 00:14:21.588 Here so we can just set up custom
00:14:21.588 --> 00:14:23.639 body controller dot answer.
00:14:25.800 --> 00:14:26.570 Yeah.
00:14:30.310 --> 00:14:32.884 But if this is. If you
00:14:32.884 --> 00:14:34.600 call this study answer.
00:14:38.380 --> 00:14:43.020 Don't ask her to this answer here. Uhm?
00:14:45.920 --> 00:14:49.838 I. Yeah, 'cause you set it up online 50.
00:14:49.840 --> 00:14:52.837 Yeah, we should be looking at that same one.
00:14:52.840 --> 00:14:55.790 So I think that might.
00:14:55.790 --> 00:14:57.798 Might do what we're wanting it to do.
00:14:57.800 --> 00:14:59.808 OK, as soon as we get the next,
00:14:59.810 --> 00:15:01.178 the next input should.
00:15:01.178 --> 00:15:04.370 I guess all the input should declare. Yeah.
00:15:11.610 --> 00:15:14.274 Oh yeah, yeah. So I guess we could.
00:15:14.280 --> 00:15:17.430 Test this as well and then The thing is,
00:15:17.430 --> 00:15:20.755 this isn't a. It isn't even adding.
00:15:20.760 --> 00:15:24.310 The answers in right now.
00:15:24.310 --> 00:15:25.470 Which even though we don't
00:15:25.470 --> 00:15:26.630 have a slider in there,
00:15:26.630 --> 00:15:28.580 it should at least be.
00:15:28.580 --> 00:15:30.260 Uhm, putting answers in here,
00:15:30.260 --> 00:15:30.930 shouldn't it?
00:15:33.970 --> 00:15:39.152 Yes. Context I using answer
00:15:39.152 --> 00:15:42.567 creating record create user answer.
00:15:45.310 --> 00:15:48.327 Are we seeing that console log of
00:15:48.327 --> 00:15:51.810 this questions? Come let me see.
00:15:51.810 --> 00:15:55.485 So that is what that's when we.
00:15:55.490 --> 00:16:00.162 Click next. Say I'm getting used
00:16:00.162 --> 00:16:02.527 to this theme taskbar style.
00:16:02.530 --> 00:16:06.120 Trying this out instead of the. Buttons.
00:16:10.320 --> 00:16:12.798 Yes, we do get answers and we
00:16:12.798 --> 00:16:15.457 got a post of 404 not found.
00:16:15.460 --> 00:16:18.540 So that's probably why it's not submitting.
00:16:18.540 --> 00:16:23.830 Uhm? Invalid form check with name
00:16:23.830 --> 00:16:26.840 check agreed is not focusable.
00:16:26.840 --> 00:16:30.816 OK, then we got this 404 UM.
00:16:36.900 --> 00:16:37.550 Well then.
00:16:44.290 --> 00:16:46.414 Are we able to always saying it's not found?
00:16:46.420 --> 00:16:48.820 Like it's not even there?
00:16:48.820 --> 00:16:50.710 If you ask her friends contacts
00:16:50.710 --> 00:16:52.599 using her answer, so that's great.
00:16:55.840 --> 00:16:58.216 Surely API storefronts is in there?
00:16:58.220 --> 00:17:00.999 Uhm, why is that not in there?
00:17:17.280 --> 00:17:19.730 CBI contacts.
00:17:26.140 --> 00:17:29.880 This is. Framework store.
00:17:32.640 --> 00:17:39.670 API root uhm? And this is more than.
00:17:39.670 --> 00:17:44.190 Just like back end. Let me take a look
00:17:44.190 --> 00:17:46.920 at that link one more time on the error.
00:17:50.600 --> 00:17:57.279 On this. I'm on the browser. OK, we want.
00:17:57.279 --> 00:18:00.844 API storefront contacts user answers
00:18:00.844 --> 00:18:04.650 creates which I'm really not that.
00:18:04.650 --> 00:18:06.394 That should be a folder on the web
00:18:06.394 --> 00:18:09.450 nine side, but I'm not too sure.
00:18:09.450 --> 00:18:12.108 How it gets there API storefront
00:18:12.108 --> 00:18:15.020 is a I believe like an 06.
00:18:15.020 --> 00:18:18.930 Folder. So yeah, I'd be a.
00:18:18.930 --> 00:18:20.858 Imagine some back end.
00:18:23.270 --> 00:18:26.210 I think it's like store.
00:18:26.210 --> 00:18:28.558 Let's see. 06 storefronts,
00:18:28.558 --> 00:18:32.090 06 storefronts and three more, yeah?
00:18:34.330 --> 00:18:36.346 But then at this point I'm not too
00:18:36.346 --> 00:18:38.290 sure what it touched at this point
00:18:38.290 --> 00:18:40.190 because I don't see any folders,
00:18:40.190 --> 00:18:42.470 so this is where I honestly
00:18:42.470 --> 00:18:44.880 would come to a stop. OK.
00:18:48.360 --> 00:18:50.880 I'm not sure why that's not found.
00:18:50.880 --> 00:18:54.096 Are we able to? I don't know that's
00:18:54.096 --> 00:18:55.708 not going to give us anything return
00:18:55.708 --> 00:18:57.465 just right clicking and opening it up.
00:19:01.690 --> 00:19:03.678 It'll tell us it's not found again.
00:19:12.040 --> 00:19:12.710 Well.
00:19:16.560 --> 00:19:19.590 And I'll try to get a back end at this point.
00:19:19.590 --> 00:19:22.520 Try to see possibly why.
00:19:22.520 --> 00:19:26.025 We're not finding that a
00:19:26.025 --> 00:19:29.140 storefront contacts. Yeah.
00:19:29.140 --> 00:19:32.820 OK, uh, let's see.
00:19:32.820 --> 00:19:35.948 There's on SSB here.
00:19:44.440 --> 00:19:50.090 Brandon Lyon. He looks like he's. Busy.
00:19:50.090 --> 00:19:54.176 Haha. Everybody is crazy. Let's see.
00:19:58.470 --> 00:20:01.200 Yeah, Patrick Wang.
00:20:01.200 --> 00:20:05.656 Yes, not sure if you'd be able to.
00:20:05.660 --> 00:20:07.000 Although he's pretty pretty
00:20:07.000 --> 00:20:08.005 savvy with everything,
00:20:08.010 --> 00:20:10.014 I feel like I would say
00:20:10.014 --> 00:20:11.360 usually fixes all, yeah.
00:20:13.510 --> 00:20:15.508 See, he's got a green bubble.
00:20:15.510 --> 00:20:18.030 I wanna get back in here, yeah?
00:20:20.880 --> 00:20:22.090 Else, oh, I don't know.
00:20:22.090 --> 00:20:23.770 I'll let you type. Maybe he's busy.
00:20:23.770 --> 00:20:26.180 I don't want to just call him in I guess.
00:21:00.730 --> 00:21:04.759 Hello welcome. Hello.
00:21:04.760 --> 00:21:09.680 Hey Patrick. It's going OK.
00:21:09.680 --> 00:21:12.880 We got Danny controlling.
00:21:12.880 --> 00:21:19.344 OK, yeah, so this is for FSB uhm?
00:21:19.350 --> 00:21:22.416 We are trying to set up the.
00:21:22.420 --> 00:21:25.042 I am trying to test the
00:21:25.042 --> 00:21:25.916 medical questionnaire.
00:21:25.920 --> 00:21:32.207 UM these guys are helping me. And. It's.
00:21:32.207 --> 00:21:37.589 Doing this create answer record function.
00:21:37.590 --> 00:21:41.245 Which, uh, calls create user
00:21:41.245 --> 00:21:44.900 answer on CDI API contacts.
00:21:44.900 --> 00:21:49.316 And. That's supposed to go to.
00:21:49.320 --> 00:21:54.318 This URL contacts user answer create.
00:21:54.320 --> 00:21:57.620 But when we press it,
00:21:57.620 --> 00:21:59.126 it's giving this.
00:21:59.126 --> 00:22:02.138 It's making a post request and
00:22:02.138 --> 00:22:04.447 then it's giving a 404.
00:22:04.450 --> 00:22:05.280 For this.
00:22:09.220 --> 00:22:12.610 Text content users with grades.
00:22:15.440 --> 00:22:20.126 OK, uh. What is that error?
00:22:20.130 --> 00:22:22.230 Invalid phone control with name
00:22:22.230 --> 00:22:25.180 equals CK agreed is not focusable.
00:22:28.510 --> 00:22:29.990 Well, we're not too sure.
00:22:29.990 --> 00:22:32.950 We just saw it pop up along with this 404.
00:22:32.950 --> 00:22:35.318 Could we maybe search that in the code?
00:22:37.410 --> 00:22:38.594 Yeah, uh, OK agreed,
00:22:38.594 --> 00:22:41.649 can we take a look at where it's being?
00:22:41.650 --> 00:22:42.994 Uh, hailed from like,
00:22:42.994 --> 00:22:45.496 can we right click on the registration
00:22:45.496 --> 00:22:47.980 hashtag return like the link on
00:22:47.980 --> 00:22:50.656 the right and it do open new tab?
00:22:50.660 --> 00:22:52.808 Yeah, yes we can see where
00:22:52.808 --> 00:22:54.520 it's hailing from. Yeah.
00:22:59.170 --> 00:23:03.685 Oh well, it's just this registration uhm?
00:23:03.690 --> 00:23:07.890 Which is the whole registration thing.
00:23:07.890 --> 00:23:11.940 You know, oh, is this at the same page?
00:23:11.940 --> 00:23:15.356 Yeah, it's this is starting back at UM.
00:23:17.420 --> 00:23:19.590 At the beginning of it,
00:23:19.590 --> 00:23:22.910 but we are on step three and we're
00:23:22.910 --> 00:23:25.940 getting this error. OK, so, uh, OK,
00:23:25.940 --> 00:23:29.570 so that's that that error is being thrown.
00:23:29.570 --> 00:23:33.287 Uh, sorry, this is a sort of question about
00:23:33.287 --> 00:23:37.041 that area is being thrown because with
00:23:37.041 --> 00:23:40.589 these registration forms they put in special.
00:23:40.590 --> 00:23:43.270 Blocks to prevent people from.
00:23:43.270 --> 00:23:45.270 Essentially hijacking and reading
00:23:45.270 --> 00:23:47.270 what previously has entered,
00:23:47.270 --> 00:23:48.674 like keylogging essentially.
00:23:48.674 --> 00:23:52.770 So once it's been entered the form disappear.
00:23:52.770 --> 00:23:56.138 It's no longer editable.
00:23:56.140 --> 00:23:57.420 It's probably for home,
00:23:57.420 --> 00:23:58.700 you know, entering something,
00:23:58.700 --> 00:24:00.441 injecting some sort data, and.
00:24:00.441 --> 00:24:01.363 You know,
00:24:01.363 --> 00:24:04.129 hitting all the validation and stuff.
00:24:04.130 --> 00:24:06.270 So that should be fine,
00:24:06.270 --> 00:24:08.808 but you're saying the posts is
00:24:08.808 --> 00:24:11.425 not available and can you show
00:24:11.425 --> 00:24:13.520 me the endpoint call again?
00:24:17.050 --> 00:24:20.194 Not this one, so this is
00:24:20.194 --> 00:24:22.900 the create user in Sir.
00:24:22.900 --> 00:24:24.745 User routes, contacts,
00:24:24.745 --> 00:24:27.820 user is great and it's
00:24:27.820 --> 00:24:31.177 a post OK and then come.
00:24:31.180 --> 00:24:33.574 Can you show me indeed TypeScript
00:24:33.574 --> 00:24:36.240 where you're making this call? Yeah.
00:24:40.200 --> 00:24:44.670 And you're making. Create a circular.
00:24:47.340 --> 00:24:48.860 This time using Siri.
00:24:51.570 --> 00:24:53.020 And this is being called
00:24:53.020 --> 00:24:54.180 from the next button.
00:25:06.030 --> 00:25:10.258 Wait, so you're creating a new user?
00:25:10.260 --> 00:25:15.739 Uh, no uhm. Or creating an
00:25:15.739 --> 00:25:19.604 or creating a user answer.
00:25:19.610 --> 00:25:21.685 Uhm, and basically we're we're
00:25:21.685 --> 00:25:24.551 creating this to add it to the
00:25:24.551 --> 00:25:27.029 database and so that it ties the
00:25:27.029 --> 00:25:29.228 answer that they are entering,
00:25:29.230 --> 00:25:32.270 which this is the answer from the input
00:25:32.270 --> 00:25:34.809 field along with the current question
00:25:34.809 --> 00:25:37.660 that they're on by the question ID.
00:25:37.660 --> 00:25:40.720 And then you know these two
00:25:40.720 --> 00:25:42.760 are just not null.
00:25:42.760 --> 00:25:44.730 A column from the database.
00:25:47.790 --> 00:25:51.927 OK and then is there gonna be
00:25:51.927 --> 00:25:55.980 multiple questions? Uhm yes.
00:25:55.980 --> 00:25:58.170 You could show him the database,
00:25:58.170 --> 00:26:04.960 I think SMS. Yeah, so this, UM.
00:26:04.960 --> 00:26:10.900 This, uh, user answer is it's just one user
00:26:10.900 --> 00:26:16.572 answer and so it goes out and makes this UM.
00:26:16.580 --> 00:26:18.190 I don't and that's that's
00:26:18.190 --> 00:26:19.800 what this is up here.
00:26:19.800 --> 00:26:21.800 I don't remember what we
00:26:21.800 --> 00:26:23.400 were doing with this.
00:26:23.400 --> 00:26:25.674 Uhm, I think at first we
00:26:25.674 --> 00:26:27.879 were gonna put them all in.
00:26:27.880 --> 00:26:31.140 An array like that, uhm?
00:26:31.140 --> 00:26:35.137 I don't know if if that's still.
00:26:35.140 --> 00:26:37.300 Something we were planning used,
00:26:37.300 --> 00:26:39.775 but uhm doesn't look like
00:26:39.775 --> 00:26:42.250 it so anyways this is.
00:26:42.250 --> 00:26:45.701 You know this goes out and and
00:26:45.701 --> 00:26:49.180 puts each answer into the database.
00:26:49.180 --> 00:26:51.568 And yeah, uh, SMS.
00:26:54.620 --> 00:26:57.865 Patient so this is the user
00:26:57.865 --> 00:26:59.079 answer. User answer yeah.
00:27:02.080 --> 00:27:04.048 So this is the user answer.
00:27:04.050 --> 00:27:07.066 You know the answer field is here along
00:27:07.066 --> 00:27:10.108 with the question ID and the user ID.
00:27:10.110 --> 00:27:14.620 OK got it and then. Can we go look
00:27:14.620 --> 00:27:16.930 at the endpoint again real quick?
00:27:16.930 --> 00:27:19.490 Where you're calling it?
00:27:19.490 --> 00:27:23.032 Yeah, so you're saying this start user
00:27:23.032 --> 00:27:26.069 insert question ID question in Sir.
00:27:26.070 --> 00:27:28.846 And show me the error of front end
00:27:28.846 --> 00:27:32.220 it the air on the front end saying
00:27:32.220 --> 00:27:34.879 that that endpoint does not exist.
00:27:34.880 --> 00:27:37.925 So are we sure that endpoints working?
00:27:37.930 --> 00:27:41.157 UMSL you can use to run that.
00:27:43.830 --> 00:27:47.160 No. I don't I.
00:27:47.160 --> 00:27:49.500 I'm not sure that it's running.
00:27:49.500 --> 00:27:51.630 Like where was this copied from?
00:27:54.030 --> 00:27:59.160 Uhm? This was.
00:27:59.160 --> 00:28:01.500 The more direct answer would be
00:28:01.500 --> 00:28:04.548 is does the back end have the
00:28:04.548 --> 00:28:06.883 ability to receive these answers?
00:28:06.890 --> 00:28:10.650 Yeah, I I think what we did was.
00:28:10.650 --> 00:28:15.666 We came into, UM, CVICV API
00:28:15.666 --> 00:28:20.280 contacts and searched for answer.
00:28:20.280 --> 00:28:23.656 And we found a few different of these
00:28:23.656 --> 00:28:27.255 and then we found this one which said,
00:28:27.260 --> 00:28:30.305 you know, create a new user answer.
00:28:30.310 --> 00:28:32.490 So then we created this
00:28:32.490 --> 00:28:34.670 function based off of that.
00:28:37.070 --> 00:28:40.260 Filming, assuming that this was.
00:28:40.260 --> 00:28:43.076 Set all set up on the back end,
00:28:43.080 --> 00:28:47.480 but I don't know if it is it it may.
00:28:47.480 --> 00:28:50.243 Well, this is,
00:28:50.243 --> 00:28:54.848 this file is built dynamically.
00:28:54.850 --> 00:28:58.550 By the back end code.
00:28:58.550 --> 00:29:03.054 Oh well, if the back end are who?
00:29:03.060 --> 00:29:04.746 Did this or whoever pulled this
00:29:04.746 --> 00:29:06.958 in 2 SB did it correctly whenever
00:29:06.958 --> 00:29:09.684 they run like a I believe it's a
00:29:09.684 --> 00:29:11.630 T4 or something on the back end.
00:29:11.630 --> 00:29:13.570 They're supposed to generate these
00:29:13.570 --> 00:29:16.378 end points at the front end can hit.
00:29:16.380 --> 00:29:18.445 Uh-huh it's similar to what
00:29:18.445 --> 00:29:21.048 links CSS does you know there's
00:29:21.048 --> 00:29:23.754 a compile compile to style now.
00:29:26.980 --> 00:29:29.948 Are you able to search the solution
00:29:29.948 --> 00:29:32.195 for create user answer? Yeah,
00:29:32.195 --> 00:29:34.635 and is there any other instance of it?
00:29:45.060 --> 00:29:46.578 That's why we call it air,
00:29:46.580 --> 00:29:48.358 and these are just in that file.
00:29:51.280 --> 00:29:52.130 Searching now.
00:29:59.820 --> 00:30:02.736 'cause four, if I remember correctly,
00:30:02.740 --> 00:30:05.170 this should be for, well,
00:30:05.170 --> 00:30:10.258 the original usage of it was from RX1.
00:30:10.260 --> 00:30:15.560 Yeah, I don't know if RX one has a custom.
00:30:15.560 --> 00:30:17.042 Back in that they're not using
00:30:17.042 --> 00:30:19.016 for this, or if it has to go.
00:30:21.200 --> 00:30:24.375 Essentially. Additional endpoint called
00:30:24.375 --> 00:30:27.105 custom endpoint called there making OK.
00:30:27.110 --> 00:30:31.086 And yeah this this was all UM.
00:30:31.090 --> 00:30:32.730 This is all of that.
00:30:32.730 --> 00:30:36.498 And I have arcs one up over here.
00:30:36.500 --> 00:30:39.993 UM, thing is there's is done a
00:30:39.993 --> 00:30:42.237 little bit differently because
00:30:42.237 --> 00:30:45.457 they're fully using this medical.
00:30:45.460 --> 00:30:49.868 Question uhm? Module.
00:30:49.868 --> 00:30:54.738 And it's got, uhm? You know so.
00:30:54.738 --> 00:30:57.910 So basically, uhm, he typed in.
00:30:57.910 --> 00:31:00.150 The question and the
00:31:00.150 --> 00:31:02.948 answer into each of these.
00:31:02.950 --> 00:31:07.640 And here, in and specify which type.
00:31:07.640 --> 00:31:09.626 Yeah, and uh, what is these?
00:31:09.630 --> 00:31:11.290 Uh, but the submit button.
00:31:11.290 --> 00:31:13.910 So if you go down, what is this?
00:31:13.910 --> 00:31:15.830 What is the action of submit
00:31:15.830 --> 00:31:17.270 button is calling, yeah.
00:31:24.460 --> 00:31:26.595 Uh, it doesn't look like there is
00:31:26.595 --> 00:31:28.628 a submit button attached to this.
00:31:28.630 --> 00:31:31.996 Oh wait, no, there is a.
00:31:32.000 --> 00:31:33.770 Well, so let's add medication.
00:31:33.770 --> 00:31:35.078 Yeah, that's different.
00:31:35.078 --> 00:31:39.480 I think that's it might be a different step.
00:31:39.480 --> 00:31:44.591 Yeah. Uhm? Yeah,
00:31:44.591 --> 00:31:49.008 here's where the question or body is.
00:31:49.010 --> 00:31:51.714 Here submit button submit
00:31:51.714 --> 00:31:54.418 registration controller submit steps.
00:31:59.680 --> 00:32:03.820 OK, and then so they're probably, uh.
00:32:03.820 --> 00:32:07.770 Collecting all this data first.
00:32:07.770 --> 00:32:10.524 And then doing a one whole
00:32:10.524 --> 00:32:12.360 submission on the submit.
00:32:12.360 --> 00:32:19.150 Uh-huh uhm. The CA.
00:32:19.150 --> 00:32:21.745 Shoot, I forgot where it's at, oh?
00:32:21.745 --> 00:32:23.820 Within the body type script,
00:32:23.820 --> 00:32:26.536 can you pull it up real quick?
00:32:26.540 --> 00:32:29.487 Yeah, on SSPR on here on here.
00:32:31.940 --> 00:32:34.289 Of submit Boyd.
00:32:38.460 --> 00:32:40.556 OK, well this doesn't
00:32:40.556 --> 00:32:43.176 look like it's built out.
00:32:43.180 --> 00:32:45.276 This submits comma town.
00:32:45.276 --> 00:32:49.110 Yeah, so uh, it's David available.
00:32:49.110 --> 00:32:50.580 I think he's out today.
00:32:50.580 --> 00:32:52.930 He's out today. Crap, oh.
00:33:01.210 --> 00:33:03.274 Try thank you. Uhm,
00:33:03.274 --> 00:33:06.370 body dot HTML for me please.
00:33:11.670 --> 00:33:14.398 In here. Yeah, uhm,
00:33:14.398 --> 00:33:17.126 this is our exponent.
00:33:17.130 --> 00:33:19.428 Yeah, oh it wasn't on here.
00:33:19.430 --> 00:33:21.350 I was on the view.
00:33:21.350 --> 00:33:23.246 I wanted to look at that
00:33:23.246 --> 00:33:24.510 submit again and that's
00:33:24.577 --> 00:33:25.959 registration control,
00:33:25.960 --> 00:33:27.109 DOT submit and.
00:33:29.160 --> 00:33:30.660 We look at somebody,
00:33:30.660 --> 00:33:32.910 so that's going to be somewhere.
00:33:32.910 --> 00:33:35.958 ALS yeah we have submit there.
00:33:35.960 --> 00:33:38.510 Yeah, that's protected right there.
00:33:41.600 --> 00:33:43.030 What does protected mean again?
00:33:45.050 --> 00:33:48.018 Maybe it can only be called by
00:33:48.018 --> 00:33:50.139 this controller? I'm actually OK,
00:33:50.139 --> 00:33:54.630 cool we got Patrick here. So dumb.
00:33:54.630 --> 00:33:59.230 The the. The way this step works
00:33:59.230 --> 00:34:02.275 is whenever you hit the submit
00:34:02.275 --> 00:34:05.159 on the registration controller,
00:34:05.160 --> 00:34:08.960 it calls the steps submit.
00:34:08.960 --> 00:34:11.056 See how online #30.
00:34:11.056 --> 00:34:12.628 Yeah submit step.
00:34:12.630 --> 00:34:15.288 So then then it submits it.
00:34:15.290 --> 00:34:17.942 So this step is the body
00:34:17.942 --> 00:34:19.268 that typescripts submit.
00:34:21.590 --> 00:34:24.054 So it basically just pass it all
00:34:24.054 --> 00:34:26.822 along the chain, so there is modules
00:34:26.822 --> 00:34:28.962 within the form within steps.
00:34:28.970 --> 00:34:33.092 Uh-huh so then for every step there's a form.
00:34:33.100 --> 00:34:35.266 And everything within the form there
00:34:35.266 --> 00:34:38.030 is a module for the questionnaire.
00:34:38.030 --> 00:34:40.496 Whenever they hit the submit step,
00:34:40.500 --> 00:34:43.740 it takes it from the module to the
00:34:43.740 --> 00:34:47.067 form to the step in a submit all.
00:34:47.070 --> 00:34:50.016 Basically collecting from lowest to highest
00:34:50.016 --> 00:34:52.690 upwards and shoving across the wire.
00:34:52.690 --> 00:34:55.970 OK, now. Uhm?
00:34:59.020 --> 00:35:02.580 Can we search in here to see if
00:35:02.580 --> 00:35:05.860 that create user API as many used?
00:35:05.860 --> 00:35:10.140 In RX one? Yeah, uhm.
00:35:10.140 --> 00:35:14.280 Do you mean a createuser answer? Correct?
00:35:22.950 --> 00:35:30.220 And by the way, I worked with Brandon on SSP.
00:35:30.220 --> 00:35:33.668 On this thing and I can't remember why,
00:35:33.670 --> 00:35:36.926 but I think he said that this one
00:35:36.926 --> 00:35:39.989 had to be done this way instead
00:35:39.989 --> 00:35:43.149 of the way RX one was done,
00:35:43.150 --> 00:35:46.705 where you know how RX one has all the
00:35:46.705 --> 00:35:49.606 answers and the type of since each
00:35:49.606 --> 00:35:52.629 question can have a different type.
00:35:52.630 --> 00:35:54.946 So this one's checkbox,
00:35:54.946 --> 00:35:58.420 other or radio and other text.
00:35:58.420 --> 00:36:03.316 But he said that SSB had to be done
00:36:03.316 --> 00:36:06.196 differently so that every field
00:36:06.196 --> 00:36:10.919 essentially had to be just a text input.
00:36:10.920 --> 00:36:15.600 Uhm, and I don't know why that was.
00:36:15.600 --> 00:36:18.379 But that that was the way that
00:36:18.379 --> 00:36:20.989 he built it out like this.
00:36:20.990 --> 00:36:26.638 Is SSPS question only gonna be text based?
00:36:26.640 --> 00:36:28.668 No, actually the questions
00:36:28.668 --> 00:36:30.696 that they sent over.
00:36:30.700 --> 00:36:34.918 Uh, here, let me show you.
00:36:34.920 --> 00:36:36.968 Here are the questions that they sent over.
00:36:43.090 --> 00:36:45.020 Actually, look at this note.
00:36:45.020 --> 00:36:47.336 Questions 2 through 7 based on
00:36:47.336 --> 00:36:48.880 selective response question one.
00:36:55.940 --> 00:37:00.780 So basically if you answer.
00:37:00.780 --> 00:37:06.996 B. Then you're only shown to.
00:37:07.000 --> 00:37:09.690 In three, if you answers,
00:37:09.690 --> 00:37:12.380 you know how many doses.
00:37:12.380 --> 00:37:16.676 If you answer 2, then you're shown 2345.
00:37:16.680 --> 00:37:18.624 If you answer 32345.
00:37:18.624 --> 00:37:21.054 6-7 if you enter zero,
00:37:21.060 --> 00:37:23.867 then I guess you just skipped 2.
00:37:23.870 --> 00:37:27.934 8. Have a right, OK,
00:37:27.934 --> 00:37:30.214 so let's just deform logic.
00:37:30.220 --> 00:37:31.291 Yeah, it's fine.
00:37:31.291 --> 00:37:33.790 We can put that in there to
00:37:33.875 --> 00:37:36.111 display different radio button
00:37:36.111 --> 00:37:38.906 based on the previous election.
00:37:38.910 --> 00:37:41.190 So that will be OK.
00:37:41.190 --> 00:37:43.896 OK, OK, can we look at
00:37:43.896 --> 00:37:46.220 this search result in RX1?
00:37:48.240 --> 00:37:50.128 And I'm not sure I know how to
00:37:50.128 --> 00:37:52.103 answer this, 'cause you don't.
00:37:52.103 --> 00:37:56.208 I guess we'll have to ask Brandon why
00:37:56.208 --> 00:37:59.710 he wants you doing text format. Uhm?
00:38:01.970 --> 00:38:06.810 OK, so there's no source results here. No.
00:38:06.810 --> 00:38:10.626 Please see that was in CV API contacts.
00:38:10.630 --> 00:38:13.976 I can look that up in here.
00:38:21.380 --> 00:38:23.735 It's there's nothing for answering
00:38:23.735 --> 00:38:25.629 here, nothing for questions.
00:38:32.430 --> 00:38:35.810 Have is that endpoint exists?
00:38:35.810 --> 00:38:40.796 'cause if it feels like that
00:38:40.796 --> 00:38:43.289 endpoint shouldn't exist.
00:38:43.290 --> 00:38:45.730 I don't know how to check if the
00:38:45.730 --> 00:38:47.839 input exists on the back and come.
00:38:50.550 --> 00:38:53.709 But it's it's yeah it's saying 404 not found.
00:38:53.710 --> 00:38:56.158 So essentially that endpoint doesn't exist
00:38:56.158 --> 00:38:59.401 here and it doesn't look like we have
00:38:59.401 --> 00:39:03.420 a functional working example. For it oh
00:39:06.100 --> 00:39:08.300 have come.
00:39:10.400 --> 00:39:13.264 Let me let me see you real quick.
00:39:13.270 --> 00:39:16.500 This is a little bit of my room, UM?
00:39:20.880 --> 00:39:22.698 Do do do do do do.
00:40:04.370 --> 00:40:05.378 Trying to fire.
00:40:10.380 --> 00:40:14.125 Hey guys. Hi, sorry to see you.
00:40:14.130 --> 00:40:15.910 Hey what's up? Hey,
00:40:15.910 --> 00:40:19.629 it's pretty sorry for calling I love blue
00:40:19.629 --> 00:40:23.469 here from Danny's share his screen right now.
00:40:23.470 --> 00:40:26.266 He's trying to work on SV.
00:40:26.270 --> 00:40:29.366 My guess he copied some of the stuff
00:40:29.366 --> 00:40:32.808 from RX1 for the medical questionnaire.
00:40:32.810 --> 00:40:35.967 Yeah, did he still have the stuff
00:40:35.967 --> 00:40:38.877 that that we worked on? Brandon.
00:40:38.877 --> 00:40:41.679 Yeah, but basically that this create
00:40:41.679 --> 00:40:44.814 user answer it. It's trying to.
00:40:44.814 --> 00:40:48.282 Do this post request to contacts
00:40:48.282 --> 00:40:51.476 user answer create and it some
00:40:51.476 --> 00:40:55.189 getting a 404 on the front end.
00:40:55.190 --> 00:40:58.574 OK, uh, when's the last time you pulled?
00:40:58.580 --> 00:41:00.278 Uhm? Pretty recently,
00:41:00.278 --> 00:41:02.542 actually this morning 'cause
00:41:02.542 --> 00:41:06.563 this was a I made a copy of the
00:41:06.563 --> 00:41:09.368 branch that you and I had worked
00:41:09.368 --> 00:41:12.224 on and then I pulled into that.
00:41:12.230 --> 00:41:14.638 Uhm, so this is that this has
00:41:14.638 --> 00:41:16.300 everything from this morning.
00:41:18.410 --> 00:41:21.330 OK, let me go see 'cause Brandon Lyon
00:41:21.330 --> 00:41:23.749 actually did this Friday afternoon.
00:41:23.750 --> 00:41:27.480 So let me go check and see here what I
00:41:27.582 --> 00:41:30.505 pulled. CR Branch was called Medical
00:41:30.505 --> 00:41:33.174 Questionnaire so I created 10 and
00:41:33.174 --> 00:41:35.666 I forgot to put message in there.
00:41:35.670 --> 00:41:39.580 Did you pull from QA? Yeah OK.
00:41:39.580 --> 00:41:42.466 Did you build in Visual Studio?
00:41:42.470 --> 00:41:45.378 Yeah. I I rebuilt.
00:41:49.010 --> 00:41:52.070 Just make sure that.
00:41:52.070 --> 00:41:54.254 Maybe later 30. Yeah, it looks
00:41:54.254 --> 00:41:56.829 like it's not been completed yet,
00:41:56.830 --> 00:41:58.820 so let's see what's active.
00:41:58.820 --> 00:42:02.258 Let me see if he's actually out on a
00:42:02.258 --> 00:42:05.968 call with him, so let me hop over there.
00:42:05.970 --> 00:42:07.950 I'll be right back, OK?
00:42:10.490 --> 00:42:17.920 Wonder how we can check? You know? Uh.
00:42:17.920 --> 00:42:19.820 It's something that's not completed.
00:42:22.690 --> 00:42:23.830 It's like an easy way to.
00:42:30.260 --> 00:42:32.430 Wait, I'm sorry, check what.
00:42:32.430 --> 00:42:35.825 How to check if if like an
00:42:35.825 --> 00:42:38.549 endpoint is not create OK?
00:42:38.550 --> 00:42:40.842 Hey Danny, did Brendan
00:42:40.842 --> 00:42:44.280 Lyons send you a message on?
00:42:44.280 --> 00:42:48.498 Friday Uhm let me see.
00:43:02.240 --> 00:43:04.256 Not directly would it have been
00:43:04.256 --> 00:43:06.955 in the sea, and then it would have
00:43:06.955 --> 00:43:09.320 been to you and David, he said.
00:43:12.190 --> 00:43:13.020 I see.
00:43:21.160 --> 00:43:22.756 Essentially he hasn't PR it yet.
00:43:22.760 --> 00:43:24.350 He's still testing it right now.
00:43:24.350 --> 00:43:26.205 He's going to make the PR soon.
00:43:56.130 --> 00:44:00.127 So the link hasn't been created yet.
00:44:00.130 --> 00:44:04.080 I don't see a a chat between him and a
00:44:04.186 --> 00:44:08.443 David and I hear it just hurts him there.
00:44:08.450 --> 00:44:12.804 He may have forgotten I guess too.
00:44:12.810 --> 00:44:15.594 OK, send it to you but but but
00:44:15.594 --> 00:44:17.536 essentially he hasn't PRT yet
00:44:17.536 --> 00:44:20.245 'cause he's still testing it so OK.
00:44:22.500 --> 00:44:24.836 OK, you don't have to worry about the.
00:44:24.840 --> 00:44:27.010 You don't have to worry about them
00:44:27.010 --> 00:44:30.620 actually saving yet to the back end, OK?
00:44:30.620 --> 00:44:33.152 I just wanted to to test
00:44:33.152 --> 00:44:35.220 that before we moved on.
00:44:35.220 --> 00:44:38.770 While I've got you, Brandon, come.
00:44:38.770 --> 00:44:43.210 Question about the UM slider.
00:44:43.210 --> 00:44:46.108 The way that this was, uhm, working.
00:44:46.108 --> 00:44:48.971 While it's still kind of in list
00:44:48.971 --> 00:44:53.030 form like this, is it each input?
00:44:53.030 --> 00:44:55.370 Is filling in the same will?
00:44:55.370 --> 00:44:57.710 That will the slider fix that?
00:44:59.840 --> 00:45:01.968 Uh, yeah, because you would only be
00:45:01.968 --> 00:45:04.278 doing one at a time and that yeah,
00:45:04.280 --> 00:45:05.760 that's the whole reason why
00:45:05.760 --> 00:45:07.240 I suggested doing a slider.
00:45:07.240 --> 00:45:09.643 A front end or might have a better way
00:45:09.643 --> 00:45:12.266 of like you could list them like this.
00:45:12.270 --> 00:45:14.622 The problem is what you're seeing
00:45:14.622 --> 00:45:17.489 now where you'd have to bind each one
00:45:17.489 --> 00:45:20.050 of these input boxes to a question.
00:45:20.050 --> 00:45:22.498 But if we do it as a slider,
00:45:22.500 --> 00:45:24.798 what will happen is that call
00:45:24.798 --> 00:45:26.810 will be made every time.
00:45:26.810 --> 00:45:29.573 And so, like the engine model for you know,
00:45:29.580 --> 00:45:31.120 test or whatever you know,
00:45:31.120 --> 00:45:33.883 whatever you put in there when you hit next,
00:45:33.890 --> 00:45:34.979 it'll that back.
00:45:34.979 --> 00:45:37.975 End call will be made and it'll save
00:45:37.975 --> 00:45:40.243 that question to that answer and
00:45:40.243 --> 00:45:43.118 then it will go on to the next one.
00:45:43.120 --> 00:45:44.020 Right, OK?
00:45:46.380 --> 00:45:50.983 Uhm? But yeah, I mean if we want to list
00:45:50.983 --> 00:45:52.569 them like this, that's obviously fine.
00:45:52.569 --> 00:45:54.650 It just it. It does have to be an
00:45:54.650 --> 00:45:56.678 input box and then it would just each.
00:45:56.680 --> 00:45:58.633 Each answer would have to somehow be
00:45:58.633 --> 00:46:00.866 bound to a specific question and I am
00:46:00.866 --> 00:46:03.936 not sure how to do that. OK yeah, I uhm.
00:46:03.936 --> 00:46:06.390 I'm sure we could figure that out,
00:46:06.390 --> 00:46:09.736 but I I actually think the slider.
00:46:09.740 --> 00:46:13.625 Maybe? Better just from, you know, uh?
00:46:13.625 --> 00:46:16.050 User experience, yeah for sure.
00:46:16.050 --> 00:46:16.736 Yeah, uhm.
00:46:16.736 --> 00:46:19.480 I did ask Casey about the slider and
00:46:19.554 --> 00:46:21.888 I haven't gotten a response yet,
00:46:21.890 --> 00:46:24.810 so I'll follow up with him on that.
00:46:28.730 --> 00:46:33.336 But OK, so we can work on.
00:46:33.340 --> 00:46:36.014 Well I guess let me let me see if I can
00:46:36.014 --> 00:46:38.525 get an answer from him and if he says.
00:46:38.530 --> 00:46:42.467 Go, then we can work on the slider if not and
00:46:42.467 --> 00:46:46.270 off to wait on that and wait on Brandon Lyon.
00:46:46.270 --> 00:46:47.512 I honestly I think you're good
00:46:47.512 --> 00:46:48.999 to at least work on the slider.
00:46:49.000 --> 00:46:51.296 I don't know if anybody here has
00:46:51.296 --> 00:46:53.119 done anything like that before.
00:46:53.120 --> 00:46:56.430 OK, but uh yeah, I would just work on that.
00:46:56.430 --> 00:46:59.310 And and, uh.
00:46:59.310 --> 00:47:02.320 Yeah, I think they they won't care.
00:47:02.320 --> 00:47:05.770 I found an example of something.
00:47:05.770 --> 00:47:09.566 And I asked David to take a look at it to
00:47:09.566 --> 00:47:12.942 see if it's something that would work in.
00:47:12.950 --> 00:47:15.536 This cell registration stuff and stuff.
00:47:15.540 --> 00:47:19.008 And he said that it would.
00:47:19.010 --> 00:47:20.438 There's something like this.
00:47:22.800 --> 00:47:27.838 Yeah. So. OK cool awesome.
00:47:33.080 --> 00:47:33.554 Alright Brandon,
00:47:33.554 --> 00:47:34.976 well thank you for your help.
00:47:34.980 --> 00:47:36.170 Oh yeah no problem man.
00:47:36.170 --> 00:47:38.456 I'll talk to you guys later.
00:47:38.460 --> 00:47:40.868 OK, thank you bye.
00:47:46.530 --> 00:47:47.960 OK, so.
00:47:51.050 --> 00:47:54.300 Let me ask him quick.
00:47:54.300 --> 00:47:56.340 Does anybody else have anything
00:47:56.340 --> 00:47:58.680 that they wanted to work on?
00:48:06.610 --> 00:48:10.304 No, I'm good. OK, uhm you guys
00:48:10.304 --> 00:48:13.883 just want to hang out for a minute
00:48:13.883 --> 00:48:16.739 while I ask Casey about this.
00:48:16.740 --> 00:48:19.436 Yeah, you better try to build the slider.
00:48:19.440 --> 00:48:26.030 Yeah. Yeah, I just wanted to see if, uh.
00:48:26.030 --> 00:48:29.210 The client. I mean, I can't imagine.
00:48:32.910 --> 00:48:35.808 Uh, I'm gonna ask him, but I I can't
00:48:35.808 --> 00:48:38.259 imagine that they would like be upset
00:48:38.259 --> 00:48:41.019 about it and demand that we list all
00:48:41.019 --> 00:48:43.620 the questions out this way. You know?
00:48:45.940 --> 00:48:47.980 It seems like the better way
00:48:47.980 --> 00:48:49.909 to do it. With the slider.
00:48:52.470 --> 00:48:53.079 Let me sing.
00:49:25.000 --> 00:49:25.460 OK.
00:49:30.300 --> 00:49:31.885 And let me put something
00:49:31.885 --> 00:49:33.470 back 'cause I took out.
00:49:42.510 --> 00:49:44.951 I see in the name for the input, thinking
00:49:44.951 --> 00:49:47.119 that that might be causing a thing here,
00:49:47.120 --> 00:49:49.559 but that's not what it was. It was the.
00:49:55.890 --> 00:49:56.889 Who is this?
00:49:59.620 --> 00:50:04.366 Finding the input too. This answer variable.
00:50:08.360 --> 00:50:10.754 On the body controller and so
00:50:10.754 --> 00:50:13.040 when it displayed each of them,
00:50:13.040 --> 00:50:16.407 it was just finding it the same.
00:50:16.410 --> 00:50:18.986 Thing over and over again 10 times.
00:50:22.410 --> 00:50:28.408 Uhm? Yeah, that's on the slider that you.
00:50:28.410 --> 00:50:31.732 Show da phone. Probably won't.
00:50:31.732 --> 00:50:33.037 Will there be a previous?
00:50:33.040 --> 00:50:35.128 I guess we could probably leave in a
00:50:35.128 --> 00:50:36.430 previous, although that will start.
00:50:40.450 --> 00:50:45.090 A previous thumb button, yeah?
00:50:45.090 --> 00:50:48.048 Yeah, I guess that could work.
00:50:48.050 --> 00:50:50.000 Well, let's think about this for
00:50:50.000 --> 00:50:51.950 a minute. I'm just here some.
00:50:55.330 --> 00:50:58.502 Does. There's a question count.
00:50:58.502 --> 00:51:00.230 Step up every time or doesn't
00:51:00.292 --> 00:51:04.640 know what question, moron. Uhm?
00:51:08.870 --> 00:51:13.670 Yeah, it's some it's iterating through.
00:51:13.670 --> 00:51:19.890 The questions in the database.
00:51:19.890 --> 00:51:23.340 Uhm, and so this is rich,
00:51:23.340 --> 00:51:27.560 not body control questions questions.
00:51:27.560 --> 00:51:30.290 And it's loading the questions.
00:51:30.290 --> 00:51:32.778 From here, so when it loads this controller
00:51:32.778 --> 00:51:35.416 it gets the questions from the database.
00:51:35.420 --> 00:51:36.788 It doesn't say anything
00:51:36.788 --> 00:51:38.498 about the order or anything,
00:51:38.500 --> 00:51:43.387 but I've seen it should have the question ID.
00:51:43.390 --> 00:51:45.758 Yeah, we should be good and if not
00:51:45.758 --> 00:51:48.198 then it should be something. Yeah.
00:51:48.198 --> 00:51:51.062 Oh yeah, if it's yeah it will have
00:51:51.062 --> 00:51:53.618 the question ID because it it.
00:51:53.620 --> 00:51:55.320 It, UM, takes the data.
00:51:55.320 --> 00:51:57.020 It gets back from this.
00:51:57.020 --> 00:51:58.950 Get questions.
00:51:58.950 --> 00:52:00.858 And that is.
00:52:03.850 --> 00:52:06.755 Doesn't say it, but I I assume
00:52:06.755 --> 00:52:09.939 it's all the data in this table,
00:52:09.940 --> 00:52:12.120 so it's got the ID.
00:52:12.120 --> 00:52:14.730 The question all this stuff too,
00:52:14.730 --> 00:52:18.510 which is which we don't need.
00:52:18.510 --> 00:52:21.849 So it's like an array of objects.
00:52:21.850 --> 00:52:25.288 Yeah, I think I think we should be good.
00:52:25.290 --> 00:52:28.278 OK. We're still figuring out this
00:52:28.278 --> 00:52:30.744 angular stuff, so bear with me.
00:52:30.744 --> 00:52:35.790 Dude, I'm the same I'm I was actually a.
00:52:35.790 --> 00:52:37.386 I don't know, I'm I'm happy we
00:52:37.386 --> 00:52:38.937 got to jump up on here and.
00:52:38.940 --> 00:52:41.588 I feel like it's a good learning experience.
00:52:41.590 --> 00:52:43.678 Yeah, every time we, you know,
00:52:43.680 --> 00:52:45.430 look at a different problem.
00:52:45.430 --> 00:52:46.822 It's a good one,
00:52:46.822 --> 00:52:47.786 OK, Kevin said,
00:52:47.786 --> 00:52:49.942 let's relate this to KK and ensure
00:52:49.942 --> 00:52:52.430 we should go this route trying to
00:52:52.430 --> 00:52:54.850 get more communication in teams channels.
00:52:54.850 --> 00:52:58.819 So if I am out sick like last Friday.
00:52:58.820 --> 00:53:00.746 What can still move forward OK?
00:53:04.040 --> 00:53:07.260 Oh Patrick, just a.
00:53:07.260 --> 00:53:09.300 Oh, this is, uh, Kendall.
00:53:09.300 --> 00:53:12.339 Kendall has one.
00:53:12.340 --> 00:53:14.573 Yeah, it's a I don't know if
00:53:14.573 --> 00:53:16.687 there's something you guys want to use.
00:53:16.690 --> 00:53:19.178 If you look at the front of UI,
00:53:19.180 --> 00:53:21.140 it's pretty well built out and then
00:53:21.140 --> 00:53:23.623 you can do like next back before and
00:53:23.623 --> 00:53:25.598 there's a couple API's and attached
00:53:25.598 --> 00:53:27.887 to it so you can prevent previews.
00:53:27.890 --> 00:53:28.766 Only next steps,
00:53:28.766 --> 00:53:31.310 and then if you click the view source,
00:53:31.310 --> 00:53:33.176 the step is pretty easy done.
00:53:33.180 --> 00:53:35.108 If you Scroll down,
00:53:35.108 --> 00:53:37.518 it's basically just a Jason.
00:53:37.520 --> 00:53:40.016 You need to implement this like
00:53:40.016 --> 00:53:41.680 without going through like.
00:53:41.680 --> 00:53:43.724 Course if it's not attached to it,
00:53:43.730 --> 00:53:46.936 we just include the jQuery power and
00:53:46.936 --> 00:53:49.128 interest using JavaScript to run it.
00:53:49.130 --> 00:53:50.894 So you see, this equals X tabs
00:53:50.894 --> 00:53:52.730 and each of them has a title.
00:53:52.730 --> 00:53:53.498 There's a button,
00:53:53.498 --> 00:53:55.034 next form and stuff like that.
00:53:55.040 --> 00:53:57.830 It builds out for you.
00:53:57.830 --> 00:54:00.854 I don't know what the results is going
00:54:00.854 --> 00:54:04.700 to look like, but I hope I'm thinking.
00:54:04.700 --> 00:54:07.290 If you do something similar.
00:54:07.290 --> 00:54:09.670 And in.
00:54:09.670 --> 00:54:12.160 You should be able to.
00:54:12.160 --> 00:54:14.224 Manipulate the data after the user
00:54:14.224 --> 00:54:16.480 goes through the step and then we
00:54:16.480 --> 00:54:18.370 could do like energy if space on
00:54:18.441 --> 00:54:20.465 certain fields and stuff, yeah?
00:54:20.465 --> 00:54:22.890 Like we wouldn't need this
00:54:22.890 --> 00:54:25.540 'cause this is payment editor.
00:54:25.540 --> 00:54:31.318 Correct Craggs UM and if we need to load.
00:54:31.320 --> 00:54:33.889 Come on the left insiders like low
00:54:33.889 --> 00:54:36.898 content with Ajax so we can do that as well.
00:54:36.900 --> 00:54:37.881 If there's a.
00:54:37.881 --> 00:54:39.843 If we're looking for SFN pointed,
00:54:39.850 --> 00:54:41.998 have different questions.
00:54:41.998 --> 00:54:44.146 We got 2.
00:54:44.150 --> 00:54:44.611 OK.
00:54:44.611 --> 00:54:46.455 Looks like there's like
00:54:46.455 --> 00:54:48.760 event attachment as well so.
00:54:52.000 --> 00:54:56.480 Content on air reset on some wives.
00:54:56.480 --> 00:54:59.392 OK, yeah, so there's a bunch of like
00:54:59.392 --> 00:55:02.015 lifecycle stuff for this form that we can.
00:55:02.020 --> 00:55:05.470 Uhm, do and it looks like you also do like
00:55:05.552 --> 00:55:08.919 if you click the keyboard navigation tab.
00:55:08.920 --> 00:55:11.458 Looks like you also turn this
00:55:11.458 --> 00:55:13.950 form to a vertical style 2.
00:55:13.950 --> 00:55:17.734 Oh, that is cool yeah, so if yeah,
00:55:17.734 --> 00:55:19.886 so that's pretty neat.
00:55:19.890 --> 00:55:23.720 Yeah, yeah, so if the.
00:55:23.720 --> 00:55:26.690 Uhm? Which we call it.
00:55:26.690 --> 00:55:27.846 Sorry, losing my track here.
00:55:27.846 --> 00:55:30.251 If the size step is going to be too much
00:55:30.251 --> 00:55:33.330 space or tasteless space, we just do the.
00:55:33.330 --> 00:55:34.620 This one whatever.
00:55:34.620 --> 00:55:36.770 But I like this for,
00:55:36.770 --> 00:55:39.530 but the only problem with this
00:55:39.530 --> 00:55:42.972 is that the number of steps may
00:55:42.972 --> 00:55:45.978 change based on the first question.
00:55:45.980 --> 00:55:49.121 'cause like if they say uhm were you on
00:55:49.121 --> 00:55:52.388 here when we looked at the questions? Yeah,
00:55:52.388 --> 00:55:55.070 you can still poop it in a single section,
00:55:55.070 --> 00:55:58.050 so you can say step one will be question one.
00:55:58.050 --> 00:56:00.570 Step two will be 227. OK,
00:56:00.570 --> 00:56:03.990 and then step three will be 8:00 and 9:10.
00:56:03.990 --> 00:56:06.276 You know stuff like that, yeah?
00:56:06.276 --> 00:56:08.592 You could probably list them all
00:56:08.592 --> 00:56:11.087 and have like an GF on someone.
00:56:11.090 --> 00:56:14.950 Yeah yeah, yeah. OK.
00:56:14.950 --> 00:56:16.021 Wow, that's cool.
00:56:16.021 --> 00:56:18.163 I would like to do this.
00:56:18.170 --> 00:56:21.383 It seems like it would take a little longer,
00:56:21.390 --> 00:56:23.010 but.
00:56:23.010 --> 00:56:25.878 Yeah, and then we can write
00:56:25.878 --> 00:56:28.370 our custom template to come.
00:56:28.370 --> 00:56:30.146 The thing with the Kindle is
00:56:30.146 --> 00:56:32.070 that we can't write our custom.
00:56:32.070 --> 00:56:34.205 Attributes and then we can pass it
00:56:34.205 --> 00:56:36.431 along and say hey based on question
00:56:36.431 --> 00:56:38.750 one we want to do different views.
00:56:38.750 --> 00:56:40.845 Different stuff like that and
00:56:40.845 --> 00:56:43.949 it will take care of that stuff.
00:56:43.950 --> 00:56:44.440 OK.
00:56:47.940 --> 00:56:50.380 But I don't know if.
00:56:50.380 --> 00:56:52.487 We have kinda Lori attached to angular.
00:56:52.490 --> 00:56:53.698 I mean two Seth.
00:56:53.698 --> 00:56:55.875 Uhm, there's a potential we might
00:56:55.875 --> 00:56:58.142 already have that in there somewhere
00:56:58.142 --> 00:57:00.403 in the code that we can use.
00:57:00.410 --> 00:57:02.060 Or maybe it's always somewhere else,
00:57:02.060 --> 00:57:02.580 something similar,
00:57:02.580 --> 00:57:04.140 but this is just kind of
00:57:04.140 --> 00:57:05.360 food for thought deal.
00:57:08.850 --> 00:57:12.386 Oh uhm, there's just a response on this,
00:57:12.390 --> 00:57:16.536 it says. Uhm, I could see it working,
00:57:16.540 --> 00:57:19.447 but I think we need to preserve the ability
00:57:19.447 --> 00:57:22.062 to answer some, but not all questions.
00:57:22.062 --> 00:57:23.777 Some groups may be required
00:57:23.777 --> 00:57:25.738 if you answer question one,
00:57:25.740 --> 00:57:28.533 you may be forced to answer that yeah, yeah.
00:57:28.533 --> 00:57:31.251 Also, we need to be sure
00:57:31.251 --> 00:57:33.980 to provide a progressbar.
00:57:33.980 --> 00:57:37.540 OK, so I think.
00:57:37.540 --> 00:57:40.070 The ability to answer some.
00:57:43.520 --> 00:57:47.360 Would be. I mean, you could.
00:57:47.360 --> 00:57:49.550 You could basically say which
00:57:49.550 --> 00:57:52.170 fields are required on this and
00:57:52.170 --> 00:57:54.018 which are not, right, correct?
00:57:54.018 --> 00:57:56.846 So that question that answers that question
00:57:56.846 --> 00:57:59.375 and then the groups may be required.
00:57:59.380 --> 00:58:02.116 You know that's what we were
00:58:02.116 --> 00:58:04.846 just talking about. So I think.
00:58:04.846 --> 00:58:05.750 That's everything.
00:58:05.750 --> 00:58:08.280 The only question is can we put, uh,
00:58:08.280 --> 00:58:12.280 well, this is kind of a progress bar.
00:58:12.280 --> 00:58:15.220 Let me show him this and see.
00:58:23.600 --> 00:58:26.018 And we can we could dynamically
00:58:26.018 --> 00:58:28.384 update the steps to like if
00:58:28.384 --> 00:58:30.400 there is going to be like.
00:58:30.400 --> 00:58:32.288 If the client wants like hey I want
00:58:32.288 --> 00:58:34.208 all these questions to be having
00:58:34.208 --> 00:58:36.320 individual steps, we could do that too.
00:58:36.320 --> 00:58:38.763 It's fine, which is colleague which is
00:58:38.763 --> 00:58:41.090 attached to this cycle of the graph.
00:58:41.090 --> 00:58:42.296 Just call refrescante.
00:58:42.296 --> 00:58:44.306 Someone entered the first question.
00:58:47.260 --> 00:58:49.628 Wait, say that again.
00:58:49.630 --> 00:58:52.718 Uh, if we need to create the functionality
00:58:52.718 --> 00:58:56.268 of like saying based on the first question,
00:58:56.270 --> 00:58:59.175 the different steps of the question changes,
00:58:59.180 --> 00:59:02.520 like how many steps?
00:59:02.520 --> 00:59:04.515 Oh, if the client wants that instead
00:59:04.515 --> 00:59:06.869 of like a grouping like step one,
00:59:06.870 --> 00:59:09.358 you know what you took and Step 2.
00:59:09.360 --> 00:59:11.628 All the other two to seven question
00:59:11.628 --> 00:59:14.119 right and then onwards if they want to
00:59:14.119 --> 00:59:16.861 say if a client wants hey I want each
00:59:16.861 --> 00:59:19.001 of these questions based on the first
00:59:19.001 --> 00:59:20.556 questions answer to update itself.
00:59:20.560 --> 00:59:22.110 We can do that too.
00:59:22.110 --> 00:59:23.862 It just look more.
00:59:23.862 --> 00:59:26.560 Work, but it's possible. OK.
01:00:39.150 --> 01:00:40.560 OK, I'll be right back guys.
01:02:53.080 --> 01:02:54.858 OK, I'm back. Can you hear me?
01:02:57.240 --> 01:03:05.780 Yep. OK. Switched my earbuds OK, uhm.
01:03:05.780 --> 01:03:08.788 Kevin gave the thumbs up so it looks
01:03:08.788 --> 01:03:11.547 like we're good to go with this so.
01:03:11.550 --> 01:03:13.530 Let's figure this out.
01:03:16.560 --> 01:03:19.028 Patrick, are you there?
01:03:19.030 --> 01:03:21.660 Yes, Sir, so does all.
01:03:21.660 --> 01:03:28.356 This is all this already loaded up in SEV.
01:03:28.360 --> 01:03:33.080 Uhm, I know and check clearing don't know.
01:03:33.080 --> 01:03:37.540 OK. Uhm, but we can test.
01:03:37.540 --> 01:03:40.948 Just copy everything in the body
01:03:40.948 --> 01:03:45.110 section and put it in the form. OK.
01:03:57.470 --> 01:03:59.166 Let's see, there's medical
01:03:59.166 --> 01:04:00.850 questionnaire. I'm just gonna.
01:04:05.250 --> 01:04:05.640 Mid
01:04:08.840 --> 01:04:10.592 uh, that won't work because you
01:04:10.592 --> 01:04:12.780 have a comment on 15 already, yeah?
01:04:26.000 --> 01:04:27.890 OK, let's see what this looks like.
01:04:35.490 --> 01:04:37.380 By the way, it's starting to storm
01:04:37.380 --> 01:04:40.470 over here, so. If I suddenly disappear,
01:04:40.470 --> 01:04:43.550 I'll come back as quickly as I can.
01:04:45.570 --> 01:04:47.230 What you disappear? No.
01:04:49.850 --> 01:04:51.836 Into thin air. Like a magician?
01:04:51.840 --> 01:04:54.496 Yeah, sort of like back to the future.
01:04:57.430 --> 01:04:59.690 You know when his, uh?
01:04:59.690 --> 01:05:03.440 When he starts to disappear because.
01:05:03.440 --> 01:05:06.826 In the past. You know you guys
01:05:06.826 --> 01:05:08.500 have seen back to the future.
01:05:08.500 --> 01:05:09.612 Good God it's loud,
01:05:09.612 --> 01:05:10.724 like really storming over.
01:05:10.730 --> 01:05:12.130 No, I can hear you.
01:05:12.130 --> 01:05:14.076 I hear that thundering yeah yeah wow.
01:05:14.080 --> 01:05:16.304 At first I thought it was just hungry.
01:05:16.310 --> 01:05:19.430 I was like David.
01:05:19.430 --> 01:05:22.226 Why I'm surprised to hear that.
01:05:22.230 --> 01:05:23.928 Yeah it is. It is storming.
01:05:23.930 --> 01:05:25.758 It's thundering right now,
01:05:25.758 --> 01:05:29.010 so it's getting rid of your rain.
01:05:29.010 --> 01:05:29.401 Actually,
01:05:29.401 --> 01:05:31.747 like I find it very relaxing.
01:05:31.750 --> 01:05:34.798 I do too.
01:05:34.800 --> 01:05:36.636 Thank you to actually like it.
01:05:43.410 --> 01:05:50.040 Yes, here that. Yes Sir, wow. That's crazy.
01:05:50.040 --> 01:05:52.847 OK, this is bill. Let's try this.
01:05:56.670 --> 01:05:59.280 Hello I have been here.
01:06:02.320 --> 01:06:05.031 Close this stuff. Close
01:06:05.031 --> 01:06:07.377 this for now. Put my face.
01:06:12.870 --> 01:06:16.427 Can you fix color? By the way, see?
01:06:16.427 --> 01:06:18.716 UM, we were talking about last time.
01:06:18.720 --> 01:06:21.002 If you go into options down here
01:06:21.002 --> 01:06:23.004 maximum length, I think 15.
01:06:23.004 --> 01:06:26.620 Is short as you need it to be.
01:06:26.620 --> 01:06:29.336 For when you get to the at
01:06:29.336 --> 01:06:31.386 a billing address step and
01:06:31.386 --> 01:06:33.768 then when you fill that in.
01:06:33.770 --> 01:06:35.516 It only tells up to there,
01:06:35.520 --> 01:06:38.430 so you don't have to.
01:06:38.430 --> 01:06:41.920 You know saves you an extra 1 to 2 seconds.
01:06:44.260 --> 01:06:46.110 OK, nothing.
01:06:57.020 --> 01:06:59.078 7X active step.
01:07:03.360 --> 01:07:04.760 Yeah, step custom body.
01:07:04.760 --> 01:07:07.220 This is where it should be Roe.
01:07:09.810 --> 01:07:14.339 Uh, there it looks like it's there.
01:07:14.340 --> 01:07:17.300 Let's see, there's script.
01:07:17.300 --> 01:07:21.000 I included the script tag.
01:07:21.000 --> 01:07:22.535 Ah yes, you're supposed to
01:07:22.535 --> 01:07:24.386 include the script tag. Oh OK.
01:07:24.386 --> 01:07:27.130 Yep uhm. OK, so it looks like
01:07:27.130 --> 01:07:29.405 the Kindle slider is not.
01:07:29.410 --> 01:07:37.320 Uhm? On Saturday off. Uhm?
01:07:37.320 --> 01:07:38.648 Then maybe tonight, knowing
01:07:52.180 --> 01:07:54.360 getting confused by these windows,
01:07:54.360 --> 01:07:59.292 I wanted to come. Do this thing where I.
01:07:59.300 --> 01:08:05.439 Rename my workspace. And then, like.
01:08:07.850 --> 01:08:11.350 Rename it like SSB.
01:08:11.350 --> 01:08:16.558 And then if you go into your vscode.
01:08:16.560 --> 01:08:19.908 Settings and go to window title.
01:08:19.910 --> 01:08:23.110 You can change this instead of root path.
01:08:25.970 --> 01:08:28.805 Name I think it was yeah and see it
01:08:28.805 --> 01:08:31.809 can say just SSB that would make it
01:08:31.809 --> 01:08:35.066 quicker so you can see like if you've
01:08:35.066 --> 01:08:38.100 got multiple PS code Windows open it's
01:08:38.100 --> 01:08:43.420 like SSBCMARX one and so on. But, uh.
01:08:43.420 --> 01:08:48.358 But then the problem is, uh, this, uh?
01:08:50.680 --> 01:08:57.320 Is then in the. Folder here.
01:08:57.320 --> 01:08:59.444 And so get sees that and
01:08:59.444 --> 01:09:01.979 I tried to do that trick.
01:09:01.980 --> 01:09:05.076 Michael, you know that trick that KV had,
01:09:05.080 --> 01:09:07.762 UM, where were you make it
01:09:07.762 --> 01:09:10.180 assume unchanged by the index.
01:09:10.180 --> 01:09:12.608 But it didn't work.
01:09:12.608 --> 01:09:15.643 Because I guess this isn't.
01:09:15.650 --> 01:09:17.975 You know, added this isn't
01:09:17.975 --> 01:09:20.300 committed in the first place.
01:09:20.300 --> 01:09:22.268 So it's like you can't ignore.
01:09:22.270 --> 01:09:23.925 You can't assume something that's
01:09:23.925 --> 01:09:26.219 unchanged that isn't there to begin with,
01:09:26.220 --> 01:09:29.510 so I don't quite know what to do about that.
01:09:29.510 --> 01:09:31.568 I think there's gotta be a
01:09:31.568 --> 01:09:34.498 way to do that to make it so
01:09:34.498 --> 01:09:36.706 that the title bar just shows.
01:09:36.710 --> 01:09:38.894 You know the name of the workspace in
01:09:38.894 --> 01:09:41.408 that you can hide the workspace from get.
01:09:41.410 --> 01:09:43.475 If you move this outside of the
01:09:43.475 --> 01:09:44.939 folder then nothing loads in.
01:09:47.570 --> 01:09:51.010 Anyways, I'm getting off topic.
01:09:51.010 --> 01:09:52.809 It move it out. It's because the
01:09:52.809 --> 01:09:53.950 workspace references is broken.
01:09:53.950 --> 01:09:55.819 So yeah, actually open up the workspace.
01:09:55.820 --> 01:09:57.787 You can actually just change it one
01:09:57.787 --> 01:09:59.920 level up and they'll reference it.
01:09:59.920 --> 01:10:03.478 Yeah yeah, but.
01:10:03.480 --> 01:10:10.100 I gotta get some way, forget to. Ignore that.
01:10:10.100 --> 01:10:12.724 Or I just leave it in there and.
01:10:12.730 --> 01:10:14.400 Ignore it myself. Yeah no.
01:10:14.400 --> 01:10:16.640 I usually leave it in there and
01:10:16.640 --> 01:10:18.389 try to ignore it myself.
01:10:18.390 --> 01:10:20.890 Oh, you do that.
01:10:20.890 --> 01:10:22.724 Yeah, I need to make a change
01:10:22.724 --> 01:10:24.060 to it because I don't.
01:10:24.060 --> 01:10:26.220 I don't like that it's missing
01:10:26.220 --> 01:10:28.651 some of the folders or I like
01:10:28.651 --> 01:10:30.475 to hide some of the folders,
01:10:30.480 --> 01:10:33.184 so I'll make a change to the workspace,
01:10:33.190 --> 01:10:35.886 but I try not to commit it well.
01:10:35.890 --> 01:10:36.904 Do you change?
01:10:36.904 --> 01:10:39.270 You change the name of the workspace,
01:10:39.270 --> 01:10:41.798 no 'cause if you don't change the name
01:10:41.798 --> 01:10:44.680 of the workspace then you can do that.
01:10:44.680 --> 01:10:46.708 Assume unchanged thing and it won't.
01:10:49.090 --> 01:10:50.530 And then that will work.
01:10:50.530 --> 01:10:52.924 So Git will just ignore any
01:10:52.924 --> 01:10:55.800 changes you make to the workspace.
01:10:55.800 --> 01:10:57.490 So you can use that.
01:10:57.490 --> 01:10:59.922 Uhm, it's just if you change the name
01:10:59.922 --> 01:11:02.220 then it's a totally different file.
01:11:02.220 --> 01:11:05.139 Git doesn't have that file in the
01:11:05.139 --> 01:11:08.478 index and so. That won't work, but.
01:11:08.480 --> 01:11:14.900 Here this thing here KB. Like this?
01:11:14.900 --> 01:11:16.676 You just type in the path,
01:11:16.680 --> 01:11:17.644 so you type in.
01:11:17.644 --> 01:11:18.849 Here you know and like
01:11:18.849 --> 01:11:20.250 the workspace whatever.
01:11:24.120 --> 01:11:26.456 Yeah, it's pretty cool. That kind of thing.
01:11:29.250 --> 01:11:29.840 Anyways.
01:11:31.880 --> 01:11:36.959 Off topic. Uhm? Where were we?
01:11:39.000 --> 01:11:39.670 Uh.
01:11:44.440 --> 01:11:47.765 This the Kendall. Kindle is not showing.
01:11:57.430 --> 01:12:03.510 Uh, that's because Kendall is.
01:12:06.880 --> 01:12:09.060 OK. Uhm?
01:12:15.380 --> 01:12:18.290 Sorry, I'm trying to see where
01:12:18.290 --> 01:12:20.422 the freaking. Is Kendall.
01:12:20.422 --> 01:12:23.908 I think this version Candela we
01:12:23.908 --> 01:12:27.049 have doesn't have that ability.
01:12:27.050 --> 01:12:28.280 Which is amazing.
01:12:43.900 --> 01:12:47.316 OK, uh, where do we have it?
01:12:47.320 --> 01:12:50.490 Yes, I'm trying. Pull up
01:12:52.690 --> 01:12:53.880 some demos.
01:13:10.290 --> 01:13:11.560 Hello wizard.
01:13:26.420 --> 01:13:29.778 Where is all the kinda stuff? Is it in UI?
01:13:32.570 --> 01:13:34.295 Uh, that's why I'm trying
01:13:34.295 --> 01:13:36.860 to find out. No bottles.
01:13:48.710 --> 01:13:51.286 It's not under K, is it Telerik?
01:13:53.640 --> 01:13:57.636 Yeah. I thought I saw it before.
01:14:00.300 --> 01:14:04.390 There's no point asking. Full stop.
01:14:19.300 --> 01:14:22.920 Telerik Tango styles default nothing.
01:14:37.100 --> 01:14:41.996 Line up. This might have some stuff JS.
01:14:52.350 --> 01:14:54.228 OK, you search in your eye.
01:15:04.970 --> 01:15:07.680 OK, so this is uhm.
01:15:11.590 --> 01:15:14.540 Uh, it's under JavaScript file,
01:15:14.540 --> 01:15:17.480 so it's a UI scripts,
01:15:17.480 --> 01:15:21.980 third party Telerik Kendo UI.
01:15:21.980 --> 01:15:23.993 JS, Kendo, Dortmund,
01:15:23.993 --> 01:15:30.010 JS and this is a 2015 ish version.
01:15:33.510 --> 01:15:34.440 Uhm?
01:15:55.930 --> 01:15:57.330 What version did you say?
01:15:59.830 --> 01:16:09.149 Uh. The 2015 dot 3.11 OK so we have come.
01:16:09.150 --> 01:16:10.844 I don't know what is the requirement
01:16:10.844 --> 01:16:12.729 to have this wizard, but I assume.
01:16:19.590 --> 01:16:22.950 How to get that JavaScript file?
01:16:31.390 --> 01:16:33.250 I'm asking James, UM?
01:17:10.720 --> 01:17:11.866 OK, good news is we don't
01:17:11.866 --> 01:17:13.030 have it loaded by default,
01:17:13.030 --> 01:17:14.500 but we have rights to it so.
01:17:16.730 --> 01:17:17.650 Uh.
01:17:49.900 --> 01:17:51.846 I'm asking if James can join us.
01:18:44.120 --> 01:18:44.670 Hey.
01:18:49.380 --> 01:18:51.318 OK, James said gulp the file.
01:18:51.320 --> 01:18:52.608 Find the Kindle section
01:18:52.608 --> 01:18:53.574 and attitude necessary.
01:18:53.580 --> 01:18:55.620 Add the necessary files
01:18:55.620 --> 01:18:58.680 to run it to the build.
01:18:58.680 --> 01:19:00.248 So open the gulpfile.
01:19:02.690 --> 01:19:04.000 Think so.
01:19:10.740 --> 01:19:11.300 In
01:19:15.020 --> 01:19:17.270 to Kindle James.
01:19:20.120 --> 01:19:22.340 Ask Jenn Jenn Yep uh-huh.
01:19:22.340 --> 01:19:25.434 OK, there goes so Jane Kindle files.
01:19:25.440 --> 01:19:30.520 And then. Uh, the ones we're looking for.
01:19:34.450 --> 01:19:36.688 Skin Download Wizard is like a
01:19:36.688 --> 01:19:38.970 Kindle wizard here or something.
01:19:42.400 --> 01:19:46.660 Calendar color picker data dataviz.
01:19:50.850 --> 01:19:53.978 Filebrowser, OK, what the hell is this guy?
01:20:33.630 --> 01:20:37.617 OK. Do you guys see if there is a?
01:20:39.640 --> 01:20:45.530 Wizard or some sort of form? No I tried.
01:20:45.530 --> 01:20:50.250 Searching for wizard in the.
01:20:50.250 --> 01:20:55.820 In that kendo JavaScript folder.
01:20:55.820 --> 01:21:02.060 But I don't know. Ritis say it.
01:21:12.250 --> 01:21:14.070 Listen to one of these other ones.
01:21:17.920 --> 01:21:23.406 No, no results in. Third party
01:21:23.406 --> 01:21:26.300 Telerik kendo UI. The wizard.
01:21:28.870 --> 01:21:32.237 It might be under. Navigation.
01:21:32.237 --> 01:21:36.239 That's what Kindle List is has.
01:21:39.300 --> 01:21:41.835 Keyboard dash navigation is fairly
01:21:41.835 --> 01:21:46.468 new the demo, but it says like.
01:21:46.470 --> 01:21:49.050 Here. There's some.
01:21:51.560 --> 01:21:54.890 Function here is kendo. Wizard
01:21:59.490 --> 01:22:01.550 in that's not in the.
01:22:04.450 --> 01:22:06.478 The thing the fine.
01:22:08.500 --> 01:22:09.528 Doesn't look like it.
01:22:22.000 --> 01:22:23.810 There's a lot for navigation.
01:22:39.020 --> 01:22:41.928 Minified so many find.
01:24:39.450 --> 01:24:43.690 Oh, it may not be. ****.
01:24:49.390 --> 01:24:52.050 We not we may not have access to that on our.
01:24:55.570 --> 01:24:56.578 Version of it.
01:25:01.150 --> 01:25:01.720 Terrence
01:25:12.050 --> 01:25:22.682 I mean like an hour. The type
01:25:22.682 --> 01:25:25.090 of license that we have, yeah.
01:25:42.090 --> 01:25:43.968 Do you know what which type
01:25:43.968 --> 01:25:46.170 we have? Is it just kendo UI?
01:25:50.840 --> 01:25:55.840 Uh, yes. It's all, it's all kendo UI, uhm?
01:25:58.080 --> 01:26:00.656 The version of the I mean were 2015.
01:26:00.660 --> 01:26:03.690 There's a first in 2021. Oh, OK.
01:26:05.800 --> 01:26:07.715 Yeah, 'cause it looks like
01:26:07.715 --> 01:26:10.044 there's just kendo UI for jQuery
01:26:10.044 --> 01:26:12.368 and can do you I for angular.
01:26:15.690 --> 01:26:19.068 We're using kendo UI for jQuery.
01:26:19.070 --> 01:26:24.380 Correct, OK? Looks like there's just that,
01:26:24.380 --> 01:26:28.706 but it's like the version like.
01:26:28.710 --> 01:26:32.490 Like it might be in a newer version of it.
01:26:32.490 --> 01:26:34.920 I think so. I also don't.
01:26:39.370 --> 01:26:43.230 I'm not entirely sure, I think. Papa
01:26:51.730 --> 01:26:52.801 there's a slider.
01:26:52.801 --> 01:26:55.460 I don't know if it's. Correct?
01:27:14.240 --> 01:27:14.890 Uhm?
01:27:20.400 --> 01:27:26.158 Hey, good Sir. Sliders like. Settings.
01:27:32.160 --> 01:27:34.248 The one that's just called slider.
01:27:36.840 --> 01:27:38.410 Under editors.
01:27:43.890 --> 01:27:48.104 Yeah, that looks like it's just a.
01:27:48.110 --> 01:27:50.560 Just like a mixer, almost.
01:28:08.930 --> 01:28:11.000 I wonder if the name is
01:28:11.000 --> 01:28:12.380 something else or something.
01:28:14.750 --> 01:28:17.740 Or Wizard was under navigation.
01:28:23.470 --> 01:28:26.074 Is there an application
01:28:26.074 --> 01:28:29.630 library in a folder? See here.
01:28:42.530 --> 01:28:45.296 And that wizard is perfect though.
01:28:52.570 --> 01:28:56.129 Stepper. So it's temporary.
01:29:05.450 --> 01:29:08.182 Or I mean stepper, who work, I guess.
01:29:08.182 --> 01:29:10.569 Do we have stepper in our library?
01:29:13.940 --> 01:29:16.887 I guess that's what like we should
01:29:16.887 --> 01:29:19.420 search for that kendo stepper.
01:29:24.710 --> 01:29:25.320 No.
01:30:20.940 --> 01:30:21.930 James right now.
01:32:04.100 --> 01:32:08.618 Looks like it does have trevu.
01:32:08.620 --> 01:32:11.446 But so it does have some.
01:32:13.570 --> 01:32:14.998 Of these components.
01:32:22.080 --> 01:32:22.760 Yeah.
01:32:24.830 --> 01:32:27.530 Wonder if tab strip could work?
01:32:34.170 --> 01:32:35.658 Do tab strip.
01:32:38.120 --> 01:32:39.628 It has tab strap.
01:32:59.390 --> 01:33:00.728 I'm just gonna drop that in
01:33:00.728 --> 01:33:02.250 here and see if that works.
01:34:22.980 --> 01:34:24.779 I don't see how that could work.
01:34:36.850 --> 01:34:37.774 Yeah, that wouldn't work.
01:34:37.774 --> 01:34:39.869 It looks them all in on the same page.
01:34:42.380 --> 01:34:44.950 Well. Me.
01:34:54.720 --> 01:34:56.670 OK, so James.
01:34:59.600 --> 01:35:02.558 Uhm, suggested that we can play.
01:35:02.560 --> 01:35:05.266 Just create some sort of field
01:35:05.266 --> 01:35:07.980 and track that step manually.
01:35:10.880 --> 01:35:12.685 So essentially it's going to
01:35:12.685 --> 01:35:15.594 be one big form that has all of
01:35:15.594 --> 01:35:17.652 the form fields attached to it.
01:35:17.660 --> 01:35:21.513 Uhm, but then. On the, UM,
01:35:21.513 --> 01:35:23.859 the step through which is using
01:35:23.859 --> 01:35:26.779 a bootstrap step or something.
01:35:32.320 --> 01:35:35.295 Uhm? Can we get rid of this?
01:35:43.720 --> 01:35:48.607 So, uhm, you mean instead of the kendo thing?
01:36:28.300 --> 01:36:30.256 Yeah. Instead of using the sorry,
01:36:30.260 --> 01:36:32.395 I was trying just want to James.
01:36:32.400 --> 01:36:33.628 Yeah instead using something
01:36:33.628 --> 01:36:34.856 from the Kindle peace.
01:36:37.530 --> 01:36:41.406 Uh-huh UMWA just create like a UM.
01:36:51.870 --> 01:36:54.126 Satisfying examples of people is like
01:36:54.126 --> 01:36:56.770 multi step through and attached to that.
01:37:25.360 --> 01:37:26.450 OK, uhm.
01:37:29.600 --> 01:37:32.372 Do we know the controls are just
01:37:32.372 --> 01:37:34.439 wasting your time right now?
01:37:34.440 --> 01:37:39.948 Do we know if? The question is gonna
01:37:39.948 --> 01:37:43.433 change down the road essentially.
01:37:43.440 --> 01:37:45.294 And the end point is how they're changing it,
01:37:45.300 --> 01:37:51.134 right? Yeah, I think that they may
01:37:51.134 --> 01:37:57.039 add questions later. Uhm and so.
01:37:57.040 --> 01:38:00.988 Yeah, the questions like may get.
01:38:00.990 --> 01:38:02.875 Uhm, pulled into the database
01:38:02.875 --> 01:38:05.550 from an API on the back end.
01:38:05.550 --> 01:38:07.958 And but then we are just pulling
01:38:07.958 --> 01:38:09.760 them in whatever's in the
01:38:09.760 --> 01:38:11.495 database when the page loads.
01:38:14.990 --> 01:38:19.160 And how is the not going to deep into UM?
01:38:19.160 --> 01:38:23.202 How is the? Question reference has been
01:38:23.202 --> 01:38:26.579 control and what I mean by that is safe.
01:38:26.580 --> 01:38:29.534 For example, if question one has 025 01:38:29.534 --> 01:38:31.590 selection right radial selection.
01:38:31.590 --> 01:38:34.742 What is the flag in that question that
01:38:34.742 --> 01:38:37.530 tells it hey, if it's question one,
01:38:37.530 --> 01:38:40.764 hide this question. If it's question two.
01:38:40.764 --> 01:38:43.706 This with that question. Uhm, well,
01:38:43.706 --> 01:38:48.740 I hadn't gotten to that point yet, uhm.
01:38:48.740 --> 01:38:54.105 But as far as the. Type of answer.
01:38:54.105 --> 01:38:58.575 Uhm that's where Brandon had said
01:38:58.575 --> 01:39:04.905 that they all have to be text. Uhm?
01:39:04.905 --> 01:39:09.580 Basically. And maybe that was because.
01:39:09.580 --> 01:39:12.940 You know he wanted to set it up as the
01:39:13.030 --> 01:39:16.560 slider on multi step type thing. Uhm?
01:39:18.600 --> 01:39:22.020 As opposed to just like a
01:39:22.020 --> 01:39:24.300 long list of questions.
01:39:24.300 --> 01:39:27.989 But he said that the the answers
01:39:27.989 --> 01:39:30.749 will essentially have to be text.
01:39:30.750 --> 01:39:34.720 The answers are speech text.
01:39:34.720 --> 01:39:37.234 Yeah. But you have a question
01:39:37.234 --> 01:39:40.249 that it's a radio button though.
01:39:40.250 --> 01:39:42.788 Yeah, I mean the questions that
01:39:42.788 --> 01:39:45.354 there giving us are all like
01:39:45.354 --> 01:39:47.718 in the form of radio buttons.
01:39:53.090 --> 01:39:56.254 But he was saying, you know from.
01:39:56.260 --> 01:40:00.140 A user experience standpoint
01:40:00.140 --> 01:40:04.790 because they, uhm.
01:40:04.790 --> 01:40:09.038 Might want to bring in more questions later.
01:40:09.040 --> 01:40:12.700 And the task said that.
01:40:12.700 --> 01:40:15.087 Uhm, they're expecting to be about 20 01:40:15.087 --> 01:40:17.689 questions to the questionnaire right now.
01:40:17.690 --> 01:40:20.798 We only have.
01:40:20.800 --> 01:40:24.349 10 but they might add some later,
01:40:24.350 --> 01:40:26.582 and so there might be end
01:40:26.582 --> 01:40:28.699 up being as many as 20.
01:40:28.700 --> 01:40:31.454 So I think that was the
01:40:31.454 --> 01:40:33.290 rationale for making it.
01:40:33.290 --> 01:40:36.618 More of a slider as opposed to sorry.
01:40:36.620 --> 01:40:39.866 I let me refresh my question
01:40:39.866 --> 01:40:42.490 or sorry my concern is.
01:40:42.490 --> 01:40:47.326 If we use input type text.
01:40:47.330 --> 01:40:50.290 You cannot use that as a radio button.
01:40:50.290 --> 01:40:53.266 Is my. Depletion, right?
01:40:53.266 --> 01:40:55.924 So if Brandon is saying you
01:40:55.924 --> 01:40:58.537 can only use input type text,
01:40:58.540 --> 01:41:00.946 then we have to go back
01:41:00.946 --> 01:41:03.380 and be like hey client,
01:41:03.380 --> 01:41:07.586 you just sent us questions as.
01:41:07.590 --> 01:41:09.795 Radio selections, yeah.
01:41:09.795 --> 01:41:15.690 Well, I think the the reasoning was that.
01:41:15.690 --> 01:41:19.200 If we're going to display it as a slider,
01:41:19.200 --> 01:41:24.186 then you know this will always be sort of.
01:41:24.190 --> 01:41:28.138 Like this this will you know it's
01:41:28.138 --> 01:41:31.649 it's iterating over the question so.
01:41:31.650 --> 01:41:35.540 I don't know if there was a way to iterate
01:41:35.637 --> 01:41:39.159 and have it displayed different types.
01:41:39.160 --> 01:41:39.614 Uhm?
01:41:39.614 --> 01:41:43.700 I mean, I guess we could do something like.
01:41:43.700 --> 01:41:47.152 You know? Angie, if uh,
01:41:47.152 --> 01:41:53.780 you know and it's the question is, uh.
01:41:53.780 --> 01:41:54.400 Question type.
01:41:54.400 --> 01:41:57.795 And I don't know if this is the right syntax
01:41:57.795 --> 01:41:59.906 for angular, but you know what I mean?
01:41:59.910 --> 01:42:01.620 Like if it's.
01:42:01.620 --> 01:42:02.832 Something like that.
01:42:02.832 --> 01:42:05.256 Then we display you know that
01:42:05.256 --> 01:42:07.895 type radio and then maybe we just
01:42:07.895 --> 01:42:10.069 have inputs for each of these.
01:42:10.070 --> 01:42:12.750 So there's another one for.
01:42:12.750 --> 01:42:15.220 Check box.
01:42:15.220 --> 01:42:18.476 That sort of thing, would that be possible?
01:42:18.480 --> 01:42:21.160 Yeah, that's definitely possible in.
01:42:21.160 --> 01:42:23.757 Oh OK, and we should do that.
01:42:23.760 --> 01:42:25.878 Uhm, what is?
01:42:25.880 --> 01:42:28.145 Who's working on the backing
01:42:28.145 --> 01:42:29.843 on this question? Uh,
01:42:29.843 --> 01:42:32.840 did it give you a simple question like hey,
01:42:32.840 --> 01:42:36.720 this is? This is the radio button data.
01:42:36.720 --> 01:42:40.320 You can get. This is the checkbox to get.
01:42:40.320 --> 01:42:42.970 These were the sample questions.
01:42:42.970 --> 01:42:46.589 Or I'm sorry, not this simple questions,
01:42:46.590 --> 01:42:50.950 but these sample question data.
01:42:50.950 --> 01:42:54.760 Come out with like question dot
01:42:54.760 --> 01:42:58.060 form question type question value.
01:42:58.060 --> 01:42:59.338 No, I don't.
01:42:59.338 --> 01:43:02.820 I don't think I've gotten anything like that.
01:43:02.820 --> 01:43:08.910 OK, uh. Who is the packager for SSP?
01:43:08.910 --> 01:43:09.990 Uhm?
01:43:09.990 --> 01:43:13.230 Let me see.
01:43:13.230 --> 01:43:16.006 I know Brandon Lyon is one of them,
01:43:16.010 --> 01:43:17.926 and I think Brandon.
01:43:17.926 --> 01:43:20.800 This is well let me check.
01:43:20.800 --> 01:43:26.170 Josh stover Brandon Brandon Lyon.
01:43:30.140 --> 01:43:31.040 Uh.
01:43:35.880 --> 01:43:39.950 Yeah. Alright, let me see here.
01:43:42.180 --> 01:43:44.970 A little thinner again in
01:43:44.970 --> 01:43:48.970 there like 20% of calls.
01:43:48.970 --> 01:43:49.915 Uh, 'cause essentially.
01:43:49.915 --> 01:43:50.860 Right now you're,
01:43:50.860 --> 01:43:54.370 I would say you're pretty much.
01:43:54.370 --> 01:43:57.674 Blocked. I mean,
01:43:57.674 --> 01:43:59.053 I guess you can still build up
01:43:59.053 --> 01:44:00.519 the slider part of things and.
01:44:02.540 --> 01:44:03.664 You know gets the.
01:44:03.664 --> 01:44:05.069 Just throw some quite like
01:44:05.069 --> 01:44:06.440 sample questions in there.
01:44:06.440 --> 01:44:08.678 Be like, hey.
01:44:08.680 --> 01:44:10.006 Here's a couple of radio buttons.
01:44:10.010 --> 01:44:10.890 Here's this and that.
01:44:13.890 --> 01:44:17.589 But we want you need to be able to.
01:44:17.590 --> 01:44:20.878 You need to sync with the back Enders.
01:44:20.880 --> 01:44:22.524 Whoever is working on
01:44:22.524 --> 01:44:24.168 getting this endpoint back.
01:44:24.170 --> 01:44:27.410 Oh, these these questions do say like this
01:44:27.410 --> 01:44:30.469 question and it says radio buttons, right?
01:44:30.469 --> 01:44:34.312 But that needs to be translated into
01:44:34.312 --> 01:44:37.476 the database for you to get that.
01:44:37.480 --> 01:44:40.635 From the. The end points, right?
01:44:40.635 --> 01:44:43.020 So yeah, they can if they're going to say
01:44:43.084 --> 01:44:45.266 they have all these criteria, says hey,
01:44:45.266 --> 01:44:47.282 the question is going to be dynamic,
01:44:47.290 --> 01:44:48.730 dynamic and then you don't
01:44:48.730 --> 01:44:50.170 know what the questions are.
01:44:50.170 --> 01:44:52.466 You don't know what the type is expecting,
01:44:52.470 --> 01:44:54.432 yeah? Then it could be hard
01:44:54.432 --> 01:44:56.709 for you to build a UI for it.
01:44:56.710 --> 01:45:00.282 It's like trying to build. Or hell,
01:45:00.282 --> 01:45:03.231 without knowing what the body is, right?
01:45:03.231 --> 01:45:06.102 Yeah, there's there's nothing in here, UM?
01:45:06.102 --> 01:45:07.812 About that, unless it's supposed
01:45:07.812 --> 01:45:10.169 to go in Jason attributes like
01:45:10.169 --> 01:45:12.469 unless it's something like this.
01:45:12.470 --> 01:45:13.170 Whoops, yeah,
01:45:13.170 --> 01:45:15.270 that that's exactly what I'm saying,
01:45:15.270 --> 01:45:16.402 so you have to.
01:45:16.402 --> 01:45:19.316 We have to get with the back end there
01:45:19.316 --> 01:45:21.962 to see what he's expecting where he's
01:45:22.040 --> 01:45:24.368 going to put those pieces there.
01:45:24.370 --> 01:45:27.736 OK and like some sort eyes or flag on
01:45:27.736 --> 01:45:31.317 the front end for us to be able to say
01:45:31.317 --> 01:45:35.137 hey what type of format this question is?
01:45:35.140 --> 01:45:39.320 And what type of?
01:45:39.320 --> 01:45:42.246 Like this is like affect other questions.
01:45:42.250 --> 01:45:45.586 Say if we pulled the Word document right,
01:45:45.590 --> 01:45:50.603 you said you say based on the question one.
01:45:50.610 --> 01:45:52.266 It changes the selection
01:45:52.266 --> 01:45:54.750 criteria of Question 2 to 7.
01:45:54.750 --> 01:45:58.530 So then how is that relationship being?
01:45:58.530 --> 01:46:02.078 Constructed in a question. Yeah, right?
01:46:02.078 --> 01:46:04.046 What is the parent child relationship?
01:46:04.050 --> 01:46:06.978 How it's being constructed?
01:46:06.978 --> 01:46:08.928 Uhm? So on and so forth, right?
01:46:08.928 --> 01:46:10.314 And it's OK if the back in
01:46:10.314 --> 01:46:11.567 there just tell you that hey,
01:46:11.570 --> 01:46:13.388 like this is how I'm going to make it.
01:46:13.390 --> 01:46:14.410 It's going to question one.
01:46:14.410 --> 01:46:15.822 Have a Jason attribute.
01:46:15.822 --> 01:46:16.528 I says.
01:46:16.530 --> 01:46:20.310 A control or parent of questions 2435.
01:46:20.310 --> 01:46:23.530 Whatever income limit is air
01:46:23.530 --> 01:46:26.750 a whatever that's worth 2.
01:46:26.750 --> 01:46:26.998 OK,
01:46:26.998 --> 01:46:29.557 but we had to have something on the front end
01:46:29.557 --> 01:46:31.987 for us to attach you to then dynamically say,
01:46:31.990 --> 01:46:32.620 hey.
01:46:32.620 --> 01:46:35.140 Based on these selections,
01:46:35.140 --> 01:46:37.798 change the selection for those and
01:46:37.798 --> 01:46:40.380 then for every those children,
01:46:40.380 --> 01:46:44.640 questions like say for question #2.
01:46:44.640 --> 01:46:46.750 Like Pfizer Madonna like, right?
01:46:46.750 --> 01:46:49.907 Like what is their relationship to what
01:46:49.907 --> 01:46:53.056 the question one's answer is going to be?
01:46:53.060 --> 01:46:56.390 Do they say display on parent
01:46:56.390 --> 01:46:58.610 question equals to one?
01:46:58.610 --> 01:47:01.552 Right, it was two stuff like that, so that's.
01:47:01.552 --> 01:47:05.823 All the court errors we need, yeah, I mean,
01:47:05.823 --> 01:47:08.770 just from the way they worded this.
01:47:08.770 --> 01:47:11.626 I'm guessing that if they select
01:47:11.626 --> 01:47:14.340 zero then they don't display.
01:47:14.340 --> 01:47:16.472 Any of these questions?
01:47:16.472 --> 01:47:18.839 If they, uh, select one,
01:47:18.839 --> 01:47:21.437 then they display two and three
01:47:21.437 --> 01:47:23.766 because it says how many doses.
01:47:23.770 --> 01:47:27.123 If you choose one then it wants
01:47:27.123 --> 01:47:29.010 information about dose one.
01:47:29.010 --> 01:47:30.754 If you select two,
01:47:30.754 --> 01:47:32.934 then it wants information about
01:47:32.934 --> 01:47:34.650 dose one and dose 2.
01:47:34.650 --> 01:47:36.560 And if you select three,
01:47:36.560 --> 01:47:40.046 then it wants information about all three.
01:47:40.050 --> 01:47:42.600 And for each one it wants
01:47:42.600 --> 01:47:44.300 the manufacturer and the
01:47:44.389 --> 01:47:46.670 vaccination. So I'm pretty
01:47:46.670 --> 01:47:48.770 sure that's what this means.
01:47:48.770 --> 01:47:51.675 Question 27 based on selected
01:47:51.675 --> 01:47:53.999 responses to question one.
01:47:54.000 --> 01:47:56.891 But I don't know how they are
01:47:56.891 --> 01:47:58.815 displaying these if they're
01:47:58.815 --> 01:48:01.179 like just Jason attributes.
01:48:01.180 --> 01:48:09.220 Like if you know question with ID one has a.
01:48:09.220 --> 01:48:14.309 You know the answer is a one.
01:48:16.680 --> 01:48:22.210 Then, uhm, you know. Display the Jason
01:48:22.210 --> 01:48:26.920 attributes and there's like an array of.
01:48:26.920 --> 01:48:29.470 Possible answers or something like that.
01:48:32.610 --> 01:48:34.338 I don't know how how they want all that.
01:48:36.780 --> 01:48:39.090 Yeah, it's yeah I would.
01:48:41.940 --> 01:48:44.495 Uh, I would say. You need to
01:48:44.495 --> 01:48:47.209 figure it all out first before
01:48:47.209 --> 01:48:50.800 you start building this, OK? Uhm?
01:48:54.600 --> 01:48:56.322 Because based on what structure they're
01:48:56.322 --> 01:48:58.686 putting it on, is how you're going
01:48:58.686 --> 01:49:01.010 to construct the front end. Yeah.
01:49:04.070 --> 01:49:06.558 Uhm, so I would put impediment on this
01:49:06.558 --> 01:49:08.948 and let the project manager know.
01:49:08.950 --> 01:49:11.758 OK hey I need to get with the back
01:49:11.758 --> 01:49:14.747 end or at least to talk out what
01:49:14.747 --> 01:49:17.088 I'm expecting on the front end.
01:49:17.090 --> 01:49:19.232 Yeah, 'cause you can always just
01:49:19.232 --> 01:49:21.689 hard coding and get that part out.
01:49:23.980 --> 01:49:27.462 You know? If that makes sense.
01:49:27.462 --> 01:49:32.153 Yeah, yeah for sure. OK, cool uhm.
01:49:32.153 --> 01:49:34.197 Well typing sorry time.
01:49:34.200 --> 01:49:35.982 Is there any other questions or
01:49:35.982 --> 01:49:38.080 stuff I need that can help with?
01:49:38.080 --> 01:49:41.650 I know that wasn't really an answer, but.
01:49:41.650 --> 01:49:42.844 No, that's fine.
01:49:42.844 --> 01:49:46.489 I mean my only other question real quick was,
01:49:46.490 --> 01:49:50.010 uhm, you said, James said, Uhm?
01:49:50.010 --> 01:49:54.588 To build out the multi step.
01:49:54.590 --> 01:49:57.586 Uhm, you know display of the questions?
01:49:57.590 --> 01:50:00.794 UM, does that mean we're not
01:50:00.794 --> 01:50:03.940 gonna use the kendo version?
01:50:03.940 --> 01:50:07.796 Uh, unfortunately, not OK, so that's not a.
01:50:07.800 --> 01:50:12.129 It's not part of the version that we have,
01:50:12.130 --> 01:50:16.370 and it's also not. Uhm?
01:50:16.370 --> 01:50:19.382 Per James stuck the angular attachment
01:50:19.382 --> 01:50:22.370 to those forms are very iffy.
01:50:22.370 --> 01:50:24.890 OK, so it's not worth like trying
01:50:24.890 --> 01:50:27.978 to load a newer version of kendo,
01:50:27.980 --> 01:50:29.908 uh, that require yet.
01:50:29.908 --> 01:50:31.836 It requires reworking core.
01:50:31.840 --> 01:50:35.568 OK, so probably not.
01:50:35.570 --> 01:50:38.002 So while you can probably do is just
01:50:38.002 --> 01:50:40.488 do like a for the step controller,
01:50:40.490 --> 01:50:43.478 just create like a medical questionnaire
01:50:43.478 --> 01:50:46.541 controller connecting or you have and just
01:50:46.541 --> 01:50:49.300 add a scope value NSX step right like?
01:50:49.300 --> 01:50:51.238 Yeah, here's a medical yeah yeah,
01:50:51.240 --> 01:50:53.184 like type property on stuff, right?
01:50:53.184 --> 01:50:55.776 So you just be like current step or
01:50:55.776 --> 01:50:58.528 something. Current stuff is integer.
01:50:58.530 --> 01:51:00.636 Then I should click the next
01:51:00.636 --> 01:51:01.689 and previous button.
01:51:01.690 --> 01:51:04.483 It will then increase and decrease those
01:51:04.483 --> 01:51:07.610 button to a certain point like 0 or.
01:51:07.610 --> 01:51:09.710 When whatever and then.
01:51:09.710 --> 01:51:12.850 You can then. Uh.
01:51:12.850 --> 01:51:14.422 Dynamically calculate the last
01:51:14.422 --> 01:51:16.780 step based on the endpoints return,
01:51:16.780 --> 01:51:19.597 so if the if the back end endpoint for
01:51:19.597 --> 01:51:22.676 the question returns 20 questions right.
01:51:22.680 --> 01:51:25.100 Then depending on the logic
01:51:25.100 --> 01:51:28.300 of what they wanted to be set.
01:51:28.300 --> 01:51:30.679 It will be.
01:51:30.680 --> 01:51:31.490 Uhm?
01:51:35.090 --> 01:51:37.850 Yeah, if people logic you'll just
01:51:37.850 --> 01:51:40.699 do like calculate how many steps.
01:51:40.700 --> 01:51:43.860 Or how many? How many steps the question
01:51:43.860 --> 01:51:47.149 needs to have and then that will be
01:51:47.149 --> 01:51:50.078 translated into the min Max of the
01:51:50.078 --> 01:51:52.550 page or pagination of those slider.
01:51:52.550 --> 01:51:55.626 Now. Uh, is this?
01:51:55.626 --> 01:51:59.740 This is user registration right? Yeah.
01:51:59.740 --> 01:52:02.057 Oh, it's always at most important part.
01:52:02.060 --> 01:52:03.340 OK 'cause you can't.
01:52:03.340 --> 01:52:06.359 If you need build this out in action form.
01:52:06.360 --> 01:52:09.339 It's like cool 'cause it's easy as hell but.
01:52:11.680 --> 01:52:12.940 User registration.
01:52:12.940 --> 01:52:16.150 It's gonna be annoying. Uhm?
01:52:18.990 --> 01:52:19.340 I.
01:52:21.860 --> 01:52:24.180 I don't know. I will also bring it
01:52:24.180 --> 01:52:27.004 up if it's if this is too much work.
01:52:27.010 --> 01:52:29.375 Potentially just be like half
01:52:29.375 --> 01:52:31.740 the user register for account.
01:52:31.740 --> 01:52:36.004 And then afterwards they have to go in.
01:52:36.010 --> 01:52:38.032 Fill out the medical questionnaire before
01:52:38.032 --> 01:52:40.363 they can proceed to arrested the side
01:52:40.363 --> 01:52:42.526 or something that will make it easier.
01:52:42.530 --> 01:52:44.486 'cause then you can use action
01:52:44.486 --> 01:52:45.790 form grid and stuff.
01:52:45.790 --> 01:52:48.065 Oh OK, yeah, but I don't know.
01:52:48.070 --> 01:52:49.374 They probably won't just
01:52:49.374 --> 01:52:50.678 because they want this.
01:52:53.600 --> 01:52:55.904 But yeah, uh, that's probably we have to
01:52:55.904 --> 01:52:58.592 go find out what the questions are found
01:52:58.592 --> 01:53:00.860 on the structures you're going to need.
01:53:00.860 --> 01:53:02.939 And then from there we can then
01:53:02.939 --> 01:53:04.640 determine how to dynamically.
01:53:04.640 --> 01:53:06.610 Approach the structure of the
01:53:06.610 --> 01:53:08.976 questions and then render the data
01:53:08.976 --> 01:53:11.223 on the front end based on the
01:53:11.223 --> 01:53:13.539 questions and putting on restrictions.
01:53:13.540 --> 01:53:19.250 OK. Cool. Yep, cool.
01:53:19.250 --> 01:53:20.598 Alright, thank you Patrick.