I'll find that. To see screen there. Oh, yeah. That's good. Okay.

So like we said, for the project, it started as a POC, then it turned into a
project itself. Right? So when AJ entered, we we were in v one. And then they also
had non p o is what I've heard. Non p o was there that time also.

Then after some some hiccups and problems, then they decommissioned the version one
non p o, which is utility. Then last year, they came back to us for, utility with
some extra demands. And, what we did is we started the non p o project for them in
week two version. Okay? Which was mostly, I think, SARSD, AJI, Sonomi.

This all was on was on YouTube platform. That is when I think I came I came into
Sareen. I was not there. So I came in with SARSD and then also took over AJI. So
when this AJ project was going on, actually, like I told just based on some
customization, they wanted their name, their color, things like that, which we
easily achieve.

But from a user perspective, I found a lot of gap because I'm also new to the
system. So every time when they ask a question, I didn't have an answer. So I used
to go back to him say, I should go back to Titus. I used to come back to Prabha. I
used to keep asking questions because I'm new.

So that is when I came to know for some things, there is no answer. The they like,
even the team will say that, oh, yes. This is the gap. Maybe note it down, and you
will fix it later. So one time, I was talking to a big man, big man told, okay.

So whatever idea you have, you start putting it. We'll have to put it into a
design. Right? That's it. So that is the genesis of this design.

What are you saying is came through that discussion with Vigna where he told, if
you really think, a new UI with added user centric features. Right? So everything,
that we do here should be configurable. The user should be able to, you know,
enable or disable that that level of custom custom we can achieve. Then that he
said that will make sense.

Just changing color and, not changing things there and there. What's the point?
Right? You then you are not technically, you're not achieving anything. Just
whitewash and you put new weight.

That's it. So that was the goal. This was the, base he give. So then he told, we
need I said, we cannot do this alone. We need to get some new AI with developer.

So I think he reached out to Roshan, and Roshan assigned, one of those. So Mona was
working in Power BI politics, and then she she was moved into Serena. So she's also
like, she's just completely new. She doesn't know anything. It was that she doesn't
know anything.

So, there was training sessions for her. I was connecting with what is Serena, what
is PO bills, what is introduced, all those kind of discussion and sessions here. So
basic level of understanding she had, what Serena could do. Then, we start. So
everything that you see here, it is like, I will I will say she will do.

So, for example, if I am, like, okay. I put the upload button top. That's all I
will say. So how would you look? How would where it is?

She likes to Yeah. That is that she will do because that with her experience and
with, her, what she's seen so far, she will take care. What I will give is a
skeleton saying that, okay. I will put in my notebook. I will write down.
Okay. Summary, render. So that was a design earlier. Everything else, color
scheming, shadow, everything she would take care. Yeah.

So then, because this all started from now, so I put my focus under, non PO, which
is the service based utility. Right? This normal bills that we receive. So in this,
we brought these categories. Process you need to tell it.

In the non PO process also how we are doing it. Okay. So today, when we say utility
bills, I hope you know what the utility bills are. How we are processing for our
Dubai alpha UA clients is that, there are two good examples like they want at least
a lot to empower, etcetera etcetera. So the good thing is when there is no two
factor authentication, right, what we have, like, a code through SMS or email, when
that is not enabled for these portals, but to so not to Adi and it is still not
doesn't have two factor authentication.

But so if, let's say, I give credentials of our client to put that in product and
market, we just need to use the name of password. So these kind of portals, we were
able to achieve and, let's say, automatic login and download the latest build
approach. Right? So Titus with using selenium, all they built is that we will be
given account number. For that, we will have, credentials.

We'll have user and password, which is included. Okay. He will take this. He will
go to the particular website. He will enter it's a manual.

He didn't say it is. It will enter the username password. It will search for that
account. It will see if the latest bill is available in selenium format. Let's say
if it is already available, then it will not download anything.

So duplicate. But if the latest bill is new to us, then then we will download it
and we'll bring it into selenium. Then comes in the OCR, then the Google, etcetera,
which we will get written. But that is the basic, you know, between, I think for
Gallandari also, this was the Yeah. Tag.

Send you a claim from that to Yeah. This that the idea, like the idea. So that is
what has flourished today into the YouTube audio. But then came a challenge for all
this with two factor authentication. It's currently says, Serena cannot bypass that
stuff.

Right? So Yeah. We can. I don't think I'm not ventured into that as of now. I'm
trying to you need to comprehend this one OTP for that.

But, I think we can do that in, but I can say again risky. Like So what's Yeah.
This in the case we can do. I did some projects with cookies with their name. Is
it?

I was asking Vigna. For example, how how they give us dedicated email to four email
ingestion. What if this email is registered for the OTP, and we have access to that
inbox? Yeah. That also we can do.

But then you just leave that's taking additional risk. So what we have Yeah. It's a
district. Right? So now what happened?

Let's say we achieved this, but then one final we are not able to do everything for
the entire person from that one is saying that you promised you will download from
this website, but you're not doing it. No. If we have the one TP, no Mhmm. Then
directly we can directly we need this to get the cookies. Like, when you log in,
like, there's, credential is stored in cookies.
Correct. So with that cookies, we can directly log in. That's what I did some
setting in bytes using Python. But every time it'll ask for OTP? No.

No. No. If you use the cookies, no. It will have, like, generally, if you open
Outlook in one time login, you will do right. Oh, yeah.

In browser. Similar. That's what I did. But, if you put it back in VM now, then we
need to check how it will behave. I generally just do it in a local system.

Yeah. This is running on servers. So. Yeah. Then we need to check like whether
cookies are saved or is it getting?

Oh, that's a file. We'll store them cookies in a file. Oh, yeah. We'll just add
that file into that Selenium to read that. Oh, so you're accessing that cookie?

Yes. By using the cookies, we'll just, Chrome driver, no drivers, web drivers. So
we'll just add to that and then it will access. That's what I did for my, projects.
As a problem, that is a blocker.

So two factor authentication, whatever is that we are unable to bypass. So what we

do, we request our clients to send these invoices in bulk. But once the particular
service for, let's say, two, we cannot bypass. Then we'll say send all the two
invoices in one email to a dedicated email. So let's say, now for AJA, they are
assigned AJA, [email protected].

That's the email. No no other emails will come into that. It's only for Sabrina.
And what Only for AJA. Only for Exactly.

It's client specific. And it is created by them. They don't have access. We don't
have access. All that we do is they have to consider, we will take their client ID,
client secret, and tenant ID so that we will get the read access of this inbox.

Yes. Right? So that's how it works. So whatever invoices come, into this so there's
not invoice. Any file that comes into this inbox, we will download.

We will start those. So that is how we process the two factor authentication bills.
Thirdly, there's a third way of uploading, which is the, the upload, literally the
upload button. You can click on upload manually. But the constraint here is,
especially when it comes to non PO invoices, because of the sheer amount of
invoices that account, nobody's going to sit and upload on.

Right? It's not possible. Every, like, every, entity might have is, like, thirty,
forty bills per month. That is also I'm trying to over simplify it. Yeah.

Right? That is right. It's more generally. Okay. So So nobody's gonna do that.

So they'll be what is the value? If I'm just going to do this, I might as well,
I'll go to the app with that. Right? So much time they're spending. So everyone
goes for the email approach only, but they try to automate it using, the.

So far, is it clear? Is it any doubt? Is it not? No. So far.

So this way, doing anything. Alright? There's no say enough. We are then we do also
is able to achieve this. And in this this thing, there is no change to this
process.

They're uploading was in there. Right? We can move to two files instead of, you
know, voice. We can mention uploading my other upload files. So what will happen to
you can direct upload the folder for that the invoice file?
We had earlier. Right? Which one? Bulk upload. But then we removed it.

Bulk upload. What do you think? One PDF. One PDF. One PDF.

One PDF. One PDF. One PDF. One PDF. One PDF.

One PDF. One PDF. One PDF. One PDF. The same as email only.

No. But email will be placed one by one, right? No. That's the risk we have
currently as of now. Like you, it will work, but sometimes if there's sometimes
sound then, it will be a trouble.

Like, currently, if you use upload now, you can see instantly the data. Like, what
are the the CR data in, you can see. Well, there is one invoice. Only one invoice.
One time.

I mean, at that time. Yeah. So we see it. This also can include the touch mask.
What happened?

So it's based on their what are they? So let's say they're they're from the local.
They're selecting one entire folder itself. Mhmm. Often with this.

So sending it through, we can limit email at also like, but it will take a lot of
time, right? User to sit and then it upload. That is their risk. Like, let's say I
have 50, You know, like, but they were sorry. It's around a hundred pages.

Mhmm. So if you upload all pages, how much time will take? They need to wait wait
right until it is uploaded successfully. That's right. So now let's say we need to
upload one invoice.

It must be one MB. So he's saying that until the entire folder upgrade up uploads
have to wait. And then also we are not going to show the result, I think, it will
go to batch. I understand. So that that uploader is options.

Yeah. That's all. Let's say if we have one or two invoices, then now if any, the
bot didn't run for three minutes. So the supporting team longer and then let is
they'll upload using this. Okay.

That's like a feature. I'll upload that. Okay. Okay. Yeah.

So, to I'm starting from the beginning of this. So I just want to say that in this
design so for one second that that getting downloaded for to mail that that
automatically got up to upload it here. So what happens? Yeah. What what I have
understood is when we download it is going to blob.

Right? From blob, we are picking what is we're doing OCR and whatever it is, we
will need it into, the front end. So we are reading from the email. Then we are
sorting into clop from blob. We are Yeah.

I missed. But that process is not gonna change. We this in this design, because
that is actually like an external thing connected to Serena. We have not made any
change to the voice because nothing can be done as of now is what I understand.
Right?

And it's working. Honestly speaking, it's when it works, it works. We have not an
app we've not had an issue with it. But when it after the invoices has landed in
Serena's when the the drama starts. Right?
When people start saying that, the multiple thing they're saying, I'm not able to
trace. I'm not able to understand. I'm finding it difficult. Right? The more it's
it's like user is finding it difficult with an old UI, like, how to navigate.

Right? It might be because they are not spending enough time. Right? Because when,
initially, when I came in, like, difficult. But today, it is natural for me.

I know where things are. So one, they are not spending time. The second is second
point is actually connect to the first point itself. Why are we not able to retain
users? Right?

And I think that clarity, we are enabled for a strategy. Right? The average use
time, no, that screen is I I think only one or two users, telephone and someone
because that is their job. Right? They do if they don't do it, they get fired.

So they are forced to do it. But we like, why are we finding it so difficult? If
they can work with the system like ERP, which is very minimal. I understand it's
minimal. It works.

But we have a robust, well looking UI like this. We should make sure that our users
are retained inside. Our reread is very less likely. And also brought the clients.
You know, maybe it must be better.

You know, see, you know, me, it's I think they are using started just recently
recently. No, but that started using. Oh, yes. Until then it was the APT module was
doing. This screen looks so beautiful.

Yeah. So this is actually actually the screen. I feel this empty screen. I don't
know. It's just static.

So what happened is when we started, we need to start somewhere. So Yeah. So she

just put commit. So so probably, let's say now, we'll go from we'll go step by
step. Model activation.

So model activation, what does it know? There is no activation. Model activation,

nothing. What is it called now? Something.

Just a model Yeah. And model activation. Actually, it was something it was model
creation. Yeah. So initially, it was model creation because if I don't know if you
know, we have we have moved to the open area.

So even we had the day day of course. So the day of the approach, we always go and
bug Titus. Is he already is Titus and all having already worked? No. Mhmm.

Titus is not. Okay. Because Titus is the one who's headache, this depression.
Right? So he's like the bottleneck.

Anyone anyone needs anything regarding, the amputee or utility, it always comes to
it. So once you're in the meeting, that more of music, it is a particular model we
are going to design with the condenser world approach. That's what he's say. Yeah.
That is the word approach.

Exactly. Meaning exactly. So from all our previous claims, we'll have a master
model, which has, like, so much data. Okay. It will have so many different fields.

So whatever kind of invoice you throw at it, it will it will almost it will extract
the values correctly. So what we do, we just take this master model and just paste
it, paste it, paste it. You can show that configuration. You will have the top.
Take that one.
That's fine. So so that 3PM meeting will be skill. So 02:30 of the institute. So
they spend their time. Yeah.

I have a nice What's the with you for notifications that you told me. Oh, the Ah,
that Reventing. I haven't discussed on workflow. It's not a case. And workflow is
so is funny.

So is also there. But it's Everybody put it in, mono. Notification next week. You
come more often, man. What about you?

Yeah. Yeah. Just the baby. The thing is, we are going at full speed. Okay.

Let me He has to do the time resource first. He has to do. Because he completed
recon successfully. It's good. Oh, that's the assignment.

Yeah. Good. Good. How did you have, like, any feedback retrospective to us? No.

No. No. No. No. No.

It's not good. Anyway, it's good. So so, yeah. So let me scary on. Yeah.

So so, this model. So what we used to do is to even now we have that. We are
completely moving to opening for utility, only for PO based. You guys have a one
separately. I haven't got it on.

Sure. Sure. Sure. Sure. Yeah.

So you added Yeah. I think that you don't Yeah. I should yeah. One moment. Which?

No. No. I have a. Yeah. So one master model with this copy into all clients.

So let's say we have a demo master model. We'll copy that model into now let's say
new client. Let's say AJ. We'll copy that and then that model, we will replicate to
different entities. Let's say 10 entities are there within AJ.

There are 10 accounts for I mean, sorry. 10 entities that have multiple accounts
under each entity. Right? So for DevOps, so we will just copy the model and keep it
in, conflict portal. So this is the approach which we're currently also following.

I don't know what's it. I don't know why we are not moving to is testing or this.
No. Currently, there is no person to, like, we need to assign someone to add the
tags, but they have a HR tax required. Everything is ready.

You just need to add the tags and then they need to write this prompt. No prompts.
Yeah. Like for each description, they need to provide for each tag. What is the
description?

I think we are depending on Jiten for that too much. No, no, no. Jiten is done for
a few days since he knows that like which tag is required. What is the description?
Yeah.

But for non people, he don't know like, what, but they are also be there. No, no,
no. Type and add supporting. We just need to add the tags, whichever tags are
required. Okay.

Then we need to add each tag. What is the description? So based on that description
only, it will extract. It will extract. So that they need to add that, description
or not.
It's I think pretty much, is that we just need to add the tags and we just need to
change. That's it. Yeah. So the opening is still we have not implemented by
Infiniti. So as a pro this is what we do.

We'll take one master model, and we used to migrate it. So that is where this model
creation term was brought in by Neil Bohner because we had to create every time he
say, you know, for Algura food, we want to create a Deva model. So then we used to
click on like, we were like, okay. Let's click on Deva for Algura food and then
create. That's what we should because this one, if it has to be done by Titus, I I
mean, install this task, he has to allocate some time, run my script, migrate, then
test it once, then he'll say, okay.

It's migrated. So we ask that why can't we move the dependency completely away from
him and keep it in the front end? And let's say tomorrow, someone from the client
itself wants to do it. They can do it. They don't have to reach to it dot seven.

Great. So that was the approach. Yeah. But one question, Arun. If you I'm able to
see different service products.

So these are the dependent. Like, if I choose the if you wanted to the like, any
minute multiple. Yeah. Yeah. So I think in the new designs is gone top.

Right? So this is where where the product pointed out that this cannot be, Yeah.
Like, whenever you click it, it should show them. I can't understand. That's what I
see.

Oh, okay. Yeah. This is gone. This is outdated. What you see is not how it is.

Because Pradha pointed, we missed it. He was like, when when I click, they were
here. Here, it'll get a what? Only four four records are there. That's So we cannot
show this in a table.

It's wrong. Mhmm. So what we did, we we put this thing and then we put it here. So
it's a round of you can tell it totally one at a time. And then we give the same
swap feature here.

So they could swap between entity or service product. Yeah. Okay. But then good. If
you have those class, but this is not the latest decision.

Okay. There is actually, it's already done it. Okay. So let's forget about this.
But the idea.

Right? So we were like, we'll create. So then the thing suggested that this model
creation concept is not going to be there for us. Mhmm. Now because now we're going
to move away from the AI to open a model.

Can we go to open a model? There is no model creation. Right? We just upload.

Because That's it.

That's a trend. No. Because We don't need to train. Doesn't matter if the client is
Praca, Bargo, or Zapthik. Everyone are getting the what is it?

They were all the same. Yeah. They're all the same. Yeah. So it is like having one
master model, which you already trained.

So it doesn't matter. So, yeah, the time you select Deva, we know in the back end
what is getting selected. So you feed the invoice for that, it will be mixed up
because we have the prompts. Like, it's Suggested tag names. That's it.
There is no Completely based on? Tags. Whatever the tags we added or the
description based on that, it will directly not click. Litigation. Those are excel
exceptional cases.

Yeah. So, yes. But, so then as for their let me say, when you put that, feedback,
we changed it from activation sorry, from model creation to activation of the
active. So let's say tomorrow, someone is saying that we are no more using these
entities. So then we would like to deactivate.

That's it. So activate the active. So we are just giving them I guess if they don't
don't have to today, if we have to do this, we have to go to the DB, make from one
to zero. Like anything. Yeah.

Change change of like, simple. I know it. Right? The support team of person has to
learn it, and still they're reaching out to them. Right?

Like, they wanna do it. They'll do it. Maximum dependency, we should reduce on us.
Let them start up. We need to reduce the DB usage.

Yeah. I heard, like, I see. Again, I'm I'm new to product. When I came,
immediately, I was given DB access. And I I used to learn, like, something, you
know, in the that we have done something on front I have done.

Okay. That is in, I remember Kim saying, I think when told that told nobody should
have DB access. Why is anyone playing in the DB? Right. The DB and the Like, how is
the I I'm a be why should I have DBs?

Same. We have the doubts. Like, we don't have any control over that. And something
will happen. Everyone will reach out to them.

To you people saying that something went wrong. There is no log. There is they
don't everyone is having common log. Same. Yeah.

As the main back. It goes into, fall back. Everyone has something has to fix. So
these are the issues, basically. So once this all goes live, probably we will
restrict access to everyone.

Nobody should log in. Yes. Right? If it is so critical, only then we should reach
out to people like you can say a lot. And then there's everything should be so this
should be our our head headlight.

Right? Everything should be done through UA. Right? Right from, be support.
Everyone should be able to do, on the basis of access.

Right? So if he's a test, what he's seeing should be different. If he's entity
user, what he's seeing should be different. So on that level, we can control.
Anyway, so that is that is why these kind of features you have got an activate,
deactivate.

So this, we can swap also if they want to select, bulk entities or bulk service or
all that. But this this is more optimal. Yeah. Okay. Just any doubt that you Okay.

This is so after this model, where it will maybe use this moment. Right? So where
we are And then you will have to this. I suppose if we create one, like, we'll
select some some some some. So in that model, have separation.

That is a good question. So what I'm just thinking. So this know what we have
created, to be honest, if you want to see, there is a different website. That's
interesting. That's incorrect.

No. That's what he's asking. He's saying, like, no. Like, what we have created.
Mhmm.

Here it is. Just the accurate, accurate, and accurate. That's it. That's it. If you
actually want to see what is the prompt, what is the description?

But are you seeing that access to clients? Yes. Yes. No. No.

No. No. They based on that access would be like Are they based on place? Yes.
Customer super admin.

As of now Gandhirational portal we have on portal. So there you can see what are
the tags we have, what are the descriptions we have. Models also what are the
Models concept to forget about models. Model concept. I think I'm logged in here.

I just Yeah. You can open that. I'll tell you the credentials. What is it? PHG?

Dev. I found config. Displace iPhone config. That's it. Any portal, if you want to
access, you can just put iPhone config, -config.selenapros.com.

This one I logged it. Yeah. Credentials. Same. Both.

Yeah. Yeah. So, this one is based on both. No. This is not still the idea.

We can do this data. This is also I've been a reference. That's all right. Oh,
yeah. Okay.

So this is what we have today, which is the ones you are saying, model based.
They're ready for every entity. So, you know, for Deva Yeah. We created this
channel. I did.

Again, for the one more Deva, I would find for this entity. Yeah. I did. But from
OpenAI, what we're trying to do is one vendor will have, what is the approach we
are taking here? One vendor will have only one, with no.

Everything is on global model. Everything on global model. But if you want to

change any specific vendor, then you can come here and you can just change to a
custom prompt. That's a different concept. So Right.

Because no further, if you would view this. Right? So every vendor wants same
details, like invoice totals, subtotal, unit price, quantity, everything is same.
Right? So mostly, double prompt will work.

But in terms of satisfied, no, global prompt won't work. Technically, we need to
add, like, why because they will have different, tags. It is a lot of different
tags. Everything is different different for each service provider. So this is what,
we were saying about global and custom.

So in global, it is like pretty predetermined. We're saying that mostly 90%, ninety
five % of the invoices will see these are the things we generally need to process
and invoice to Syria. All these things that you see are tagged in. And like he told
each tag will have a description. So that openly understands exactly what to pick,
right?

So So this is the global prompt. Meaning, in this prompt, we are speculating that
most of the invoices will get, you know, all of these tax would get picked if it is
available. Supposedly, let's say something fails. Let's say, the unit price is not
getting picked. Whatever you do, whichever you are trying to be able to is not
getting big, then we will become custom, and then we will change the description.

Now we will start making it post specific. We will be might say that unit price is
right next to quantity Right. See, you know, we are we are trading the model.
Right? So this is pretrained model.

Then now we are giving more insights to the model saying that, okay. Fine. You'll
find it right next to quantity. Okay. Like, drum thing.

It's only fine different. Yeah. Or you'll find it under the PRN something. Right?
Then we will pick.

That's a that's a trial and error method. That's what I understood from this. Trial
and error only. Yeah. Because we don't know what that is speaking.

So we just like connect. Yeah. It's a kid we are trying to reach. That's it.
Simple.

So the same thing. No. Think from Deva Deva, perspective. In global and what we'll
have, we'll have generally, what we'll find for, like, customer ID, sorry, tier
number, address, electricity, water, this. So all of those will be will define
here.

And and it's a description. So because this data bill is saved for the entire UAE
region. Doesn't matter who the client is. If it works for 90% works for everyone.
Unless, like, how we told now, day before yesterday, we got something new for this
irrigation.

I never saw irrigation in the until they estimate. We were I I I was able to work
irrigation, but it is and it's a huge amount. We completely missed it. Okay? The
because it is not picked it.

Yeah. We never bought it for a way. And last 02/1980, bro. So you don't want to be
missed to to to completely missed it. So and we we go live.

It's in production. So we were like, see, we were first of all, they didn't use the
location. I'll let you know. It's their problem. Yeah.

They gave only for water. So we picked water, we send water. And they're like, but,
this bill is supposed to have irrigation. Then we were like, your stapler has not
given us irrigation. Then then they both had a Okay.

Anyway, so I'm just trying to say that so these are the surprises we might have.
But the good thing is then we should, update that irrigation in the global league.
Because tomorrow, that might come for another client. That time we should not
Customer. You should custom?

Why? Because there is no concept called global in satisfactor. Yeah. Everything is

custom. Everything is custom in satisfactor.

Why? Because Okay. But they were tax is different. But say what tax are do
different. Different.

That is correct. That I will know. I'm I'm say depending on, on a provider itself.
Yeah. Single provider means it's a customer.

No. You're you're thinking in a different way. But here, global weeks, same tags
will be a form. That's what I say. Everything is a test of, but we are thinking to
have some import option.

Okay. We'll just download this, whatever this is there. Then we'll put it to let's
say this is we added for MR. We want to add it for a strategy. So we'll just put
some download button, which is upload.

Export it. Export it. That's what we are thinking. Like me and just kinda was
thinking, let's put some button to download all these details. Mhmm.

Then we'll just import that instead of copying it through VBR scripting, download
it and then import that. That's it. Good one. So one question, I think. I suppose
one electricity, and that is it.

First of all, I'm speaking of electricity company. So when that even that'll be
like demo, so five people are using same company details. Right? So the invoice
will be same. Right?

Like, the fees might be same. Right? No. No. So that's different.

Right? No. No. So Deva is the company. Okay.

Dubai Electricity and Water Authority. Under that, they are giving things like
electricity, water, etcetera. Now let's say AGI is reached out to Deva saying is
give us a connection. Mhmm. Oh, okay.

They Well, like, how long, for example, data data, some of this is paying for the
SCOM See. Electricity. Like Okay. I thought individual directly taking connection
from the electricity domain. No.

I understood. No. So this device in middle of this No. Device is the company which
is providing electricity. So device is best form.

Oh, okay. Okay. Okay. But if we have this form solely electricity, there they was
giving multiple things. Not only electricity electricity water.

So now to add to that point, now AJ is the main company, parent company. It will
have multiple entities. Yes. So sometimes two and two or more entities might share
the same, element on the same part. For example, now marketing department and our,
external department both are sharing one room, it seems.

Then both will get allocation fifty fifty. 50 percent there is there. That's the
next topic. Yeah. That that is the, you know, advance.

We are getting into it, whatever to say. So that that concept is there. Cast
allocation. That's the next question. Yeah.

This model we find it. Yeah. So that is, independent for the each. So no. What,
what I've said is only correct.

So what we will do is you know, when we when we get no AJ as a client and we say
Deva, we will we will probably keep the tax specific to them. Yes. AJ as a whole
company will have, Deva common. Right? As a company, it will have common.

And what that Deva will be the same. Right? But if every client across the the
world, so they will generate only single build. Right? Format in the same.

The tags will be same. So we can just do the same format. That was probably where
the export import from here. Very helpful. Yeah.
The initial setup we can do in queue basically. Yeah. So I mean we stop the index.
So the background setting. Calvration is done.

So this is clear from all the activation, deactivation. That's all. We are just
let's let's say the or let's say something what happened, they will they would have
activated only three. The rest of that comes, they'll say we'll activate it. One
question is here, like, that model is running in back model, like, how was it that
is passing in the PO based invoices?

Exactly. Uh-huh. It just schedule them. Okay. Scheduled it.

Like, how it will take the dates, like, model how it is running. It's in a pure
based, it is processing, like, the 2% extraction, like, required fields. Oh, you
mean the rules? I think that's what he's asking. Like, you mean what, how would
he's expecting?

Oh, they are clearly we were able to see. Right? Like, guys. Status. Directly.

This in the progress, but you're able to see. Right? Now that progress The system
check-in progress is happening now. What is happening there is asking the back end?
Where is the back end model?

The same. If you're whatever you're seeing in print and that's I can also ask for
it through. It's gonna click once, invoice got uploaded into the blog now. Mhmm. So
we'll just pick from there.

Just pass it the same. Everything is Yes. Awesome. So that is this is the way we
started first. Okay.

The first screen. So with model activation, then we move to account handling. So
now let's say we have for AJA is a parent company, we have 10 entities. Yep. Right?

For 10 entities, now let's come to first entity. First entity is having maybe 10 of
let's say, five service providers. They want to so for each service provider, there
are multiple accounts. Right? For example, now let's take data semantics as a
company.

Data semantics is having, HR department, sales department, marketing. Now marketing

team is saying, we need 10, Airtel accounts. Airtel new numbers for doing phone
calls. Okay. So now that entire thing is going under, data semantics company.

Entity would be marketing. Account would be Airtel. Under that sorry. The provider
would be active. Accounts would be the 10 account numbers, the mobile numbers.

Is this clear? Yeah. So that that 10 account numbers, we have if you have to feed
it into setting up, this is where. My prototype. Yeah.

This this this this started. Now you will show it will go now more, This is very
real. This is the biggest pain. If we can achieve this because there are so many
rules here. I had written here one set of rules in this room.

Yeah. According to uploading, we're doing DP on it. No. No. Why you didn't say
again?

Bro, I can do like two bytes. You we will not have DBX. No. No. Once again, we have
Excel app, right, title now itself.

We can do that using Excel. Right? Excel, I'm actually not sure. Oh, yeah. I have
You don't have.
I have used them, but I'm not introduced. Yeah. That I have you have showed during
training. I have I'm sure. I'm sure, but I told them what happened now.

This was during the SRG time. When I did, what happened? Few of the cost allocation
got missed. Then is when Mandari told me, if it is having more than one allocation,
you cannot do to excel. Mhmm.

You have to still go back to DBM. Okay. Okay. Okay. Then it's like, what the hell
is?

I don't know. Even I don't know. So I just like, what do you mean I went to be?
Because that yeah. You have to go.

I don't really it's like can't. So You see, again, we have forced to. Right?
Cititis will not sit and do this this cost allocation. Support team only has to do.

So now they got access. Now support team might have doubts because it's a new
client. So then they'll give back to be it. Now I got access. Right?

It is reached to a point where is asking access to DB. And then what? Right. I
said, do you have access to DB? Probably.

Where do you have? And it's like, no. No. No. Well, access to the product.

You say, well, I really will change everything. You know, $1,000,000, I will change
this. You know, this technical bug. Yeah. He's How can we provide that?

Let's let them be the creator also, but then anyway, this is this is the what is
happening so far. So when we come into account onboarding, currently, our team is
using the DB onboard method. Basically, we have a predetermined template. We will
enter the data. I have, like, four, five Excel files are there.

In each table, we'll go and we'll import. That's what we do. So I'll just add in
there. I think in DB, you know, you can just use the current device. Right?

It is working. Not why you are Device is a single single account you can add right
now. But that will come more time. No. But they're adding, like, we're adding bulk.

Bulk bulk. No. One if it is one account, no. Then we ask the client only to do
Yeah. Within the UI, which is fine.

Which is fine. That does not change, I guess. Even in this design, it is just a
look and feel what is changed. But the company can tell on the moment. Team that
they won't do because waiting to production is our problem.

After we are gone live and they're saying everything is okay, then it is their
problem. But still there is dependency. For example, no irrigation. What will they
do? See, this is the gap.

What will they do? Right. Yeah. So, anyway, coming back to this, so, we all have DB
access. We are trying to reduce this or no DB access to people like us.

So for that, we need to optimize our data entry within UI. Within UI, it will be
load specific. Exactly. Correct. So this is the second module, which is for
specific entities, specific service portal, we are going to add accounts.

So if I were to click account, add an account, like, this is how, brother told me
we can add an account. Okay? But what here we did is we are not restricting them to
add one account. We can add more than one account also. Let's say they have Yeah.

That's good. You said they can have mobile They're like, okay. Then I I don't mind
handling it manually. If I'm good for you. Okay.

But let's say if it is 20 or 40, maybe if it is two or one also, we have given
excel upload method method, which is next. Okay. We'll come to that again. So now
here, if you can see, we have given them an option to enter account. So from here,
if you have any doubts, stop immediately because this is the very important part.

Okay? Account number we are adding, then they're, selecting the let me say the
entity name, entity code. We can automatically populate. Yeah. Okay.

Yeah. This is why it's coming to you now. We should automatically populate the
entity code, PRN select service for it. Now this is user reset required for and
PRN. So By adding that one.

What is the need of that? See the code we should have PRN. By by four by Because
sometime, no, it's very similar, these names. Uh-huh. It's very similar, especially
Marando, you go mad.

Oh. 73 entities. Then they provide. Yeah. Fine.

So that Yeah. Maybe not required. Here, actually not required. We can remove. Okay.

Okay. Then, obviously, the service product itself. Right? So you're selecting now
they wanna say, no. And then there is more.

Mhmm. And then you would automatically as per that, combination, service for I
mean, entity to service provider, automatically, we'll have to populate the server
portal code. Okay. It's not done in the deal. That is also not required.

Actually not required. That is also not required. This all should just happen in
the back end. Because in back end, this is not required. That is why this in the
front end, we are sure.

That is, I think, internal. That is not no need to display here. No need to
display, but we need to make sure this It is there. It is there. Oh, is it there?

Then, no comes account. So I actually remember when I told Titus is using selenium
to download these invoices. So this is where you give the account you are you're
telling for Deva, go to this part particular URL to log in. So we are asking them
to enter the login URL. One.

Okay? Then we are asking them to enter the user in a password. Okay? There is not
as of now, it is not, from the UI perspective, it will we can put stuff just as I
don't know. But when it goes into DB, has to get encrypted.

Yeah. That we will handle. I will tell you what, sir, Titus is doing. It is there,
Alan. Encrypted is there.

Yeah. Through the DB method is getting automatically integrated. The DB method is

what is we are doing it now. If you upload from UI, it is already happening. Is it?

Okay. Then no worries. So that's handled. And this salary is there. You don't need
to worry about this.

Then so so much it is the account level information. Now comes what I tell you.
Here's the master template. Right? That model template and master template for '37.
The model model is different. This is a my accounts. No. No. That is that is,
actually, there is, that is totally different.

That is level let's say that is on a provider level. This is on an account level.
Under each provider, like I told now, Airtel will give you 10 account numbers.
Right? So the 10 account numbers, each account number belongs to whom.

Okay. What what is the cost allocation like he said? That is what we will
definitely want. Okay. So, so now coming back to the most important thing, which is
cost allocation.

So what is cost allocation? Like I said, you know, data semantics as a company is
having marketing department. Marketing department to do or sales calls, they're
asking for 10 active numbers. They're telling that one number one number is shared
by two people. Okay.

Okay. One number is shared by two people. Let's say. So then this cost has to be
let's let's say, Kartik and Maroon are sharing these numbers. So then if you go to
Kartik's, account 50%, so volumes are going to 2,000.

That level of granular detail is very centered. Now this is a very oversimplified
way of what I explained. But, you know, on a ERP level, if you take this is how it
would look. Entity, part center, product, project. So these are the things these
are part of financial dimensions, but this is with respect to dynamics actually.

Again, Oracle and Snap and all, I'm not sure. No. We are changing the names
according to the according to that one. I have written some, modification. Is it?

So I put in sporadic, then we have to get displaying those names. If it is

dynamics, we are displaying those names. So data is same. The way they are calling
the names is different. That's exactly So I knew.

So for me, dynamics are pretty much okay. But SAP and Oracle, I'm I'm a complete
stranger. Right? So even I have to learn. But this is This is the same as
different.

The way you say. Is it? Yeah. So just understand this this before or what we're
showing here is based on Dynamics three fifty five. Right?

So these these are the things necessary to do cost verification. Right? For one
particular account, if one person has to divide that, let's say, the amount which
is come the bill has come for that particular month, These are the things required
within dynamics for them to currently divide the amount. Okay. And how do we put
that?

For example, now here, the element factor is The element factor. So you're they're
putting 50% then so, you know, this this is where the rules keep in. Right? So he's
putting for electricity 50 and if he submit, right, we should not allow. Because if
50 is there, that is the other 50.

These are the rules. And there's a validations. They're validations. Right? That's
it.

That's it. We know it. When we see, we know it, but how will the system know? As of
now, we don't have. We have.

We have, I think. One no. But, do we have? What? Like, if it doesn't tally for one
Currently, we are adding only one.
I think not hundred of if it's starting one. What? Indeed, we don't have any
scenario. Maybe we can have we can never add because We can only control that.
Yeah.

We can't control that on a d b l. We should control that elsewhere. Suppose if we

look at the 50%, if we add add, add cost allocation, so there he can add 50. Right?
So it will come.

No, that's not a block. That's a UI violations and the API violations. You're
right. Let's say without clicking submit, he clicked on add task delegation. Next
one will come.

And here he added everything and give one more 50. 50 plus 50 is hundred. How much
are the rules that they're like that? Like this No. No.

No. This is not a rule. There's a violation. 50%. It's a violation.

Let's say to make sure that one element, for example, this is an element. Right?
Even again, let's meet to meet you. So actually, no. Good.

Okay. Let's electricity. When he when he or she is choosing electricity as element,

that should all that elements element factor should always tie it to %. Okay. So if
it is a % by the faster location only, then I have valid then one more one more
validation.

Now let's say he's adding one more element and saying electricity. Then we can't We
cannot. We should not allow this. That those are validations. We don't know
exactly.

This is, like, common sense. Yeah. But the common sense. Then we we don't
understand. But how would system understand?

No. These are This is very high for deep level, right, to each point. And I'll be
very honest, that that much amount of thought I put into this because clients are
making mistake. Okay. They're like, system didn't say, okay.

They won't feel bothered. I think we will be doing that. Exactly. This Stefa, they
are not I'm not doing I'm not doing. They they only give 200%, and we would have
done it.

And they'll be like, no. You don't have common sense. You're receiving two lane
with hundred and for us it'll happen. No? We by mistake, we made a duplicate entry.

Because we are in a hurry. Right? We have to do but when when they are doing it,
you know, and the system is saying no. You already entered the city's hundred. What
are you trying to do?

No. Actually, the issue was initially, we got a partial location sheet. Their
account number was different. Then we got a revised sheet, account number was
changed. Oh, yes.

So there was a missed, like, you know, data data Data mismatch. Mismatch. So it's
by the way, that the same. But in the inventory, you had a throw in exception
first. Then we had to change that.

I said, to be honest with that one. Right? So that is so then they can enter
everything as cost center product this one. But anyway, now let's say, they enter
for one entire account two, three it will go up to nine allocations also. It's up
to them.

They can keep adding and then submit. Right? This is for user. Right? Yeah.

No. Deletely. So the ones who is not working in d b, d b are the person. No. D B.

No. Why D B again? We are the No. For D B. Okay.

When they are giving us the partial location sheet now, we have to do it everything
management. Anymore. They have to directly. Excel upload with them. Excel.

You you if they give to you, then you can just upload. You come to the UI and then
you can also connect. Exactly. But then they that's what I'm saying. They shouldn't
come back to us.

We are we should just keep us operation like your water delay. In Serena, we treat
that problem we have. But in 3.1, we have to try to fix it. Oh, well then That's a
d p you are trying to do. That's why it is accepting.

D p you can do. Right? There is no problem. But when you do through Excel, we keep
up. % allocation, we can do.

Mhmm. But if it is more than I mean, if it's less than %, then it will throw
another. Not a error. It will only take one record because according to it it will
remove all duplicates. It will keep holding on record.

And it'll be issue also. In your cost allocation, when you go and see, only 15 will
be there. Rest of the 15 will not be there. Anyway, it's okay. No problem.

So coming back to this. So here, he has added one line. Right? And let's say he's
adding another line. A moment a moment.

He's adding basically, he's just adding account numbers, and you can see rest
everything is simply. K. So he's added three more lines, and, they've added the
account number. Now what feature we did is, what we were thinking is now that he's
added the data for the first line, what we have generally seen is for one
particular entities, service story will most likely have the same possibility.
Okay.

Right? And to be honest, it might even come under the same login. Right? That user
in browser. So that then flourished the idea thinking why can't we just select that
role?

Copy data. Just click it to put on, basically Just select what you want. I can just
copy this. In Excel, we will subtract. That's it.

That is the idea, but I know how we can achieve this. Right? We can do. We can do.
So then, see, I'm just doing selector.

This is for demonstration purpose. I'm selecting I want to sell that select service
program. Okay. In the same cost on the patient, same credentials. So you can
instead of creating certain tasks.

So we are fooling so forcing them to enter. So they'll be thinking But this is

good. This screen, like, this approach also good. So no. I've seen this because in
AJ, Reshma, that when she told, and why are forcing me to type everything once
again?

Like, why can't I do? Because she's working next time. I am the one doing in DV.
Yes. I will.

Next time get this done. She's pulling like this, like this, like, and she's like,
Harini, you know? I said, no. I'm then I share my screen and she's like, then I
think the new Google UI. She understood the pain.

So that that is when I got this idea. So then you are just selecting, okay, for
which accounts you want to paste the data. You selected that also and apply when
you apply. Then repeat it. Now, also, I have seen, it might not be dictoreta.

Sometime what will happen for each of this account, they might have to go inside
and change things. Few things. Yeah. All center might be different. Yeah.

This yeah. It is down there. Yes. Not this. So that is so you have reduced % of
workload to 20%.

Or something you will be low. Anyway, high value is what I have understood from
this. But like you said, if this is possible, this will be amazing. Yeah. This is
possible.

Possible. Decide launch is required. Maybe the click change is required. I'll let
you. No.

No. Then, the main thing is in the case. So I think that that's it from this page,
I think. Thank you. So I'm loading the system.

So we do it now. That is a certain point. So it's blurred, so I'm not selected

something. Mhmm. So she's given in this one, right, so we don't know how fast she's
able to get.

But something I have to pick. I don't know what, but something I Select the. I
think she select the But this is not required. I don't know. Not required.

No. Not required. Oh, yeah. Not required. What do you mean select all again?

This is happening. That's why I told her, to remove that, I think. She might have
thought if you want to edit sometime, we'll come after an edit. It. The better But
the problem is we are not saving that.

Yeah. Whatever you see, we'll go. So then when you click on submit, this is the
next next step because we again introduce something new. If you can see, we are
onboarding our accounts. Click on you to know your status.

This is currently not there in selling as far as I know. Right? No. We will see if
you uploading you. I know.

Oh. Now itself, if you are, there is no errors. We don't see any errors. Not
actually. Yeah.

So when I can call you Are you here? You are trying to build me on approvals? No.
No. No.

No. No. No. No. No.

No. No. No. No. No.

No. No. No What errors you see? No. No.

Errors coming to that. So one thing here, Raghu, we introduced bats. This is new.
So whatever it will be just on the came into a batch. That's pretty.

And you're seeing it as a single person. No, we don't get this type of, in
progress, direct upload instant. Or how much of our accounts it is? No, no. Through
a single approach we did right through UI through Excel.

This is required. Is it? Yeah. Yeah. Yeah.

Right. Because we are verifying already in three details according to the service
provider. So what error do you make just think what error we can get. That's a good
point. Okay.

I just see there are a few errors. What we thought of. One is service per okay.
That is not possible. It's not possible.

It's not possible. It's not possible. If it is UI upload, it is there is no error.

All validations are we are doing itself in the screens. Like if the, cost
allocation validation, everything we are doing there.

Only in cell it is bulking. Cell only in that. We will get this kind of validation.
Like these errors, like if they put some random things, then they need to validate.
That's where this helpful, very helpful.

In v one, we have this. Oh. In v one at this time, there we are, like, non UI.
Okay. Whatever the errors downloaded.

No. We are just sending them as a back Excel rejected. Oh. In Veevan, we I think we
can I don't feel it? If not email, you send it download.

We'll send them. In Veevan, Lokendra and me, I think Lokendra, I think Lokendra
worked on this earlier in Veevan. I think back three years ago. Okay. And that's a
good point.

I think not required for any case of failure, just like that. That will go there
only that we do there there only in that screen itself. Generally, only APIs are,
that kind of error will get. So, Pardag, is this creating the cost to DBL? Yes.

Yes. Now then we have only issue will

#and this is from team transcript for above content so u can compare and sync

OK. So like we said for the project, it started as a POC, then it turned into a
project itself, right? So when the AJ entered, we we were in V1 and then they also
had non pu is what I've heard non Pu was there that time also. Then after some some
hiccups and problems then they decommissioned the version in one non PO which is
utility then last year they came back to us for utility with some extra demands.
And what we did is we started the non PO project for them in V2 version OK.
Which was mostly, I think, SRV AGI Synonymi this was on was on YouTube platform.
That is when I think I came I came to sagging. I was not there. So I came in with
Srz and then also took over AJ. So when this AJ project was going on like I told
just based on some customization they wanted their name, their colour, things like
that which we easily achieve but.
From a user perspective, I found a lot of gap because I am also new to the system.
So every time when they ask a question I didn't have an answer so I used to go back
to keep and say as you go back to titles I used to come back to Pratham Vikna
everyone I used to keep asking questions because I'm new.
So that is when I came to know for something. There is no answer. They like when
the team will say that, Oh yes, this is the gap. Maybe not it down, maybe we'll fix
it later. So one fine day I was talking to Vigna and Vignan told OK so whatever
idea you have, you start putting it. We'll have to put it into a design, right?
That's that is the genesis of this design. Whatever you're saying is came through
that discussion with Vignan where he told if you really think.
A new UI with added user centric features, right? So everything that we do here
should be configurable since the user should be able to, you know, enable disable
if that. If that lot of custom custom we can actually you then that he said that
too makes it just changing colour and changing things there and here what's the
point right you and then you are not technically or not achieving anything just.
Whitewash and you put new paint. That's it. So that was the goal. This was the base
he gave. So then he told we need. I said we cannot do this alone. We need to get
some UI works developer. So I think we reached out to Roshan and Roshan assigned
Mona for us.
So Mono was working in Power Bi's and then she she was moved into Serena, so she's
also like you. She's completely new. She doesn't know anything A-Z. She doesn't
know anything. So there was training sessions for her. I was connecting with
Serena. What is PO based? What is all those kind of discussion and sessions? Yeah.
So basic level of understanding she had. What Serena could do then.
We start so everything that you see here, it is like I will, I will say she will do
so. For example if I am like OK, put the upload button top, that's all I will say.
So how would you look? How would where it is placed that is yeah that is that she
will do because that with her experience and with her what she's seen so far she
will take care what I will give is a skeleton saying that OK I will put in my
notebook I will write down OK summary and.
That was design.
Everything else, colour scheming, shadow everything. She will take care. OK, so
then, because this all started from NAVIO. So I put my focus under NONPRO which is
service based utility, right? This is normal bills that we received.
So in this we brought these categories process we need to tell them it will not be
OK process also how we are doing OK. So today when we say utility bills, I hope you
know what a utility bills are, how we are processing for our Dubai, our UA clients
is that there are few good examples like Deva at least a lot to empower right et
cetera et cetera.
So the good thing is when there is no two factor authentication right what we have
like a code through SMS or e-mail when that is not enabled for these portals.
Do so. They were, end it is still doesn't have two factor authentication but so if
let's say I give the credentials of our client to log it, we just need to use
password. So these kind of portals we were able to achieve and let's say automatic
login and download the latest build approach right? So Titus?
With using selenium, how they build it is that we will be given account number.
So that's we will have pretentions in our user name password which is encrypted.
OK, we will take this. He will go to that particular website. He will enter it's a
whenever I say it is selenium it will enter the username, password it will search
for that account. It will see the latest build is available in let's say if it is
already available then it will not download it. It's a duplicate but if the latest
build is new to us then then we will download it and then bring it into then comes
in the OCR.
Rules, et cetera. We which we'll get into, but that is a basic know I think for
also this was the yeah Tag Serena came from that. Yeah, this that the idea like the
idea so so that is what was flourished today into the utility module but then came
a challenge for for this with two factor authentication because currently Serena
cannot bypass that step right so.
Yeah, we can. I don't think I'm not ventured into that as of now. I've tried. We
need to configure this from OTP for that, but I think we can do that in.
32nd risky. Like so what's? Yeah, in the case we can do some projects with cookies
with is it? I was asking vign for example. Now how they give us dedicated e-mail to
for e-mail ingestion. What if this e-mail is registered for the OTP and we have
access to that inbox. Yeah that also we can do but then he was like that's taking
additional risk. So what we have to yeah it's a risk. Right. Right. So now what
will happen let's say we achieve this but then one final we are not able to.
The entire person will come back from saying that you promised you will download
from this website, but you are not doing it. No. If we have the know then directly
we can directly. We need this need to get the case like when you log in right
there's stored in book is correct. So with that book is we can directly log in.
That's what I did some savings using by them. But every time it will ask for OTP.
No no no no. If you use the cookies no it will act like generally if you open
outlook.
One time login you will do right. Oh yeah. New browser yeah similar.
That's what I did. But if you put in that PM, no, that we need to check like how it
will behave. I generally test and I just do it in a local system. No, this is
running on servers. So yeah that we need to check like whether this server will get
saved or is it getting no, that's a file we'll store in a cookies in a file. Oh, OK
we'll just add that file into that selenium to read that. Oh, so you're accessing
that cookie. Yes. By using the cookies we'll just.
Chrome driver, no drivers web driver. OK, so we'll just add to that and then it
will access.
That's what I did for my projects, as if not that is a blocker. Yeah. So two factor
authentication whatever is that, we are unable to bypass. So what we do, we request
our clients to send these invoices in bulk or once a particular service provider.
Now let's say do we cannot bypass then we will say send all the invoices in one e-
mail to a dedicated e-mail. So let's say now for AJ they have assigned AJ.
[email protected]. That's the e-mail. OK, no, no other emails will come to
that. It's only for saving. And only for HDA only. For ad exactly. It's client
specific and we just created by the devices. We don't have access all that we do is
we have to can say we will take their client ID, client secret and so that we will
get the read access of this inbox. Yes. Right.
So that's all we books. So whatever invoices come into this. So that's what he file
that comes into this inbox we will download. We will start those. So that is how we
process the two factor authentication bills. Thirdly, there's a third way of
uploading which is the the upload literally the upload button you can click on
upload manually. But the constraint here is especially when it comes to non peer
invoices because of the share amount of invoices that come, nobody's going to sit
and upload.
It's like it's like just not possible. Like every entity might have this like 30-40
builds per month. That is also I'm I'm trying to over simplify it. Yeah, it's it's
it's more generally OK. So nobody's going to do that. So they what is the value if
I'm just going to do this and might as well I'll do it ERP directly, right, so much
time they're spending. So everyone goes for the e-mail approach only or they try to
automate it using.
The so far is it clear?
You see any doubt is that no, no. So far. So this we are doing anything right this.
V2 also is able to achieve this and in this design there is no change for this
process. There upload invoices there, right? We can files instead of you know OS we
can mention uploading VS or upload files. So what will happen to you can direct
upload the folder. What are the invoices available for that we had earlier right
which one bulk upload but then we removed it bulk up lot.
What do I think? I don't. That's that is a badge for not in bulk. It's not in one
PDF. Uh, huh? Yeah. PDF in one. Just because directly folder upload 4050 folder
upload. Oh, that will be again that is same as this one. Only e-mail only. Yeah.
The same as e-mail only. No, but e-mail one by one, right? One by right. No, that's
that risk we have currently as of now like you it will work.
But sometime, if there's sometimes then it will like currently if you use upload
now you can see instantly the data like whatever the CR data rate you can see there
is only noise. There is only one invoice for 10 at that time. Yeah well we see.
This also can include that option of what happened from the serving based on their
whatever. So let's say they're they're from the local, they are selecting one
entire folder itself of invoices. So sending it through we can limit e-mail that
also like. No, no. But it will take a lot of time, right. The user to sit and then
it upload that is their right risk like let's say I have 50 versus.
You know, like Vadhava, sorry, Excel or not, there's 100 pages. So if you upload
all the pages, how much time it will take, they need to wait, wait right until it
is uploaded successfully.
Yeah, that's right. So now let's say when we are uploading one invoice, it must be
one MB. So he's saying that enter the 10 pads folder upgrade uploads. You have to
wait and then also we are not going to show you something. I think it will go to
batch and you understood. So then that option is no that is only for that except no
let's say if we have if not two invoices then now if any at the bot didn't run
through e-mail. So what the supporting team longer and then let is they left on
using this.
OK, that's exa feature like we'll upload that.
Yeah. So.
To start you from the beginning of this. So I just want to say that in this design.
So one second that dating download from Hotmail right that automatically got
uploaded here. So what happens? Yeah. What what I've understood is when we download
it is going to BLOB right from BLOB we are picking which is we are doing OCR and
whatever it is we will need it into the front end. So we are reading from the e-
mail then we are storing into BLOB.
From the BLOB, we are just sending it.
But that process is not under going to change. We this in this design because that
is actually like an external thing connected to Serena. So we have not made any
changes because nothing can be done as of now. What I understand right and is
working honestly speaking, it's when it works, it works. We have not an add. We've
not had an issue with it. But when it after the invoices has landed in savings when
the.
The drama starts right when people start saying that the multiple things they're
saying I'm not able to trace, I'm not able to understand. I'm finding it difficult
right? The more it's it's like user is finding it difficult with an old UI like how
to navigate right. It might be because they are not spending enough time right?
Because when initially when I came and I felt difficult but today it is natural for
me. I know where things are so.
One, they are not spending time, the 2nd is, second point is actually connected to
the first point itself. Why are we not able to retain users right? And I think that
clarity we are enabled for SRG right? The average use time? No that screen is very
less. I think only one or two users telepen and someone because that is their job,
right? They view says that if they don't do it they will get fined. So they are
forced to do it. But we like why are we finding it so difficult if they can work
with a system like ERP.
Which is very minimal. I understand it's minimal, it works, but if we have a robust
well looking UI like this, we should make sure that our users are retained in say
our retainability is very necessary and not from other clients. Maybe it must be
better. So I think they are using started this recently. Recently. No it does
started using Windows.
Until then, it was the only was doing just.
The screen looks so.
Yeah. So this is actually actually the screen, this empty screen, I don't know.
So what happened is when we started, we need to start somewhere. So yeah, so she
just put. So probably let's say now I will go from we'll go step by step model
activation. So model activation, what is it now there is no activation model
activation, nothing. What is it called now? Something. This is the model. Yeah,
model activation, activation activity. It was something. It was model creation. So
initially it was model creation because if I don't know if you know we are we are
moved to the open area right so.
Even we had the day, of course. So the day approach we always go and bug status is
he already with Titus and all that. We already worked. No, it doesn't OK, because
so Titus is the one who's heading. Yeah. This departure that's about he's like the
bottle. Like anyone needs anything regarding non PO or utility it always comes.
But what that means, if it is a model, we are going to design with the, that's the
world approach. That's what he's saying. Yeah. That is the world approach. Exactly.
Meaning exactly. So from all our previous claims, we'll have a master model which
has like so much data. OK, it will have so many different fields. So whatever kind
of invoice you throw it, it will, it will almost it will extract the values
correctly. So what we do, we just take this master modelling is paste it, paste it,
paste it 4 metres right we can show that configuration and we have the.
That's fine.
Once in a while. Yeah. Yeah. Then you guys are in calls then that's it. To connect
like this. If you think the purpose of.
Still on teams.
So that so that 3:00 PM meeting will be still 2:30 PM. So I spend their time.
Yeah. What's what? What time with you for notifications? That's you told me, right?
Oh, the that revamping I haven't discussed on workflow.
It's not the next flow so as.
Also there but before I go to.
Notification next week you come more often when.
What about you?
Well, The thing is this, we are going at full speed, OK, let me resource for this.
He has to come because he completed Recon successfully. It's good.
That's assignment. Yeah. Good. I think. Good. How did you have, like, any feedback
heterosective to us?
Good so.
So yeah, something that's carrying on. Yeah. So so.
This model, So what we used to do, we used to even now we have that completely
moved into play for utility only for PO based. We have one separate thing I will
call it 1 sure, sure sure.
Yeah, so you added.
Yeah, yeah.
SO1 master model with this copy into outlined. So let's say we have a Devo master
model. We'll copy that model into. Now. It's a new client.
That's a AJ. We'll copy that. And then that more we will replicate to different
entities, let's say 10 entities are there within DJ, there are 10 accounts for, I
mean, sorry, 10 entities around multiple accounts entered each entity, right? So
for Deva, so we will just copy the model 10 times and keep it in conflict portal.
So this is the approach which we have currently also following, I don't know what's
it, I don't know why we are not moving into it's testing. No, no, no, no. Currently
there is no person to like we need.
Someone to add the tags, but they were each are tags requiring everything is ready.
We just need to add the tags and then they need to write this prompt. No prompts
and yeah like but each description they need to provide for each tag. What is the
description? I think they're depending on for that too much. No, no no. Jitin is
done for POS since he knows that like which tag is required. What description yeah
but for non po he don't know. Like what they.
No, no type supporting alright like they know we just need to add the tags which
are the tags that are required. Nothing.
You need to add each tag. What is the description? So based on that description
only it will extract it will accept so then they need to add that.
Description Or not, it's I think pretty much is there, we just need add the tags
and we just need to change. That's it. Yeah. So the open AI is still we have not
implemented for utility. So as a proof of this is what we do. We'll take one master
model and we still migrate it. So that is where this model creation term was
brought in by me. And because we had to create every time we say no for algor.
Put we want to create a Deval model, so then we used to click on like we were like,
OK, let's click on Deva for and then create. That's what you should because this
one if it has to be done by task, he has to allocate some time.
Migrate, then test it once, then he'll say OK, migrate it. So we're just like why
can't we move the dependency completely away from him and keep it in the front end
then let's say tomorrow.
Someone from the client itself wants to do it. They can do it. They don't have to
reach Arena, right? So that was the approach. Yeah. But yeah, one question are
here. I'm able to see difference at this prototy. So these are dependent like if I
choose a favour with the like multiple. Yeah. Yeah, yeah. So I think in our new
designs it's right. There's. This is where Prada pointed out that this cannot be.
Yeah, like whenever you click it, it should show that it's sent. That's what it
says.
This is gone. This is updated. What you see is not what it is because Prathap
Pointer, we missed it. He was like when when I click dev here here it will get
update. What will be 4/4 records are there. That's so we cannot show this in a
table it's a wrong. So what we did we we took this thing entire and we put it here.
So it's a round down you can select only one at a time and then we give the same
swap feature here so they could swap between entity or.
Service provider? Yeah. But then good if you have those class. But this is the
latest. OK, latest actually is already done it. OK, so let's forget about this. But
the idea, right? So we were like we'll create. So then jitin Pratapanam suggested
that this morning creation concept is not going to be there first because now we're
going to move away from BI to open AI model. Can we go to open AI model there is no
model creation.
We just upload because that's it. That's all because we don't need to train.
Doesn't matter if the client is pratha, bhargav or everyone are getting what is it
they were saying? Yeah. They were the same. Yeah. So it is like having one master
model, which you already trained. So it doesn't matter. So yeah, the time you
select Deva, we know in the back end what is getting selected. So you feed a
invoice for that it will extract because we have the prompts like you suggested tag
names. That's it. There is completely based off.
Whatever the tags we added, what is the description? Based on that we can directly
contact.
Those are exceptional cases. Yeah. So, yes. But so then as per their, let's say
only for that.
Feedback. We changed it from activation, sorry. From model creation to activation
or reactive. So let's say tomorrow someone is saying that we are no more using this
entities, so then we would like to deactivate. That's it. So activate deactivate.
So we are just giving them again. See, they don't don't have to today if we have to
do this, we have to go to the DB make from 1 to 0 flag yeah you need to yeah.
Change. Yeah change change the flag. Simple. I know it right. The support team of
person has to learn it and still they're reaching out to them right. Why?
Want to do? Let them do it. Maximum dependency. We should reduce honest. We need to
reduce the DB usage. Yeah, I heard like I see again. I'm. I'm new to product. OK?
When I came immediately I was given DB access and I I used to learn like something
you know in Dev DB. I've done something on fund. I've done that is in. I remember
Kim said I think nobody should have DD access. Why is anyone playing in the DB?
Right exactly.
Like how was BIIMABA? Why should I have DBS? Same we have the dot select we don't
have any control over that right? And something will happen. Everyone reach out to
them to you people saying that something went wrong. There is no log there is there
you don't. Everyone is having common log. Yeah. That's the main task.
Something has to fix, so these are the issues basically. So once this amount goes
live, probably we will restrict access to everyone. Nobody should log in. Yes,
right. If it is so critical only then we should reach out to people like you can
say unlock. I guess everything should be so this should be our our head headline,
right? Everything should be done through UI, right. The right from BA support.
Everyone should be able to do.
Well, on the basis of access.
Right. But if you set a still what he's saying should be different. If he say
entity you said what he's saying should be different. So on that level we can
control anyway. So that is that is why these kind of features you have gotten
activate deactivate. So this we can swap also if they want to select bulk entities
or bulk service or something like that but this this is mood optimal yeah. OK and
just any doubt in this is so after this model where it will maybe use this model
right so.
That we are getting other viewer after this. But suppose if we OK create one model
like we select some.
So in that model have separate.
That is a good question. So thinking so.
This now what we have created, to be honest, if you want to see that is a different
website that is in copy, that's what he's asking. He's saying like now like what we
have created here it is just deactivate, activate, activate and reactivate. That's
it. That's it. If you actually want to see what is the prompt, what is the
description? But are you using that access to clients? Yes. You agree? Yes. No, no,
no. They based on that access only like that only based on place. Yes customer
support.
As of now configuration Portal, we have one portal so there you can see what are
the tags. We have portal, the descriptions, we have everything. So what are the
model standard dev models? We don't have model concept. No we cannot show what's
not. No not that not config. Yeah you can open. I'll tell you the credentials. You
can open it in Ehg Dev. You can open eh Dev itself.
Yeah, isn't long been here? This. Yeah, you can open that. I'll tell you the
creations.
Do it PhD.
Dell iPhone config just place iPhone config. That's it. Any portal if you want no
EH dev, it's any portal if you want access so you can just put iPhone config iPhone
config that's dot on this one. I logged it here credentials same.
Yeah.
What do I just put that on sync?
So this one is based on both, no, this is not still DA.
Vendor vendors? That's open end. Yeah. Open end. So this is what we have today,
which is the ones you're saying model based. They get it for every entity. So you
know for Deva, yeah, we created just like that again for the one more Devi you will
find for this entity like that. But in open AI what we're trying to do is 1 vendor
will have.
What is approach we are taking here? 1 vendor will have only one no global model.
Everything on global model. But if you want to change any specific vendor then you
can come here and you can just change to a custom prompt. That's a different
concept.
So right, because no further. If you want pureness, right? So every vendor wants
same details like invoice totals, subtotal, unit, price, quantity. Everything is
same, right? So mostly global probably work but in terms of service won't work
technically we need to add led. Why? Because they will have different tags. It is a
lot of different tags, everything is different, different for each service
provider.
So this is what we were saying about global and custom. So in global it is like
predetermined. We are saying that.
Mostly 90 percent, 25% of the invoices will see. These are the things we generally
need to process and invoice through serial. All these things that you see are
tagged and like he told, each tag will have a description so that open a
understands exactly what to pick, right? So this is the global form meaning in this
prompt we are speculating that most of the invoices will get you know all of these
stacks will get picked if it is available.
Supposedly, let's say something fails. Let's say the unit price is not getting
picked. Whatever you do, how much ever you're trying to be approved, it's not
getting big. Then we will pick on custom and then we will change the description.
Now we will start making it more specific. We will, we might say that unit price is
right next to quantity, right or we would like see. You know we are we are saying
the product right? So this is pre trained model then now we are giving.
More insights to the model thing then? OK, fine. You'll find it right next to
quantity. Note right.
I don't think it's only different. Yeah, or you'll find it under the PRN. Something
right that we do think that's a that's a prior method. That's what I've understood
from this. Yeah, because we don't know what that is. Nikki. You know, it's like,
yeah, it's a kid. We are trying to teach. That's it. Simple. So the same thing. Now
think from Deva Deva perspective in global what we'll have we'll have.
Generally what we'll find or like customer IDs or ATR number, address, electricity,
water this. So all those will be defined here.
And and it's description. So because this Deval is same for the entire UAE region,
doesn't matter who the client is. If it works for one it 90% will work for everyone
unless like how we told now day before yesterday we got something new irrigation. I
never saw irrigation in Devakal until yesterday we were I I I was new to it
irrigation irrigation but it is and it's a huge amount we completely missed it.
OK, the because error has not picked it away. How much we would have missed? How
can we?
Suggest to the closely bigger 100,000 this evening 1,00,000 from 2080 rupees to
two.
And we gone live. It's in production. So we were like, see, we were first of all,
they didn't give the notification. It is their problem, their problem they gave
only for water. So we picked water. We send water and they are like but this build
is supposed to have irrigation. And we were like you are stakeholders not given us
irregular. And then then they both had.
OK. Anyway, so I'm just trying to say that. So these are the surprises we might
have, but the good thing is then we should update that irrigation in the global
because tomorrow that might come for another client that time we should not
customer we should custom harisha why? Because there is no concept called global in
service FEDER.
Ation is custom and satisfied. Why? Because OK. But they were tax is different, but
they were tax are we do different different. That is correct that no, I'm I'm say
I'm depending on on a provider itself. Yes single provider means it's a customer.
No you're you're thinking in a different way. Oh oh. But here global leads same
tags will be.
Same same, yeah, that's what I'm saying. If everything is a custom. But we are
thinking to have some import option, OK.
We'll just download these. Whatever this there, then we'll put it to, let's say
this is we added for Mr Hmm, we want to add it for SRG. So we'll just put some
download button, which is upload. There's putting exponent. That's what we are
thinking, like me and the same thing. Let's put some button to download all this
details. Then we'll just import that instead of copying it through DVR scripting
download here and import that. That's it.
Good 101 question. I suppose one electricity and that is it for someone. Speaking
of electricity company so.
Be like deva. So five people are using same company details, right? So the invoice
will be same right? Like the fields might be same right? No, no. So that's
different, right? No, no, no. So Deva is the company. So OK dwai electricity and
water authority under that they are giving things like electricity, water et
cetera. Now let's say AGI is reached out to Deva saying yes give us a connection mm
hmm. Oh OK then like how for example data semantics is paying for Bascom.
For electricity like that, OK, I thought individual directly taking connection from
the electricity main. No. OK. Understood. No. So this device? No. Deva is the
company which is providing electricity. OK, so data wise is best form. Oh, OK, OK,
OK. But we have this form is only electricity there. There was giving multiple
things not only electricity, electricity, water. Right. So now to add to that point
now AJ is the main company parent company it'll have multiple entities. Yes so
sometimes.
Two and two or more entities might share a same.
Uh element on same power for example, now marketing department and our department
both are sharing one room it seems. Then both will get allocation fifty 5050% they
pay that is the next topic. Yeah that that is the you know advance we are getting
into it. What I'm just saying so that that concept is there cast allocation yeah
this model we so that is.
Independent for the each. Ah, so now what subset is only correct? So what we will
do is no, when we when we get now AJ as a client and we say Deva we will we will
probably keep the tag specific to them. Yes AJ as a whole company will have Deval
right as a company to have common that is what that Dev Deva will is same right for
like every client across.
The world, so they will generate only single build right format in the same. The
tags will be same so we can just do the same format.
It's probably where the export import functions very helpful. Yeah, the initial
setup we can do in game. Basically. Yeah, right.
Yeah. So I mean we stuff, we'll go back to dot com setting.
S done.
So this is clear, the model activation deactivation. That's so we're just, let's
just let's say the OR let's say sometime what happened they would they would have
activated only three the rest of the accounts they'll say we'll activate later,
yeah. One question is here like that model is running in background like how OCR is
passing in the PO based devices exactly. No, it's just scheduler, OK schedule
scheduled it like how it will pick the dates like model how it is running. It's in
a viewer based it is processing right that OS here extraction.
Required fields, but you mean the rules? I mean, that's what he's asking. Like you
mean what? Uh Howard is expecting. We're able to see, right? Like that? Actually,
this and the progress. But you're able to see right now that progress that system
check in progress was happening now what is happening there is that in the back end
where is the back end model. The same if you're whatever you're seeing in print end
that's I can also Aspen in through the script like once.
Invoice got approved into block now, so we'll just pick from that, OK, just passing
the same everything is same.
Just same.
So that is the. This is the where we started first. OK, the first screen. So with
model activation then we move to account on the link. So now let's say we have for
AJ is a parent company. We have 10 entities. Yeah, right. But 10 entities. Now
let's come to 1st entity. First entity is having maybe 10 or let's say five source
powers. They want to sell. So for each service provider.
There are multiple accounts.
Right. For example, now let's take data as a company data. Somebody's is having HR
department, say department or marketing, no marketing team is saying we need 10.
Airtel accounts at 10 new numbers for doing poll calls. OK, so now that entire
thing is going under.
Data semantics company entity would be marketing account will be actor or under.
Sorry the provider will be Airtel accounts will be the 10 account numbers.
The mobile numbers is this clear so that that 10 account numbers we have if you
have to feed it into setting up this is very.
Micro detail level here. This is this started now we will show it will go now more
this way the real.
This is the biggest pain. If we can achieve this because there are so many roles
here I had written here one set of rules in this room.
We're in DPM. We don't. No, no, I did see again.
Bro, the next two we will not have dbx. No, no, no. One second, we have excel right
now itself. We can do that raising Excel, right? Excel. I'm actually not showing
the oh only I have videos you don't have or I have used. And then then I'll
introduce yeah that I have you have showed during I have I'm sure yeah I'm sure.
But I told them what happened. No, this was during the SRG time. When I did. What
happened?
Few of the cost delegation got missed then, is when Nandini told me.
If it is having more than one allocation, you cannot do to excel.
You have to still go back to DVD. Oh, OK. OK. OK. And it's like, what the Hell's? I
don't know. Even I just like, what do you mean? I went to vikla. Vigno said. Yeah.
You have to go back to DV.
D.
So see. See. OK. We are supposed to, right. See, Titus will not sit and do this. Do
this cluster location support team only has to do it. So no, they got access. No
support team might have doubts because it's a new client. So then they'll give back
to Ba. Now I got access, right? It is reached to a point where SRG is asking access
to DB. And then what I said is that Q access to DB.
And it is like, no, no. Well access to the product is like, no, I already will
change everything. No, you don't know one change.
You know this technical back? Yeah, he's. How can we provide that other person?
Let's let them be the Creator also. But then.
You know, this is this is the what is happening so far. So when we come into
account on boarding, currently our team is using the DB onboard method. Basically
we have a predetermined template. We will enter the data and like 4-5 Excel files
are there. In each table we'll go and we'll import.
It's what we do.
Adding in DB no. You can just use the current UI itself right? It is working OK UI
or UI itself single single account you can add right now but that will come more
time no? But they're adding like bulk bulk, bulk, bulk bulk no one if it is one
account node then we ask the client only to do yeah within the UI which is fine
which is fine that is not changed I guess even in this design it is just that look
and feel release changed but the account.
The only team, but they won't do because Q82 production is our problem. After we're
gone live and they're saying everything is OK, then it is their problem. But still
there is dependency. For example, no irrigation. What will they do?
See this is the gap. What will they do? Right. Yeah. So anyway, coming back to this
so.
We all have DB access, so we are trying to reduce this or no DB access to people
like us. So for that we need to optimise our data entry with the UI with the UI,
with the specific exactly correct. So this is the second module which is for
specific entities specific service provider. We are going to add accounts in so if
I were to click account, add an account like this is what.
We can add an account, OK, but what here we did is we are not restricting them to
add one account. We can add more than one account. Also let's say they are. Yeah,
that's good. You say that. OK, then. I I don't mind entering it manually. OK, fine.
Good for you. OK, but let's say if it is 20 or even if it is 2 or one also we have
given Excel upload method method which is next OK we will come to that. OK so now
here.
If you can see we have given them an option to enter a column. So from here if you
have any doubts, stop immediately because this is the very important part. OK
account number we are adding then they are selecting the.
We say the entity name entity code. We can automatically populate. Yeah, OK, this
is coming to you now. We should automatically populate the entity board, PRN,
select service provider Pro. This is user based. Is that required forward and PR.
So while adding that one, what is the need of that silly code? We should have PRM,
Wi-Fi or WI because sometime no, it is. It's very similar these names. It's very
especially you go mad, oh 73 entities then deployed. Yeah, fine. So that may be not
actually not required we can remove. OK. OK then obviously the service provider
itself, right. So you're selecting now Dev and say.
No. And then there is more.
And then you will automatically as per that combination service for I mean entity
to service provider automatically we will have to populate the service provider
port. This is not there in the deal that is other not required actually not
required. That is also not required. This option just happened in the back end
because in back end this scenario is required which that is why this in the front
end we are showing and that is I think internal that is not no need to display here
no need to display but we need to make sure this is there it is there is it there.
Then no comes a convert. So I remember when I told now Titus is using selenium to
download these invoices. So this is where you give the call URL you're telling for
Deva. Go to this particular URL to login. So we are asking them to enter the login
URL. What? OK then we are asking them to enter the user name and password. Yeah,
OK. This is as of now it is not from the UI perspective tool we can put **** and go
but when it goes into DB it has to get encrypted.
Yeah, that we will handle. I will. I'll tell you what's Titus is doing, right is
there, is there? Yeah. Through it is getting automatically integral. OK. The DB
method is what is we are doing it. Man. If you upload from Uy it is already
happening. Is it OK? No worries. So that's handled and this salary is there, you
don't need to worry about this then. So so much it is the account level
information. No accounts what I.
'M here to master templated that model template and master template template. Now
model is model is different. This is a my accounts. Oh no no that is that is
actually there is that is totally different that is level let's say that is on a
provider level. This is on an account level under each provider like I told now
Anton will give you 10 account numbers right. So that 10 account numbers. Each
account number belongs to whom? Oh OK.
What? What is the cost allocation? Like he said, that is what we will definitely
note.
Yeah. So, so coming back to the most important thing, which is cost allocation. So
what is cost allocation? Like I said, now data semantics as a company is having
marketing department marketing department to do purpose or sales. They're asking
for 10 acting numbers. They're telling that one number one number is shared with
two people. OK, OK. One number shared with two people, let's say. So then this cost
test will be let's say, let's say Karthik and Varun are sharing these numbers.
So then if we go to Karthik's account, 50%, sorry volumes account 50%.
That level of Wrangler detail is very central.
So this is a very oversimplified way of what I explained, but you know on a ERP
level, if you take this is how it would look entity entity element, Call Centre,
product project. So these are the things these are called as financial dimensions,
but this is with respect to dynamics actually again Oracle and SAP and all. I'm not
sure no we are changing the names according to the according to that one I have
written some.
Modification is it so if it is variable then we have to we are displaying those
names if it is dynamics we are displaying those names so P data is same.
They have. They are calling the names is different. That's exactly so. I knew. So
for me dynamics now I'm pretty much OK, but SAP and Oracle I'm I'm a complete
stranger, right? So even I'll have to learn. But this is it's the same access
different the way is same is it yeah. So just understand this this.
Here is based on Dynamics 365, right? So this these are the things necessary to do
cost allocation, right? For one particular account. If one person has to divide
that, let's say the amount, which is count that bill has come for that particular
month.
These are the things required within dynamics for them to correctly divide the
amount and how do we put that. For example, now here they remain factor is the
element factor. So here they're putting 50% then see now this is where the rules
kick in, right? So he's putting for electricity 50 and if he submit right, we
should not allow.
Because if 50 is there, where is the other 50?
These are the rules and there's a valid on that validation, right that's and that
is like we know it when we see we know it, but how will the system know as of now,
we don't have as of now we have I think one more, but do we have what like if it
doesn't tie for one currently we are adding only one I think not 100 or if it's
adding not UI in DB we don't any scenari.
We can have we can never add those. Yeah, because how can you control that? Yeah,
we can't control that on ADP level, so we should control that elsewhere. Suppose if
we were entering 50%, if we had add add cost allocation. So there you can add 50,
right? So it will come, no, that it's easy. Yeah. If it's up there, it's not adding
too block. That's a UI validation and the API validations, you're right, let's say
without picking submit, he clicked on add cast to location. Next one will come. And
here he added everything and.
5050 + 50 is 100 like that. No, no, no, this is not a rule. That's a validation
5050%. It's a validation right like 100% to make sure that one element for example
this is an element, right?
Element. OK, let's me to meet you. So she's not given goods. OK, let's say
electricity. When? When he or she is choosing electricity as element, that should
all that elements element factors should always tally to 100%. OK, so if it is 100%
by the 1st allocation only.
Then I have a valid one more, one more validation. Now let's say he's adding one
more element and saying electricity. Then we can't. We cannot, we cannot. We should
not allow this to that. Those are validations. So how do it? This is like common
sense. Yeah, that's a common sense because we see we understand. But how would
system understand?
These are pretty valid. This is very.
Each point, and I'll be very honest that that much amount of thought I've put into
this because clients are making mistake. OK, they're like system didn't say, OK,
they won't feel.
Nobody's there. I'm not doing it. I think we only doing that exactly at this step.
All they're not. I'm doing. They're doing they they don't give 200% and we would
have done it and they'll be like, no, you don't have common sense.
You're receiving two line with under and the first it happened we by mistake we
made a duplicate entry because we are in a hurry, right? We have to do but when
when they're doing it now when the system's saying no, you already entered it. What
are you trying to do? No. Actually the issue was initially we got a partial
location state there upon number was different. When you got a device sheet the app
one number was changed.
So there was a missed like, you know data data data mismatch.
Exception for us. Then we had to change that answer, to be honest with.
So that is so then they can enter everything as call centre product this one. But
anyway, now let's say they entered for one entire account 23 it will go up to 8-9
allocations. Also it's up to them. They can keep adding and then submit, right?
This is for user, right? Yeah completely.
So the ones which onboarding in DB would be other person, no DB no why DB again we
have that bro then no more DBA OK when they are giving us the partial location
sheet no we have to do it everything manually anymore. They have to directly Excel
upload excel you if you if they gave to you then you can just upload you come to
the UI and then you can exactly but then they that's what I'm saying they shouldn't
come back to us.
We our we should just keep processing like your water delay.
Roy guy in the simple right in, you know. Now let's talk on, say 250 accounts, for
example, 250 accounts were only.
It's not gonna where are excel adidia then you just now you told allocation. So
vandeidra mathra that's currently now in Serena V3. That problem we have. Hmm. But
in 3.1 we have trying to fix it. Oh, then then.
That's DB you're trying to do. That's why it is accepting DB you you can do right.
There is no problem. But when you do through Excel we came up 100% occasion we can
do mm hmm, but if it is more than I mean it's less than 100% then it'll provide us
not error, it will only take one record because according to it it will remove all
duplicates. It'll keep pulling on record and it'll be issue also in your cost
allocation when you go and see only 15 will be there rest of the 50 will not be
there.
Anyway, it's OK, no problem. So coming back to this, so here he has added one line,
right, and let's say he's adding another line.
Of the line he's adding. Basically, he's just adding account numbers and you can
see rest everything is empty. OK, so yeah. OK, so he's added three more lines and
they've added the column number. Now what feature we gave is.
What we were thinking is now that he's added the data for the first line, what we
have generally saying is for one particular entity's service.
Will most likely have the same cost.
OK, right. And to be honest, it might even come under the same login right? That
user name, password so that then flourish the idea thinking why can't we just
select that role?
Copy data.
Just basically just say whatever you want, you can just copy this in Excel. We'll
just drag. That's it. That is the idea, but I know how we can achieve this, right?
We can down, we can do.
So then. See, I'm just doing select all just for demonstration purpose. I'm
selecting. I want to select select service with the same cost of location, same
credentials. So you can instead of creating so we have so forcing them to enter so
they'll be thinking but this is good. This screen like this. So no I've seen this
because in AJ, Reshma that she told and. Why are you forcing me to type everything
once again?
Like, why can't I do? Because she's working excel. I am the one doing DB.
I'm she's pulling like this like this. Like she's like already know I said no, and
then I shared my screen and she was like then I was like, you do UA.
Obviously understood the pain so that that is when I got this idea. So then you are
just selecting OK for which accounts you want to paste the data.
You selected that also and apply. When you apply, we'll repeat it now also FC, it
might not be Victoria sometime. What'll happen for each of this account where they
might have to go inside and change their things. Few things our centre might have
be different numbers. Yeah. Based on their read based on this. So that is so you
have reduced 100% of workload to 20% or something even 0. Anyway high value is what
I have understood from this.
But like you said, if this is possible, this would be amazing. Yeah, this is
possible. Possible but.
Decide not change request. Maybe the keep change request. I'll let you.
Then.
So I think that that's it from this page I think.
Somebody, that's it. So we could that is assignment, but it's blurred, so I'm not
selected something. Hmm. So she's given in this one, right? So we don't know passes
that we care, but something I have to pick. I don't know what but something I
selected I think she selected oh select but this is not required I don't know not
required I don't already Oh yeah not required. What do you mean select all again
just that's why I told her to remove that technically correct. She might have
thought if you want to edit sometime we'll come after an edit.
Other than that process, only two. Yeah, but the problem is we are not saving that.
Yeah, whatever you see, here we go.
So then when you click on submit, this is the next next step because we again
introduce something new. If you can see we are onboarding our accounts, click on
view to know your status. OK, this is currently not there, right? So as far as I
hmm, right, no, we look if you uploading UI no now itself if you are there is no
errors, OK we don't see any errors. What is the error you were expecting so.
Yeah. So when I click on here, you're trying to put rules. No rules. No, no, no
accounts.
What errors you see? No errors coming to that, so one thing here, Raghav. We
introduced bats. This is new.
So whatever, it won't be just ongoing, came into our branch back split and you are
seeing it is single. No, I am saying no we don't get this type of in progress bar
it instant or yeah how much of our accounts it is no no.
Approach. We hit it right through UI through excel. This is required.
Yeah, yeah, yeah, maybe cuz we are verifying already entity details service
provider. So whatever you might just think whatever we can. Yes, it's a good point.
OK. Yeah. I just see there are a few errors. What we thought of one is service
provider. OK that is not possible that is not possible. It's not.
That's what? That's what if it is UI upload it is, there is no error, all
validations are we are doing itself in the screen Sir like if the cost allegation
validation everything we are doing there's only it is bulk sell only in batch only
we will get this kind of validation.
Like these errors or like if they put some random things then they need to
validate. That's where this helpful very helpful. In V1 we have this oh in V1 at
this time there we are like non UI OK whatever the errors downloaded. No we are
just sending them as a back excel rejected.
In V1 VI think.
Not e-mail. You send the download instant down and vivan, rakendra and me. I think
lowkendra's and I think Lowendra worked on this earlier in V1 heading back three
years ago.
OK, that's a good point. I think not required for nothing but any case of failure
just like that. That will go there. Only that will do. There. There only in that
screen itself.
Generally only API server that kind of error will get.
So paratha is this in creating the curse to DBR? Yes, yes, no. Then the only issue
will come.

Aaron F stopped transcription