For our scheduler, but we will have to do
is we will check with what has the
highest score, right. Are you, I'm
assuming a higher the score, the better
the lead is, is is that how you wanna do
it or the lower the score the better
Delete because I've seen it at both
places, both ways Higher, higher the
score, yeah. So which one you would?
What are the leads by scores?
Right. So if I have 5
leads, no no it hasn't. So
scores versus the dates already mapped.
So I retrieved the 999 from
the model and the top five
scores we are storing in database.
Suppose I create the file. It's right?
So lead one, lead to lead to
score is say 800 and it has
a different set of blades. So which
one we have to process first? That's
on my question. First one, right? The
one with the highest score. OK, first
scene, right?This is exactly, well,
not, not not first and first out based
on the score, the highest score, you take
that one first and then see what are
the VPS list. And let's say he gives
you VPS 256. So then you should see
if is VPS 2 available. If yes, the
call goes to VPS 2 if EPS is
not available. It should go to PS-5 now.
First one's taken care of, then you the
scheduler moves on to the second one. Now
with the 800 one. 801 has VPS 5785. We
know it's already in call for the
previous one. It should go to seven. So
that's the idea. It's always the same
process for each and every lead. Lead
comes in, it's not assigned lead comes
in. Store in database, right? Yeah,
call the model, get the output.
Store the output in lead. The highest
score. That person. Yeah, yes, yeah, yes.
Next highest. Yeah, yeah, yeah. It's a
sequential process. Process, right? You
always have one scheduler that's
assigned. Yeah. All the business rules
will live inside the scheduler, right?
Higher score list. How much time it has
been all So scheduler is your source of
truth, right? You get the model and
everything, each and every lead will have
the same life cycle. They all go through
it, right? They all have to be scored
right? Because we cannot, the model
cannot score multiple lead at the same
time because what can happen is you can
receive a lead then the. Output from the
model can become obsolete. So you always.
Each lead needs to be scored, does not
matter if there is a queue or not, right?
Because yeah, for data analytics
purposes, yeah, they're met with a
chance. 2 lives can have the same score.
Is that possible? Yeah, yeah, if it's
possible. So in that case you take. The
time which one came first? Yeah, Right.
So, yeah, that. So that piece, again,
will live inside the scheduler, right.
Ayesha's code will not give you which
one. Yeah. I think of that as a black
box. Think of it as just something that
will give you a score and a list. That's
it, right. Makes sense. Are you, are you,
are you aligned over there?
Yeah. Cool. OK, Actually,
yes. Do you wanna give, uh, an
introduction And, uh, what is it that
you're doing in? Yeah.
Thanks. Uh, hi all. So I'm sure and
uh, I'm from the billing software and
last week actually I had a connect with
Malaysia and that's where we pinned down
the requirement for the automation and
that were including the. Let me share the
screen quickly. Just a
second. Let me, uh record this session.
Yeah uh, this ohh, it's not letting me
record. Ali is can you record this,
please? I don't, it's not letting me
record or Assad or anybody else who can
record. Uh,
yeah.
I think Karen did it. Karen did.
Yeah, Yeah. OK here. I think I
did. I can start it. OK.
Do let me know once done.
I think I started it. I don't see
it being red, but it's saying it's
starting, so I think you're probably
good. Uh.
Right now it's started, yes.
Continue, yes, OK. I don't see any
recording but yeah, I will start then.
OK. So as per the requirement, the flow
user flow was we are starting from the
manual job on the service Titan, it's
assigning the technician and dispatch and
then flow to the take app and then
go for the Torch app and then complete.
The entire end to end flow as a happy
flow, OK. And that's what has been
automated. But definitely since on the
Take app we do have some development or
the new UI that's where we are block. So
here we won't be able to proceed till
till I get some work around or maybe the
new deployment is there. But yeah, as a
phase one. As a Part 1 for service
type, an entire flow has been automated
using the playwright. And just let me
show you the, uh, this part OK.
And so I have developed from start
to end entire flow dispatch and the
status verification and assertions all
has been there page object model
approach. I have implemented as a
framework and let me first have a quick
execution then maybe we can come up with
the questions and then uh, any any ideas?
Just a couple of places I have
put the hard pause deliberately just to
showcase some some points to you, but
that will be like get removed once
it's all good.
Do you have the passwords hardcoded in
your automation suite or do you, are you
using something, uh, that will, that is
parameterized. We can then change, but
yeah, it will be like on the config
file or anywhere we want to. We can
keep that as a exposed, right? It, it,
it, it exposed. Yeah, think through
other. Which is good to take a security
concern, right? Yeah, I just have
passwords like this, but but this is
yeah, one environment for service
student. So yeah, that yeah, that poses a
security risk. So just look into that,
see if you can hash it because we
cannot have password in plain text in in
the code, yes. So for initial
phase it's been done and then of course
that was the like as the requirement we
can do that as well.
You probably can use, um,
secret manager AWS. That's the
best way to do it.
Yeah, OK.
And all these values are parameterized as
and when required we can maintain the
different config file or the test data
and everything. And we can do the
permutation combination and have the
different slows.
And right now here, uh, we are
waiting. OK,
so Part 1 on the call page, uh,
which was there as the first page that
has been done. OK, And just to showcase,
uh, uh, what I mean, the page object
model wise, so to keep that manageable
and easy to maintain and then the
modification, I do have this call page
job page. Login page different and
respect to actions and the element
activities belongs to that it will remain
there. So any changes on that one
particular page it will be easy to go
there and do the modification without
impacting or having bad impact on the
other part. That will be modularization
benefit. So once that is
now, now the first call page is done.
Now we are learning on the job page.
So if you see what I based on
this URL or this page title, I'm name
it as a job page or the call
page. So I will just simply.
What is it? And I will just resume the
execution now.
OK, and then here, just to
showcase you guys last pause, uh,
there's two. Focus this has been
dispatched and definitely we can see that
part as well on the other uh,
uh, app OK, And then now I'm
just resuming this one as well, and
then it will close.
So now if I uh.
If I go here.
Now this is I'm doing manually.
OK, so at least here I can see
this technician as I'm ready, but I'm not
having any any way to view the job
or something and that's where. Is block.
I guess we are working on that part.
On the same line, uh.
If I do here just to check
if that's really done or not.
So I had deliberately cancelled all the
earlier jobs and then right now I
do have, uh, I should have only
one job with this particular technician.
Which is this one?
This one, so it's done, uh, just for the
assertions and definitely in, in the
script everywhere we do have that
assertions to make sure that we are on
the same page and checking, uh, the steps
are taken care and then the expected
versus actual part as well. So this way
it has been automated as a Part 1.
Any questions? Any doubts?
And yes, uh, if I click
here report.
We will be able to see the report
as well and we can simply check what
actions and everything has been done,
what data was shared, uh, what were the
parameters and everything. Uh, we do have
the screenshot. We do have the traces. We
do have the recording as well, so
complete. 3.40 minutes, uh, whatever was
recorded that we can simply click here
and then check what exactly happened then
this will be helpful to have the
back pressing or debugging or just to
as a proof or something.
And uh, yeah, so just so I understand the
flow is you're going to create a job in
service item. From there it's going to
flow to field force. You're gonna log
into field force with that technician.
You should see that job, then you're
gonna submit the green lights form. And
then you're gonna see the lead job
created, then you're gonna go to the
Torch app and then you will see, uh,
that, uh, the phone rings for that torch
member, correct? That's the full flow
that you can. That's the full flow. Yeah,
that's the full flow. So I've broken this
entire flow into the three section based
on the application service. Then and then
the take up and then the torture.
OK, Yeah.
So reporting and all those are there just
to check, uh, what has been failed, why
it was failed. Uh, that will be easy to
understand, right? And then we can
directly work on the exact point where
the issue was arises. And then that will
be helpful to have these all recording
screenshot sharing report and anything.
And it took almost 3.40, uh,
minutes.
Yeah, no, this is good. Uh, just that,
uh, not sure if you've seen the new
requirements and it'll be a little
complicated. It's not just going to be a
jobs created and it'll flow through the
torch member. There'll be some AI scoring
involved and things like those. So not
sure how you plan on automating that
because. Uh, you know, if you, if you
create a job, it's not just gonna flow to
anyone it based on the model, it's gonna
give you an output and based on the
output, uh, right. Uh, the job or the
lead job should go to a certain towards
member, not just any torch member. So
think through how you automate that. My
best way would be to. Connect to the
postgres database as well. See the data
in the postgres DB. When the lead job
is created, you can query the lead job
table with that lead job ID that one
that you were showing and using that
query you can fetch the score and the
VPS list and you can verify. That the
back end Java code is correctly assigning
a lead to a torch member.
If you really want to test that flow,
full flow, but yeah, we can talk about
that later, yeah. So that that's the plan
actually. So initial primary requirement,
can we do really the automation and
everything. So for the initial phase,
just this could be considered as a demo
or something which can be done. And then
might definitely we will have the exact
point where is the requirement and there
might be. Find out the feasibility, the
suitable tools or the approach, anything.
And definitely, uh, we'll, we'll discuss
on that part. OK.
Any any other questions or?
Yeah so, so this, this basically reduces,
uh, the testing uh uh, cycle time Assad
right and also definitely like creating a
job and all it's it's painful yeah 100%
agree with you yeah yeah and that's for
the developer says well, I mean I was
asking uh Flyers. I like it
it, uh, Azure developer, right? Uh, you
know, I don't have to feel all these
fields and uh, it's a beating the uh,
green, green, green light form right. So
all those I just run this script. I
have the data ready in my DB yeah
yeah, go ahead and test so easy for
developers. Yeah, for sure it can be
test driven development. Yeah. OK, so we
have Ali here. So Allie, just to keep you
in the loop, right? Uh, so far, OK, you
know, since we block from testing, but we
retested a lot of those bugs that was in
the head raised and those are not
happening. So we're good over there. We
broke down the work for the new.
Requirements, right based on the smart
call routing model, the lead should be
assigned accordingly based on the best
score, based on who's the best VPS to
handle that lead, so and so forth, all
that stuff right So we have the high
level requirements. We have the technical
stories created and those stories are
also assigned right now uh, solve a
problem or a bottleneck right now is. So,
so far we've been treating the AI model
as a black box. That is the job of this
model is basically any lead that comes
in, it has to score it, it has to assign,
it has to create a score and it has to
sign apps list. So our back end
developers can still work while Ayush is
work in the model, right yesterday. I
think you're also up to the. Meet that we
don't have data right or enough data
right now for I used to really build a
model right. So that is somewhat because
from what I remember in one of the
meetings with Matt and Luke, they both
said, hey, the data is there. Why don't
you guys go and profile it and tell us
what actually is a good lead versus?That
is not elite, right? But when Ayush cut
the data, there's just no data for him to
really, uh, assess those leads. So we
somewhat blocked over there. So just
wanted to check on what is it that we
can do there? Do we know if we have
archived and service Titan of the
different jobs and things like those
because we don't have this. That in
postgres tables.
OK. So you're asking for what data, the
job data, yeah, Basically, uh, historical
data for the jobs and their conversion
rates and any, any metrics associated
with the jobs that Ayush can use that
data to really see what jobs or what
is a good job versus what is not
a good job. So Ellie, uh, just
as we discussed yesterday, the lease job
and the green lights, green lights data
is not there. So that is the issue.
Send did you send the back end team
a note?No, we
discussed it yesterday and uh, if you
remember, I was pulled into another call
to work parallely on a project. So I've
talked to them and they are looking into
it, whether that data is available or
not. The end list is one that we have to
run in the paddling. So we are using the
same data there as well to identify the
why if a if a pair. Is best and why
they are the best. So it will be the same
data will be used there as well for that
analysis. So that team, that back end
team is looking into the data. I'm
waiting for the confirmation from them,
but I'm dropping a mail today, uh, to
you, Kieran, everyone in this group so
that we will be on the same page.
OK So what help needed do you need
from me?If we have the
leads, job data and green light data then
I can start on the on building the model.
Ohh, yeah, I think if you can ask the
team for that, they'll be able to pull
whatever information you need. Yeah. So
that's why that's what I said that I'm
working directly with the team that you
have included in the call yesterday. So
I'm waiting for the for a confirmation
from them tomorrow morning, early
morning, I'll, uh, follow up with them.
Otherwise I'll. Put it up on a on a mail
officially. OK, yeah, if you wanna, I
mean, if you can just e-mail them what
exactly you need in case they forgot
today, that would be great because I know
we were just discussing things on Nicole
and then I'm actually meeting with Vivek
in about 30 minutes, so I'll bring this
up to him as well and he'll get you that
stuff. All right, I'll put up a mail
right now and I'll tell you. Business so
that uh, we think buildings in which
yeah, Yep. Great. OK,
so let's say are you solves that problem.
OK, this is question to back into
Malaysian Anthony, right, You all have
those stories assigned, right. Let's we
work with the assumption that the model
will have two outputs, one will be a
score and the other will be the best
VPS list right for that lead. Right. We
already have the technical service
created. How are we progressing over
there? Any questions, anything?
Anthony Malaysia, Visva.
They said as of now, that's it, I'm good.
You know something I discussed that
the sorting order. So with that
one I'm good. I'm writing the
logic for starting and tomorrow I'll
be changing the scheduler logic to
retrieve the highest score on the
Yahoo or which job came first
I'm going to. That that logic. So,
OK, so Anthony added three columns to the
lead job table. Yeah, right, right. Yeah.
So, yeah, one question over there. So the
second column, which is the priority
list, Anthony added as a JSON column data
type, which is fine. I I personally like
sounds a lot because they have a lot
of flexibility. Right, uh, I was looking
into it. Postgres also supports arrays.
We can create the column as an array
or we can keep it as a JSON
Data type. Uh, any opinions over there?
Like, do we want to keep it as
JSON? It's fine, It's fine. Now we object
to throw, the object mapper will convert.
Again, we convert into the respective
collection, so that's not an issue. OK,
so let's keep it as a JSON self
in the future. We need to store more,
more data in it. Yeah, we we, we
can do that. My, uh, second option is
since we already have the JSON. Column
Anthony, we can remove the second, uh,
the first column which is the score.
Because if we just add one JSON Data
column, in that JSON we can input the
score as well as the priority list. So
instead of doing 2 insertions in two
different columns, we can take the output
from Ayush. There is going to be
based on and put that dumb that JSON
directly into that one column. So
thoughts on that? I think that's a better
approach with any. OK, there's the object
which is holding the list. Another one is
the score and I convert into the Jason
I will store it. So from there again
we will. I will provide the model
tomorrow. So the model is holding the
score as well as the list and
convert a suggestion and store it in
database. While retrieving again we
convert that map to the model and
we'll be passing that to the call
routing logic which is implemented.
Ohh yeah. So regarding this score and
and the priority list, I, I would
prefer to have them separated because the
score values and score is used for
scoring. Yeah, yeah, yeah Ohh yeah, yeah,
yeah, yeah, yeah, yeah yeah. Correct,
Anthony. Yeah, that's a
good point. Because first we what, uh,
first we sort on scores. Yeah, based on
the highest score that. Yeah, yeah. So
no, no, anything. Yeah, that's that's
that's a very good call out there. Yeah.
Good, good, good call out. Yeah, yeah.
OK. So let's just keep it that way. So
Anthony has already updated the dev
tables with the column names, So we're
going to use those new column names. Make
the changes accordingly, right? For now,
just stub some data, right? Whoever's
working on that piece, insert some dummy
scores. Ayush, uh, we'll just go with the
range of 0 to 999, right? For now, just
insert some dummy data and start testing.
Then one thing that is somewhat pending
is the business rules, right? And you
can. Already I'm just storing the
random data or random number yes,
exactly instead some random data yeah
and uh, the list anywhere it
is we are getting from the
previous module, so I'm storing that
one as it is so the
list so. That, uh, tomorrow if, uh,
call once I wished and we'll take that
API call and we will store this one.
Yeah, OK, so yeah, just one thing
quickly. I know we're trying, but Allie,
can you stay for five more minutes or
two minutes maybe or we can do it
tomorrow. Can I got like a minute OK,
basically. Uh, Eddie, when really thing
that's pending from you, well, not really
pending is we just need to confirm with
you again, what are the business rules on
top of, uh, the scoring By that what I
mean is I remember we talked about should
we not have lead wait for more than 10
minutes other, any other business rules
that we need to take into consideration?
While assigning leads, uh, you know that
there are we tennis team and also still
there in Boston. They were called the
lobster. The list I gave you is what we
should be doing. That is what Matt
provided. It's something I can follow up
with in Franklin. Once we have it
working, they may say something else, you
know, like as we go through it further,
but. Now I know you can use
this list. OK, so this is again going to
be part of scheduled logic. Vishva, if
you see over here my screen right, a
technician can be skipped if the queue is
if ability. They have not been waiting
for 10 minutes right? So for your
scheduled logic, you would have to 1st
see how long the lead has been waiting
for. Right. If it has been waiting
for more than 10 minutes, which is
then going to, Trump objected again.
Right. So this logic is going outside.
Yeah, that logic that suggested that.
Need to check on the dog.
I'm gonna put the result in the chat
here. Yeah, yeah. Cool. So. We had,
I think the, uh, Anthony has
to take that part because I'm
touching the scheduler. OK, So you're
basically getting all the leads that
need to be yeah, yeah, OK.
So after agreement, take that plug
and it's checking that 10 minutes,
whatever. Find it.
Sign in. Sign in.
OK. Yeah, I think under the Anthony
business your piece for the websocket
piece, right. So once the scheduler gets
a list of all the leads, right, that need
to be assigned right, you need to get the
time delete created ad, right, If it has
been more than 10 minutes, right or
something that has a better lead right,
this which gives you. But if something
has been. 10 or more, you need to push
that lead to the torch member before you
push a better lead, right? Just that
that's like one small thing that you have
to add over here. OK, so far this is all
that we have, but later, you know, as we
have actual members test and Luke and
Matt, they give some other requirements
so we can add that too. But I just want
to confirm with you we have the technical
design. We have the new columns, right?
We have the stories created. We have the,
uh, also descriptions added code wise,
technical stories and all the stories are
assigned. So just wanna make sure to the
three devs that we have on this call,
we're from Malaysia and Anthony, you guys
are sure on what you guys need to do
and there's no questions. Everything is
clear, correct?
Can I get thumbs up correct?
Yeah. Anything OK, Cool. So today
is Tuesday. Yeah, Yeah, go ahead,
Anthony. Just, um. It's
all my tickets on on.
Sorry both all of us are on on
depending on the new columns I added. So
if you find any issues or mistake on
the new columns or issues then I'd like
you to. Yeah, you'll
let me know, um, update me what we need
to fix as well, Yeah. Yeah,
I think I saw the columns there. Uh yeah,
all looks good, right? Everything over
there. But yeah, that's a good call out
again uh, which one did you share the
branch? I don't think you shared the
branch, right. The base branch said all
the devs should be working off of Yeah,
this is only the release, just release
branch. You need to cut out the feature
branch and I'm creating. Ohh, that
branch, we are going to miss
that. I will set it tomorrow.
Yeah, so create that. No, you
just uh, put it from the
release branch. Yep, Yep, that's fine.
OK, cool. So, uh, for assumption
purposes, right? Ayush, I'm thinking your
flask. API will have a JSON
output something like this right? So
ayush for your visibility as well
right. These are the column names
that we have added right in
the table right? Let me just
check here. So one is score
right so. I am thinking you
will have a key called score
all right in there. This is
going to be an integer key.
OK, cool. OK and then second
thing is.
Priority_list, right? That's a. You can
create a key right in your
output, right? That is going to
be something like this. OK, that
is going to be an array
where you can have over here.
How are we doing it over
here?Uh, which, uh, how
are we storing the data for VPS,
right? Let me go here. So we
have the technician table over here,
right?Do
we need to search by e-mail or what's the
process over there?Sorry, could
you please repeat?So,
uh, Ayesha's output will give you the VPS
list, right? That, yeah. Is it going to
be the name of the VPS he needs
to put? Is it going to be the
e-mail or is it going to be the
technician ID? No, the technician will
get the technician IDs and they're
reacting. Yeah, yeah, yeah. Oh, oh,
it's a map map. Yeah, yeah, yeah, yeah.
So it's basically going to be a list,
right? It's going to be an array. The
first zeroth index is going to be the
the the the best 1. So from the
model, right, we'll get the score as well
as the location map. Without reacting,
who is the most? Yeah yes, that's
the map so.
Yeah, that's exactly what I'm saying,
right? So that map is basically this
array, right? The zeroth index is going
to be the best VPS. The first index is
going to be the second best, right? So
that map is this area over here, right?
So now what I'm asking you is what should
be. What what what are the
elements for this array? Do you need the
technician name? Do you need the
technician? I think I DIDID. OK, OK, it's
cool. It's. Ohh, I'd
just specific. Absolutely. Yeah, exactly.
I I agree ID is unique. So
again, you can create it as an
integer key. OK, Ayush, right. So
something like this as an output, right?
Which is basically basically some
technician ID. OK yes. So So what
this means is that for. Or
we can also put uh,
we would need to put
an ID you guys play.
We are getting into it
with the priority ranking the
technician versus like AA1650808 right
along with the. One is
the person, Yeah. But this is easier,
right? But this is easier. You don't have
to do a map, right? You can quickly
iterate through arrays, right? It's it's
easier, yeah. But if you if you have an
array, you can just directly go to the
query table and just loop through the
array directly versus doing a map, right?
I think it's easier if he just gives you
So what? Here's what I have in mind. As
part of the as the response are you it's
going to be something like this lead job
ID, right. So that back end knows that
this data is for this lead job ID, OK,
right. And in the in the request payload,
right back end will share with you the
lead job ID, right? Yes. Then so this is
just basically what you are getting
you're sending it back second. This
score, right? Whatever the score needs to
be and the priority list, uh, which one?
That's part of your code, I think, right?
Uh, what is? Let me take a look yeah,
that's the existing one, Malesh. Uh, I
prefer this one better. I personally feel
like this is easier, right? You can just
iterate to the index, but if you want, we
can have a you create this one too. This
is going to be more concise and simpler,
but if you guys prefer the this way, we
we, we can do it this way.
Yeah, basically the technician ID with
the PRD, Yeah. So do you
prefer this or do you, do
you prefer a key value map,
dictionary or hash key value map?
I'm going to prefer so that
we don't need to wait. OK,
use the existing logic. OK, that
that's fine too. No, that if that's
the case, I guess anything good job,
I guess we that we created as
a JSON column. It's more what's it
call? Yeah, it is more flexible. So
in this case, Ayush, it will be
something like this, right Tech ID_right,
zero. Right, well, I see value
starting with 0 here.
Yeah, I understood the point. How you're
wondering. That's not a problem.
Yeah, just a clarification, um,
whatever we are getting from,
uh, the data model, right,
that is uh, UH-12345 whatever
the one uh, which got
added zero is uh, like
we checked against the database
whether it is present. I see,
I see. I see. OK, got it. Got it.
OK, cool, cool. So are you it's going to
be something like this. Got it right.
It's going to be OK. So so you're putting
like. Yes, please go
ahead. Yeah, so. Whatever
is not there, the priority list from
the, uh, data model will push that
down at the end, uh, exactly which
is active right in any order exactly.
Well, no, no, I'll tell you something.
So yes, we will do that Malish,
but you don't need to insert that
right?So the idea is this is
what we're going to be. What is going
to be inserted when the lead is going
to be assigned? Let's say I only gives
me 123451 and two right? Both 1 and
2 are busy, right? Then I need to
check the DB what other ones are active
and send the lead to that. Sports member
hey, because you cannot because again,
the idea is while inserting you,
you, you, you don't have to
mutate this array or this JSON
because the data can change any
while while you're inserting and after
it's inserted right so.
This is what model will give you. This is
what you will insert when it's time to
send the lead. At that point you will see
this list or this JSON, right? If
everything, if everyone over here is
inactive, right? Then you just go to the
database, right? Pick up the first active
torch member and just send it to him.
Makes sense yeah uh yeah. In in
another perspective, we could avoid the
database hit uh, even before uh, we
are sending that makes sense I mean
you, you can, but again, then in
this case, if you wanna do that,
if you want to append 345. Right,
or zeros to it. You would have to
not get just the active ones because
while inserting someone can be inactive,
but when it's really time to send the
call they can become active. So I I'm
OK either way, right? Which way you do
it right? My I think the better way
is you insert this. If someone is not
found over here, then you just get the
active list and send it there. Personally
that's how I would do it, but if you
think that's it would be easier this way.
But basically the idea is if you want to
append new keys to this one new key value
pairs, you should not be appending
inactive ones. You should not be
appending just active. It's because
something that's active can become
inactive and something that is inactive
can become active when it's really time
to send the call, right? So whichever way
you do it, just make sure you account for
this. OK? So whoever's doing it, who, uh,
so who is taking care of insertion? Is it
Anthony Malish or Visva? I think it's
Malaysia you are doing that. Me.
Right here. No, I'm doing that.
Uh, one second. This one is yeah,
this comes from the data model.
I'm doing that one now. I'm doing the
second part. Let me take a look. Look,
look. Hold up, hold up, hold up, hold up.
Let me take a look.
Let's see the ticket. It's a small
change. Yeah, Yeah, it's it's it's a
small change. But I just want to make
sure that you guys account for this. So I
think I already done that one, OK.
Yeah, I just want to make sure that
you know all three of you are working
closely because that is linked with my
schedule or logic, right? That's why I
stored that data. No, this is not the
scheduler one. This is the ETS.
No, whenever we submit the lead job
right, we are calling the model and
getting the getting the list, it's
reactive list_at that time only we need
to store. No, no, no, just restoring
you know Vishwa store When we get
the lead we right away we call
the API. Yeah. We wait for the
response and we store, then schedule
comes next, schedule it comes next. And
it's all this morning from, from this or
you can see, yes, yes, everything is very
closely linked, right? I think even 1
developer can do it all in a week, right?
But since we have 3 developers, which is
the good thing. OK,
that's fine, that's fine. I have
dependency on that one because that I
don't have tested right. So that's why
I, I OK, yeah, if that's if
you have make sure that you get
in a call and make sure that
you are everyone is aligned right that.
This is how we are doing it right?
Because if you have already made the
change, then I don't want malaise to to
redo it. OK. So just make sure if you've
done something, yeah. So everyone please
work closely right? Send each of these
updates. Hey, if something is not clear,
everyone's cool, you know and I'll share
I have shared that in the chat in our.
Group call right in our group chat I have
shared so we have this service right? So
the response is going to be the Jason
output that we can see the job ID right?
Web pages is what you would use your API
to find the record and insert the data
which is the score and the priority list
which is again. Whatever
you want.
For that, but it also if you can
just create a 0 for data science if
you want, which is really cool. So
especially if you like sometimes they'll
go out, but just create one working. And
so you'll want to know like the CDN
is getting all these things, whatever.
Reached. So then it will be the
Northwest. And if you can invite me to
that project because I don't think I I'm
included in that one, then it will be
good. Right. So do you
want me to create a user story on Jira
and then, uh, uh, you can create a
surplus for those? Yeah, What am I
looking? You can users high level
history. You can create that. We are
working on data science story. That
machine learning model needs to be
trained for intelligent. You can just
write it and then I'll put a fill up the
details and everything. Thank you the
subtask. OK, done.
I'll do that now, yeah.
Sure, sure. Yeah. So, um, we,
we will stick to, uh, sending
the notification for the users who
are not in the list but
are active in DB.
That one, but but the question is um.
Do do we send to
those users, uh, whether or
not we have the, uh,
touch members list? I mean,
let's say you have two
lead based, we are returning
the prayer list site.
So we are trying to rewrite them like
one of these, right? What if both are
busy I mean. The
important thing is sent to 5:00 and 2:00.
They're not busy. So, OK,
so we are getting so you
can check this, right. So we
are trying to reroute them only.
So basically the data model, it
gives you the best on the
job. Yeah, that that what I'm
saying is on top of.
One is under here, probably look
into, let's say, uh, the active
torch members from the DB as
well. Where are the team? Let's
say if anyone here, let's say
for the sake of simplicity, right
take of the argument, I have
just two VPS, right? SO12345. Right.
Is 1. So this this one. So this is
the best one? Yeah, and this is the
second best one, right. So there's
treasure it out. He is available. Good
job. The lead just goes to him. He is
busy. Either he's in a second call or he
is inactive, he's offline or anything.
The leader goes to this one, right. And
ideally in an happy path yeah, I just
need you who knows I don't know what data
should be up to date with all the VPSS
A1 garage has all right so I would just
do model is not going to be trained and
I would check off right so there can be
instances when we when. And
bought a new VPS and he or
she they are not part of Ayesha's
model right yet. So in that case
if one is busy 2 is busy,
what you check is this table technician
table where this VPS is true technician
ID not in right and. Active.
So in that case my deal will
go to the wrong person also, right?
So because in the database we
are looking at right say I
have the top five. Not sure
what we want. What the best
method?We
definitely want to know who's active in
that case. Right.
We may want to send this exactly. Well,
we know that these two are the best
ones, right? Anyone after this, they're
equally the same. That's the whole idea,
right? So something you know, so we might
want to do it with that just so
we know that it's continuing to be down
for 345. 6 and 3456 all are active, so
it does not matter if it goes to yeah,
you have 5 or 6 in any random order. You
can run your query right, get active.
Just get the limit one, there's one and
assign it to it. It may not be necessary.
We only know that one and two and the
technician that's pretty 3 is as good as
4. What is as good as long as you're
getting sick?We don't have any
data for those and just so we don't get
as many points as many of our services as
you can. We have the CD one CDN here
at our main website and now you're doing
the testing we would need. You know we
need to know about the live production
model. So that is so that now 3. Fiber
now seasoned professionals, we would get
the data for 345 as well. One thing that
you and all you do is you know as you
could always call the data the connect
token. We need to retrain the model on
the live server or the testing that we
have which is the login sequence and just
try to get back a response which would be
you know. The user not
found something like that. Yes, they
are. So, so I think something
we're picking from the database, right.
So for the business, right, we
have to rewrite the right person
to close the team.
But yeah, and that's exactly what this
is. So this is going to give us that.
This is a secondary dollar grant. But if
both of them are busy, it's our bad luck,
then we just have to go through.
For the heart. It's
10 minutes from testing, 10
minutes. Right? Nobody will even
know that it's not working.
Yes, yeah, maybe we'll get
this clarification because consider this
scenario, you have 12345 and
345, whatever right for. Some
reason, maybe, uh, notification went to
them, but they, they, they didn't respond
right. But, but again, back, maybe I'm
done with that request because if they
can't be reactive, then we're going to
get back at different. Consider a
scenario waiting from the database. You
have 4404 or 500. Like that
if you feel sequentially send
notification to those 4-5 active users
from DB, it will delay that amount of
time once again, correct Right. Yeah I
mean if if none of the four, so
I would do that which will then then
you from having to add any API.
The tokens are correct. It will go to
that guy. It's so didn't accept. Then
there will be a delay once again, I think
that, uh, this priority guy, you know,
sending the notification to the priority
guy. So better to put this program right,
so doing the business. So Matt and Steve,
I guess let's look at some of the.
So that's why, that's why you consider
this scenario. Maybe for some reason,
they might have not, uh, you know, uh,
attended, uh, but but the next second or
maybe four or five seconds later, they,
they want to have that assigned to
themselves. True to that, that can happen
now that again, the question to business
then. If you really want to just keep
looping between these two and hope that
one of them become online, Yeah, And you
have 45678910 in the queue who are
getting paid and not doing any work. So
like, what should we do? Like we like
that. That's an assumption that that
you're making, right? That is an
assumption that you're making that, hey,
12345 will become online. What if they
don't? You cannot keep looping between
these two, right? If you have people that
are free. So first priority is this. If
he does not answer this one, if he does
not answer, then 3456 in any order
because I, I am a customer, right? They,
they tell me, hey, you will get a call in
10 minutes and I'm waiting for 30 minutes
then. I will not take that call, right.
The thing of it is we can confirm with
again with Ellie, if model tells you that
one and two are the best closers, but
both 1 and 2 are busy, what what do we
do? We don't do anything. We just have to
go with 3456, right? Because it's better
to if I tell you that you will get a call
in next two minutes and you don't get a
call for the next 30 minutes. Would you
take the call? No, right?Makes
sense. Yeah, Yeah. Because I mean, it's
true. It's true that, hey, he was busy.
By the time we get to three, one is
available again. Yes, we just, we missed
it. But it's we cannot. But we, we don't
have any way to know that when number one
will become available again, right?
There's just no way to know that, right.
Maybe he's in a call and after the call.
He gets tired, he might set himself to
active or inactive. He it's his lunch
break, he has to go to the bathroom,
right? Makes sense. So my suggestion is
you run its course one, then two. If both
of them are busy, then 3456. Now 3456
they don't answer. It again comes to 1.
Right, yeah um, yes, I think
we need to try uh exactly.
It's a whole cycle, so each
have to run its course. Yeah,
because, uh, so again, so so
if I'm trying 12345 not available,
right? If I go database right,
I may not. Get the right task
number for this date.
So, yeah, I mean, they, they can
go any which way, uh, depending on
what the business needs. Yeah. Because so
we need to, uh, I think repeatedly
tried this. The
routing in the jobs itself that this
stuff for list of class members who
which comes from the model.
Umm, yeah. So those I think yeah, let's
keep it simple. Let's just go with this
order, right? And then we can obviously
refine further, OK. Otherwise we if we
just gonna keep thinking what if this is
then we just won't be able to do
any dev work. Yeah yeah, OK, so.
Yeah I do have to drop though, but any
questions or anything but for now we are
clear on the tasks.
Yeah. OK. So what are
you going to available tomorrow?
With water. You're asking
me, I'm sure. Yeah, yeah. Otherwise I
will check in my code. You haven't
take a look at my branch. And
so it suggests a saving part, processing
the thing and you can send that
file or you can take a look
at if you want to give some
feedback. You can give it will let me
talk. That we send those
details so you can use this as your mock
object OK I put that in our chat as well
so for this decade, right yeah uh request
model so new response and insert right
whoever's doing it Malish or Vishva, you
can I put it in our group chat right? So
we can access it later right That this is
going to be the mock. Project. So you can
use this mock object to create your
insertion update your repository right
and then, uh create your query to insert
the data here using yeah so you OK,
cool yeah so again we'll check in with
you all tomorrow see the progress I hope
to see some PR's come in and then
you're saying something.
No, no, no, no. You cutted the branch
from the release. What is the release
branch? Can you tell me the branch The
let me just go here. So there is
a release branch. Started
from there. So you get that store
called lot of so which one is
it? Which one you guys uh, uh,
I'll I'll be dropping you. Can you
guys continue? Yeah, maybe yeah, yeah.
Which one? Which actually, Yeah, yes, it
really is. Yeah, yeah, yeah, I see.
Yeah. You see my screen, There's, there's
multiple branches. So release scorecard,
feedback address only release, only
release. Second one,
I believe, guys.
No, no, no guards scorecard. Just a
minute. I'm going to pin that once.
This is the report right towards.
So just a minute, but right now I'm going
to.
And Vishwa or Malaysia or anyone create a
feature branch where we would need to
merge the code too. I'm looking to create
tomorrow. OK so so this is the uh
ping us the release branch will create a
branch out of that release branch.
Yeah, yeah. I just, uh, I'm
bringing in the group chat. OK,
OK, yeah. Umm
uh yeah, I don't know already if you
can see here. I put the JSON here
already.
OK, OK, you said OK, it's release
over here, let's release all. OK, so
everyone, I'm putting this here in the
chat, right?Right.
This is the branch, right? So use this
branch, right? Uh, Anthony visa Malesh
branch from this branch, right? Use this
Azure based branch, which will create a
feature branch, put it in the chat and
create your PR to that feature branch.
OK, I hope to see some peers come
in by tomorrow, OK. OK,
alright, then, uh, Malaysian, which we've
talked to and which on the testing
procedure on how we can test these
cases, like when the queue forms, uh,
basically ideally shares what you should
do is you should connect your automation
to the Postgres DB. You should be
able to see the score. Make sure that
the scheduler is working correctly. So if
I have 10 records in the table and one is
available right that the first one rings
first, then the second one rings first
based on the score and time. All those
things OK. It's not.
It's already uh. So my one
is uh, uh, pulling the data
from the database based on the
highest score and sending that priority
list to the websocket service system
built from there.
He's going going to take that,
uh, he's going to implement the
logic. Yep. Anthony, are you good
on that?Umm.
OK, perfect. That's alright. Tomorrow we
should not be in confusion. Yep, exactly.
So I've shared the response, right, Mock
example, I've shared the release branch,
right, that you need to branch out which
which share the feature branch and let's
create some peers there. OK, cool.
Everyone good. Any questions for
me, I have to drop. I have a meeting,
but yeah, I'll talk to you all tomorrow.
Ping me. Let's any questions, anything.
Any conversations you're having, I would
suggest have the conversation in the
group chat so that everyone is in the
loop. OK. Right. Yeah, yeah. Alrighty.
Talk to you all later. Thank you. Yep,
Yep. Bye.