Recording_280
May 07, 2026 12:39
· 1:34:41
· English
· Whisper Turbo
· 8 speakers
This transcript expires in 26 dagar.
Uppgradering til permanent lagring →
Showing only
0:00
S…
Speaker 1 (Recording_280)
We will start with the items that we need
0:04
S…
Speaker 1 (Recording_280)
to do and we have plan 3
0:09
S…
Speaker 5 (Recording_280)
on that.
0:09
S…
Speaker 1 (Recording_280)
Those items we will estimate first and
0:14
S…
Speaker 1 (Recording_280)
then or we will I will groom it again a
0:19
S…
Speaker 1 (Recording_280)
short grooming and then we can go ahead with the next item.
0:22
S…
Speaker 1 (Recording_280)
Any any doubt
0:27
S…
Speaker 1 (Recording_280)
on add condition block?
2:02
S…
Speaker 7 (Recording_280)
What changes
2:19
S…
Speaker 6 (Recording_280)
we have done?
2:20
S…
Speaker 7 (Recording_280)
What
2:27
S…
Speaker 7 (Recording_280)
changes
2:37
S…
Speaker 1 (Recording_280)
we have done?
2:42
S…
Speaker 3 (Recording_280)
I will be on
3:08
S…
Speaker 2 (Recording_280)
leave for second week and
3:15
S…
Speaker 2 (Recording_280)
Kunal is also on the leave for 13th and 14th,
3:19
S…
Speaker 4 (Recording_280)
first week.
3:20
S…
Speaker 2 (Recording_280)
15th and 19th are tentative and
3:24
S…
Speaker 2 (Recording_280)
Hamid is
3:29
S…
Speaker 2 (Recording_280)
also but in third week.
3:46
S…
Speaker 2 (Recording_280)
15 i think second half right now
3:51
S…
Speaker 3 (Recording_280)
but will
3:55
S…
Speaker 3 (Recording_280)
be tentative okay so instead
3:59
S…
Speaker 1 (Recording_280)
of 35 we'll have like 30 maybe
4:03
S…
Speaker 1 (Recording_280)
estimate
5:01
S…
Speaker 1 (Recording_280)
So, in the design it is a select one right in
5:05
S…
Speaker 1 (Recording_280)
which we will show the attribute type available attribute
5:10
S…
Speaker 1 (Recording_280)
type and here it is just the input which is
5:20
S…
Speaker 1 (Recording_280)
also in the big line it is a simple text instead of I am being select
5:24
S…
Speaker 1 (Recording_280)
input.
5:25
S…
Speaker 1 (Recording_280)
So,
5:30
S…
Speaker 1 (Recording_280)
in
5:36
S…
Speaker 1 (Recording_280)
the if condition first is the drop down.
5:38
S…
Speaker 1 (Recording_280)
Yeah.
5:40
S…
Speaker 1 (Recording_280)
It is the drop down.
5:42
S…
Speaker 1 (Recording_280)
So,
5:43
S…
Speaker 1 (Recording_280)
he has made it as a text.
5:46
S…
Speaker 1 (Recording_280)
Yes.
5:47
S…
Speaker 1 (Recording_280)
Yeah,
5:54
S…
Speaker 1 (Recording_280)
yeah, yeah.
5:54
S…
Speaker 1 (Recording_280)
It can't be filled here.
5:55
S…
Speaker 1 (Recording_280)
Next you are seeing.
5:58
S…
Speaker 1 (Recording_280)
It's
6:06
S…
Speaker 1 (Recording_280)
a simple
6:15
S…
Speaker 1 (Recording_280)
text.
6:17
S…
Speaker 1 (Recording_280)
It's
6:22
S…
Speaker 1 (Recording_280)
a simple text.
6:23
S…
Speaker 1 (Recording_280)
Here it is.
6:24
S…
Speaker 1 (Recording_280)
It will
6:31
S…
Speaker 1 (Recording_280)
also be.
6:32
S…
Speaker 1 (Recording_280)
Add
6:36
S…
Speaker 1 (Recording_280)
and all right?
6:37
S…
Speaker 1 (Recording_280)
No,
6:37
S…
Speaker 1 (Recording_280)
it
6:44
S…
Speaker 1 (Recording_280)
is. You
7:18
S…
Speaker 1 (Recording_280)
see the.
7:19
S…
Speaker 1 (Recording_280)
Change
7:35
S…
Speaker 1 (Recording_280)
karna hooga to kaise karega?
7:37
S…
Speaker 1 (Recording_280)
Delete karna padega.
7:38
S…
Speaker 1 (Recording_280)
Yes,
7:39
S…
Speaker 1 (Recording_280)
to delete and then again add.
7:40
S…
Speaker 1 (Recording_280)
Yeah.
7:42
S…
Speaker 1 (Recording_280)
So
7:55
S…
Speaker 1 (Recording_280)
the.
7:55
S…
Speaker 1 (Recording_280)
So
8:02
S…
Speaker 1 (Recording_280)
the value
8:08
S…
Speaker 1 (Recording_280)
sum of the value can be.
8:09
S…
Speaker 1 (Recording_280)
Abhi
8:16
S…
Speaker 1 (Recording_280)
to haam abhi ke liye replicate kare na?
8:18
S…
Speaker 1 (Recording_280)
Abhi ke
8:22
S…
Speaker 1 (Recording_280)
liye drop down ne rakhke us.
9:57
S…
Speaker 1 (Recording_280)
like a drop down, right?
10:00
S…
Speaker 1 (Recording_280)
No, for condition he has created a drop down.
10:04
S…
Speaker 1 (Recording_280)
For the input field,
10:07
S…
Speaker 1 (Recording_280)
it is the normal text input.
10:09
S…
Speaker 1 (Recording_280)
I
10:14
S…
Speaker 1 (Recording_280)
think
10:21
S…
Speaker 1 (Recording_280)
it
11:10
S…
Speaker 1 (Recording_280)
would be better if we give the conditions
11:18
S…
Speaker 1 (Recording_280)
and then we will test it.
11:29
S…
Speaker 1 (Recording_280)
5, but it won't be more.
11:31
S…
Speaker 1 (Recording_280)
5 won't be more.
11:33
S…
Speaker 1 (Recording_280)
Because in the back end,
11:35
S…
Speaker 1 (Recording_280)
there is no front end side here.
11:37
S…
Speaker 1 (Recording_280)
You have to check the
11:41
S…
Speaker 1 (Recording_280)
data room. Usually,
11:44
S…
Speaker 1 (Recording_280)
if
11:50
S…
Speaker 1 (Recording_280)
you check the conditions, it's okay.
11:52
S…
Speaker 1 (Recording_280)
You have to check multiple conditions.
11:54
S…
Speaker 1 (Recording_280)
But overall,
11:56
S…
Speaker 1 (Recording_280)
there is a feature,
11:58
S…
Speaker 1 (Recording_280)
right?
11:59
S…
Speaker 1 (Recording_280)
So,
12:00
S…
Speaker 1 (Recording_280)
the conditions are pressed.
12:05
S…
Speaker 1 (Recording_280)
I would like,
12:06
S…
Speaker 1 (Recording_280)
suppose if you want.
12:07
S…
Speaker 1 (Recording_280)
Whenever we
12:17
S…
Speaker 1 (Recording_280)
say
12:29
S…
Speaker 1 (Recording_280)
that, we are thinking it is much as per
12:34
S…
Speaker 1 (Recording_280)
our experience with Onga,
12:36
S…
Speaker 1 (Recording_280)
we are just saying that.
12:37
S…
Speaker 1 (Recording_280)
It doesn't mean it is
12:42
S…
Speaker 1 (Recording_280)
correct, but still.
12:42
S…
Speaker 1 (Recording_280)
I
12:52
S…
Speaker 1 (Recording_280)
do agree that there are multiple combinations,
12:53
S…
Speaker 1 (Recording_280)
but the other stories are also compared.
13:12
S…
Speaker 1 (Recording_280)
The same here,
13:15
S…
Speaker 1 (Recording_280)
right? You have like,
13:17
S…
Speaker 1 (Recording_280)
document type combination here.
13:19
S…
Speaker 1 (Recording_280)
Six document types here.
13:23
S…
Speaker 1 (Recording_280)
And on all,
13:24
S…
Speaker 1 (Recording_280)
for combination here.
13:25
S…
Speaker 1 (Recording_280)
And in extraction,
13:27
S…
Speaker 1 (Recording_280)
you have manual or automated.
13:29
S…
Speaker 1 (Recording_280)
Manual,
13:29
S…
Speaker 1 (Recording_280)
we don't use it.
13:30
S…
Speaker 1 (Recording_280)
So,
13:31
S…
Speaker 1 (Recording_280)
just automated,
13:32
S…
Speaker 1 (Recording_280)
right?
13:34
S…
Speaker 1 (Recording_280)
So, what is it?
13:36
S…
Speaker 1 (Recording_280)
Extraction status?
13:38
S…
Speaker 1 (Recording_280)
That's a good
13:42
S…
Speaker 1 (Recording_280)
case,
13:44
S…
Speaker 1 (Recording_280)
right? But it doesn't depend on the case.
13:49
S…
Speaker 1 (Recording_280)
Tomorrow,
13:50
S…
Speaker 1 (Recording_280)
if you have other fields,
13:51
S…
Speaker 1 (Recording_280)
we'll have a lot of fields.
14:15
S…
Speaker 1 (Recording_280)
It will be like automated workflow.
14:18
S…
Speaker 1 (Recording_280)
No,
14:20
S…
Speaker 1 (Recording_280)
no, but we are talking about this testing,
14:22
S…
Speaker 1 (Recording_280)
right? These are three.
14:24
S…
Speaker 1 (Recording_280)
When they come,
14:27
S…
Speaker 1 (Recording_280)
they will do one test.
14:28
S…
Speaker 1 (Recording_280)
How much is the number of and of combination?
14:32
S…
Speaker 1 (Recording_280)
There is no limit.
14:37
S…
Speaker 1 (Recording_280)
No, no,
14:38
S…
Speaker 1 (Recording_280)
my point is that if you have the limit as in,
14:42
S…
Speaker 1 (Recording_280)
if your value is finished,
14:43
S…
Speaker 1 (Recording_280)
then what will I do?
14:45
S…
Speaker 1 (Recording_280)
I have all the value in the procurement type.
14:48
S…
Speaker 1 (Recording_280)
So,
14:49
S…
Speaker 1 (Recording_280)
how much will it come?
14:49
S…
Speaker 1 (Recording_280)
6 will come,
14:50
S…
Speaker 1 (Recording_280)
right? Extraction will come.
15:00
S…
Speaker 3 (Recording_280)
Let's say document type,
15:01
S…
Speaker 3 (Recording_280)
so document type with automation,
15:03
S…
Speaker 3 (Recording_280)
how much will it be?
15:04
S…
Speaker 3 (Recording_280)
Document type with manual,
15:08
S…
Speaker 3 (Recording_280)
how much will it be?
15:09
S…
Speaker 3 (Recording_280)
If you want to make such a combination,
15:11
S…
Speaker 3 (Recording_280)
it will be a lot easier.
15:12
S…
Speaker 3 (Recording_280)
Yes,
15:14
S…
Speaker 4 (Recording_280)
if you want to make such a combination,
15:15
S…
Speaker 4 (Recording_280)
then you will be a lot easier.
15:17
S…
Speaker 4 (Recording_280)
No,
15:17
S…
Speaker 1 (Recording_280)
no,
15:19
S…
Speaker 1 (Recording_280)
I don't think so.
15:20
S…
Speaker 1 (Recording_280)
I don't think so.
15:23
S…
Speaker 1 (Recording_280)
I don't think you need to check all the conditions.
15:26
S…
Speaker 1 (Recording_280)
We actually don't test the
15:30
S…
Speaker 1 (Recording_280)
conditions. That's what we've already done.
15:31
S…
Speaker 1 (Recording_280)
We've already tested all the combinations in Excel.
15:34
S…
Speaker 1 (Recording_280)
We've already tested Excel testing.
15:37
S…
Speaker 1 (Recording_280)
Yes,
15:39
S…
Speaker 4 (Recording_280)
but we don't do it with Excel.
15:41
S…
Speaker 4 (Recording_280)
We do it with create workflow and
15:45
S…
Speaker 4 (Recording_280)
then we need to check all the flows.
15:47
S…
Speaker 1 (Recording_280)
I'm
15:56
S…
Speaker 2 (Recording_280)
okay. I'm
16:11
S…
Speaker 1 (Recording_280)
going to discuss it at the end and publish it.
16:18
S…
Speaker 1 (Recording_280)
So, in case of publish let me just
16:22
S…
Speaker 1 (Recording_280)
give a little bit to what we have decided.
16:26
S…
Speaker 2 (Recording_280)
So,
16:28
S…
Speaker 1 (Recording_280)
we have the publish workflow.
16:30
S…
Speaker 2 (Recording_280)
So,
16:30
S…
Speaker 1 (Recording_280)
user should able to click on any workflow which on
16:35
S…
Speaker 1 (Recording_280)
the publish workflow.
16:36
S…
Speaker 1 (Recording_280)
It should validate,
16:36
S…
Speaker 1 (Recording_280)
it should automatically first of all save the changes.
16:39
S…
Speaker 1 (Recording_280)
So,
16:40
S…
Speaker 1 (Recording_280)
in
16:45
S…
Speaker 1 (Recording_280)
that case first we need to save the changes.
16:49
S…
Speaker 1 (Recording_280)
Then we need to change the status to publish and if that
16:53
S…
Speaker 1 (Recording_280)
one particular work flow was not draft then we need to move it to the published section.
16:57
S…
Speaker 1 (Recording_280)
Work flow can be only published when trigger
17:02
S…
Speaker 1 (Recording_280)
is configured,
17:02
S…
Speaker 1 (Recording_280)
required task details are completed all the mandatory validations
17:07
S…
Speaker 1 (Recording_280)
are satisfied.
17:07
S…
Speaker 1 (Recording_280)
There is no action of condition
17:12
S…
Speaker 3 (Recording_280)
right like it should be just action then it can be published even if there is no condition
17:16
S…
Speaker 3 (Recording_280)
right that is how we have created.
17:20
S…
Speaker 2 (Recording_280)
Yes,
17:20
S…
Speaker 1 (Recording_280)
yes without condition if validation
17:25
S…
Speaker 1 (Recording_280)
fails jitne bhi error save draft pe hum dikhate ho
17:29
S…
Speaker 1 (Recording_280)
sab dikhayenge aur publish nahi ho
17:34
S…
Speaker 1 (Recording_280)
ga per suppose now the
17:38
S…
Speaker 1 (Recording_280)
work flow is already published with all the validations and everything but
17:43
S…
Speaker 1 (Recording_280)
user comes to that listing page where he edits the work
17:47
S…
Speaker 2 (Recording_280)
flow template.
17:55
S…
Speaker 1 (Recording_280)
User will not have the save as draft button enabled.
18:00
S…
Speaker 1 (Recording_280)
He needs to publish it.
18:02
S…
Speaker 1 (Recording_280)
So,
18:04
S…
Speaker 1 (Recording_280)
the template was already published.
18:06
S…
Speaker 2 (Recording_280)
Yeah.
18:07
S…
Speaker 2 (Recording_280)
So,
18:11
S…
Speaker 1 (Recording_280)
edit published work to me kya aega?
18:13
S…
Speaker 1 (Recording_280)
User should be able to open in a edit mode.
18:16
S…
Speaker 1 (Recording_280)
User can modify all the agent,
18:19
S…
Speaker 1 (Recording_280)
task, condition,
18:20
S…
Speaker 1 (Recording_280)
jo bhi usko modify karna hai.
18:25
S…
Speaker 1 (Recording_280)
Once the workflow is already published the save draft button
18:30
S…
Speaker 1 (Recording_280)
should be disabled user should not able to save the changes
18:34
S…
Speaker 1 (Recording_280)
as a draft again.
18:35
S…
Speaker 1 (Recording_280)
On a cover of that disabled save draft
18:39
S…
Speaker 1 (Recording_280)
button you will showcase that user should see a message
18:43
S…
Speaker 1 (Recording_280)
and message is this workflow is already published any new changes must
18:48
S…
Speaker 1 (Recording_280)
be published directly.
19:02
S…
Speaker 1 (Recording_280)
This is a section
19:07
S…
Speaker 5 (Recording_280)
for instances.
19:08
S…
Speaker 5 (Recording_280)
I had a question related to the instances.
19:11
S…
Speaker 5 (Recording_280)
After publishing,
19:12
S…
Speaker 5 (Recording_280)
if instance is created for a workflow and then we go and change
19:16
S…
Speaker 5 (Recording_280)
the published workflow and now if you go to
19:20
S…
Speaker 5 (Recording_280)
that instance which is already created.
19:23
S…
Speaker 5 (Recording_280)
and see the template for it it will show the new
19:28
S…
Speaker 5 (Recording_280)
template details and not the older one yeah that's
19:32
S…
Speaker 3 (Recording_280)
how it is like if it is change in between then it will show the updated one updated
19:36
S…
Speaker 3 (Recording_280)
and the new trigger will be based on the new condition
20:00
S…
Speaker 2 (Recording_280)
to save the changes,
20:01
S…
Speaker 2 (Recording_280)
publish what should happen?
20:04
S…
Speaker 2 (Recording_280)
Existing published work show template
20:08
S…
Speaker 2 (Recording_280)
should get updated,
20:09
S…
Speaker 2 (Recording_280)
no separate order should get created,
20:12
S…
Speaker 2 (Recording_280)
let test configuration becomes the active,
20:15
S…
Speaker 2 (Recording_280)
abhi aate instance way.
20:17
S…
Speaker 5 (Recording_280)
So,
20:19
S…
Speaker 2 (Recording_280)
I have created one workflow template x,
20:22
S…
Speaker 2 (Recording_280)
y, z whatever it is,
20:24
S…
Speaker 2 (Recording_280)
it is published right now,
20:26
S…
Speaker 2 (Recording_280)
it has one trigger and
20:30
S…
Speaker 2 (Recording_280)
a one task.
20:32
S…
Speaker 2 (Recording_280)
It is already published.
20:33
S…
Speaker 2 (Recording_280)
Now there are I have uploaded some file
20:37
S…
Speaker 2 (Recording_280)
the trigger got executed some instances got
20:41
S…
Speaker 2 (Recording_280)
created.
20:42
S…
Speaker 2 (Recording_280)
After that I thought I have not added condition
20:46
S…
Speaker 2 (Recording_280)
added condition so I will go to that template I want to add one more condition.
21:18
S…
Speaker 2 (Recording_280)
If I open it,
21:20
S…
Speaker 6 (Recording_280)
what will it show?
21:21
S…
Speaker 1 (Recording_280)
If I open it, what will it show?
21:21
S…
Speaker 3 (Recording_280)
If I open it,
21:25
S…
Speaker 1 (Recording_280)
what will it show? If I open it,
21:26
S…
Speaker 1 (Recording_280)
what will it show? If I open it,
21:26
S…
Speaker 1 (Recording_280)
what will it show?
21:27
S…
Speaker 1 (Recording_280)
If I open it, what will it show?
21:28
S…
Speaker 1 (Recording_280)
If I open it,
21:29
S…
Speaker 1 (Recording_280)
what will it show?
21:31
S…
Speaker 4 (Recording_280)
If I open it,
21:32
S…
Speaker 2 (Recording_280)
what will it show? If I
21:56
S…
Speaker 2 (Recording_280)
open it, what
22:08
S…
Speaker 2 (Recording_280)
will it show? If I open it,
22:09
S…
Speaker 2 (Recording_280)
what will it show? If I open it,
22:10
S…
Speaker 1 (Recording_280)
what will it show? If I open it,
22:14
S…
Speaker 1 (Recording_280)
what will it show?
22:14
S…
Speaker 1 (Recording_280)
If
23:43
S…
Speaker 1 (Recording_280)
I open it, what
24:00
S…
Speaker 1 (Recording_280)
will it show?
24:01
S…
Speaker 1 (Recording_280)
If I open
24:55
S…
Speaker 2 (Recording_280)
it, what will it show?
25:00
S…
Speaker 1 (Recording_280)
The name of the name is the name of the name of
25:04
S…
Speaker 4 (Recording_280)
the name of the name
25:09
S…
Speaker 4 (Recording_280)
of the name of the
25:20
S…
Speaker 4 (Recording_280)
name
25:59
S…
Speaker 3 (Recording_280)
to continue
26:30
S…
Speaker 1 (Recording_280)
using the configuration under which they were created remains
26:36
S…
Speaker 1 (Recording_280)
unaffected
26:43
S…
Speaker 1 (Recording_280)
future workflow creation should use the latest published workflow
26:47
S…
Speaker 8 (Recording_280)
configuration.
26:48
S…
Speaker 1 (Recording_280)
Acceptance criteria,
26:52
S…
Speaker 1 (Recording_280)
publish valid workflow,
26:55
S…
Speaker 1 (Recording_280)
edit,
26:56
S…
Speaker 1 (Recording_280)
save as draft,
26:58
S…
Speaker 1 (Recording_280)
that it will be disabled,
27:01
S…
Speaker 1 (Recording_280)
publish existing instances and future instances.
27:08
S…
Speaker 2 (Recording_280)
Prigati, I have already published workflow,
27:10
S…
Speaker 2 (Recording_280)
if I edit it and if user is not trying
27:14
S…
Speaker 2 (Recording_280)
to click on publish changes and if he is going to other tab,
27:18
S…
Speaker 2 (Recording_280)
user management or someone on the tab,
27:21
S…
Speaker 2 (Recording_280)
then we have any pop -up message?
27:25
S…
Speaker 5 (Recording_280)
No,
27:26
S…
Speaker 1 (Recording_280)
no, no.
27:26
S…
Speaker 1 (Recording_280)
We have it but I guess it is same as prompt.
27:31
S…
Speaker 7 (Recording_280)
So,
27:32
S…
Speaker 3 (Recording_280)
would
27:43
S…
Speaker 1 (Recording_280)
you like to publish the changes?
27:46
S…
Speaker 6 (Recording_280)
So,
27:46
S…
Speaker 1 (Recording_280)
discard changes and publish changes,
27:48
S…
Speaker 1 (Recording_280)
I hope.
27:50
S…
Speaker 1 (Recording_280)
Okay. Publish, I got not seen.
30:00
S…
Speaker 1 (Recording_280)
You will need an investigation and
30:05
S…
Speaker 1 (Recording_280)
documentation and then we can proceed like a design approach.
30:09
S…
Speaker 5 (Recording_280)
Yes.
30:10
S…
Speaker 2 (Recording_280)
We can
30:19
S…
Speaker 1 (Recording_280)
start the
30:23
S…
Speaker 1 (Recording_280)
development but still we cannot commit on it.
30:40
S…
Speaker 2 (Recording_280)
But I guess estimate to do the investigation task and then
30:45
S…
Speaker 7 (Recording_280)
you have to keep it in the sprint tool.
30:45
S…
Speaker 2 (Recording_280)
In the investigation tool.
30:49
S…
Speaker 2 (Recording_280)
You have to
30:56
S…
Speaker 2 (Recording_280)
move in the sprint tool.
30:57
S…
Speaker 2 (Recording_280)
You have to move in the sprint tool.
30:58
S…
Speaker 2 (Recording_280)
You have to move in the sprint tool.
31:00
S…
Speaker 2 (Recording_280)
You have to move in the sprint tool.
31:03
S…
Speaker 2 (Recording_280)
You have to move in the
31:10
S…
Speaker 2 (Recording_280)
sprint tool. You have
31:26
S…
Speaker 2 (Recording_280)
to move in the sprint tool.
31:30
S…
Speaker 6 (Recording_280)
No, you didn't say it in DSM.
31:31
S…
Speaker 1 (Recording_280)
He said that it was just a moment ago,
31:35
S…
Speaker 1 (Recording_280)
but it was just a moment ago.
31:37
S…
Speaker 1 (Recording_280)
He said that it was just a moment ago.
31:40
S…
Speaker 4 (Recording_280)
He said that it was just a moment ago.
31:41
S…
Speaker 8 (Recording_280)
He said that it was just a moment ago.
31:43
S…
Speaker 1 (Recording_280)
He said that it was just a moment ago.
31:46
S…
Speaker 1 (Recording_280)
He
31:50
S…
Speaker 8 (Recording_280)
said that it was just a moment ago. He said that it was just a moment ago.
31:53
S…
Speaker 6 (Recording_280)
He said that it was just a moment ago.
31:57
S…
Speaker 2 (Recording_280)
He said that it was a moment ago.
32:19
S…
Speaker 8 (Recording_280)
No.
32:20
S…
Speaker 1 (Recording_280)
Confirmed.
33:03
S…
Speaker 3 (Recording_280)
No.
33:04
S…
Speaker 1 (Recording_280)
Confirmed
33:27
S…
Speaker 2 (Recording_280)
Yes, but the government has confirmed that if it will
33:31
S…
Speaker 2 (Recording_280)
be finished, then he will move.
33:33
S…
Speaker 3 (Recording_280)
No,
33:33
S…
Speaker 1 (Recording_280)
we
33:57
S…
Speaker 6 (Recording_280)
will take the investigation before and in the third week we have the availability.
34:03
S…
Speaker 6 (Recording_280)
So the next sprint is the investigation if
34:07
S…
Speaker 6 (Recording_280)
needed for any particular work item.
34:09
S…
Speaker 6 (Recording_280)
So we need to take that investigation in the current sprint.
34:12
S…
Speaker 6 (Recording_280)
Like the rest of the team.
34:14
S…
Speaker 1 (Recording_280)
The trigger will
34:40
S…
Speaker 4 (Recording_280)
be done,
34:40
S…
Speaker 6 (Recording_280)
right? Or do we need to do that?
34:41
S…
Speaker 6 (Recording_280)
Time trigger also is the investigation.
34:57
S…
Speaker 2 (Recording_280)
It is something that we can do.
35:22
S…
Speaker 1 (Recording_280)
So, once we finish the estimation,
35:24
S…
Speaker 1 (Recording_280)
sorry investigation will come to you and will say that this is already
35:29
S…
Speaker 1 (Recording_280)
done and now we can pick.
35:30
S…
Speaker 1 (Recording_280)
But without investigation we will not able to add details.
35:59
S…
Speaker 1 (Recording_280)
how big it is if Aditya come
36:04
S…
Speaker 1 (Recording_280)
again for file space we are fetching all the data I
36:08
S…
Speaker 2 (Recording_280)
am
37:13
S…
Speaker 1 (Recording_280)
asking you the message that message which you posted Sanjay
37:17
S…
Speaker 1 (Recording_280)
right I guess Sanjay didn't get it for the first time can you make it no no sir I
37:21
S…
Speaker 2 (Recording_280)
don't know I don't
37:33
S…
Speaker 2 (Recording_280)
suggest that the single API can answer same question
37:47
S…
Speaker 1 (Recording_280)
mein poochu Olga aur shayat se jango ko poochna padega Olga
37:51
S…
Speaker 3 (Recording_280)
will not able to answer
39:57
S…
Speaker 1 (Recording_280)
Whatever he was saying, right?
40:16
S…
Speaker 1 (Recording_280)
Then we have so these stories are optional
40:20
S…
Speaker 1 (Recording_280)
so any which was Aditya saying we will able to do it only three even if we
40:24
S…
Speaker 1 (Recording_280)
go ahead with the simplest method right
40:28
S…
Speaker 1 (Recording_280)
I have
40:32
S…
Speaker 1 (Recording_280)
given the priority for deals portfolio and the search again
40:36
S…
Speaker 1 (Recording_280)
for this we don't have designs
40:48
S…
Speaker 1 (Recording_280)
So we have the video.
40:49
S…
Speaker 1 (Recording_280)
Just
40:57
S…
Speaker 2 (Recording_280)
wait
41:06
S…
Speaker 2 (Recording_280)
for
42:19
S…
Speaker 1 (Recording_280)
a second.
45:28
S…
Speaker 1 (Recording_280)
user story is for that
45:36
S…
Speaker 1 (Recording_280)
user will able to see a search icon here
45:40
S…
Speaker 1 (Recording_280)
as just icon if user clicks on it
45:45
S…
Speaker 1 (Recording_280)
it will use it
45:49
S…
Speaker 1 (Recording_280)
and type to
45:56
S…
Speaker 1 (Recording_280)
search and this is just for the deals so
46:00
S…
Speaker 1 (Recording_280)
the text box says search deals if it
46:04
S…
Speaker 1 (Recording_280)
is not added it's if it is empty it will get you
46:09
S…
Speaker 2 (Recording_280)
know collapsed the deal
46:21
S…
Speaker 2 (Recording_280)
name filter so this is like the
46:28
S…
Speaker 2 (Recording_280)
search out and search inside as well
46:33
S…
Speaker 2 (Recording_280)
which would take priority and if
47:03
S…
Speaker 2 (Recording_280)
the user
48:57
S…
Speaker 2 (Recording_280)
if I look very comfortable very easily if I am saying if you have the thoughts
49:02
S…
Speaker 2 (Recording_280)
that are a unnecessary complicate or should be just one
49:06
S…
Speaker 2 (Recording_280)
thing I feel it contains this particular text you know like how it
49:10
S…
Speaker 3 (Recording_280)
is actually I
49:25
S…
Speaker 1 (Recording_280)
was expecting the same pop which was on the file
49:29
S…
Speaker 1 (Recording_280)
speech that it will have the list of views and then you
49:33
S…
Speaker 1 (Recording_280)
can just search and just play
49:46
S…
Speaker 1 (Recording_280)
I will ask this question.
49:48
S…
Speaker 2 (Recording_280)
Then I think like depending
49:53
S…
Speaker 2 (Recording_280)
on what Olga says and after the design discussion,
49:57
S…
Speaker 2 (Recording_280)
I think it will be best.
50:01
S…
Speaker 1 (Recording_280)
discuss all the filter related stories that now again
50:09
S…
Speaker 1 (Recording_280)
like the elements that we have which we had in mind are like changing because
50:13
S…
Speaker 1 (Recording_280)
you
50:30
S…
Speaker 1 (Recording_280)
don't see you don't
50:36
S…
Speaker 1 (Recording_280)
see something like what we have this
50:42
S…
Speaker 2 (Recording_280)
is the prototype this
50:46
S…
Speaker 1 (Recording_280)
is not what we implement there
50:55
S…
Speaker 1 (Recording_280)
is no names it
52:24
S…
Speaker 1 (Recording_280)
is fine but it's
54:43
S…
Speaker 2 (Recording_280)
right so every time they go ahead and create something new
55:01
S…
Speaker 2 (Recording_280)
And once the application is done,
55:03
S…
Speaker 2 (Recording_280)
ready, then they will complain that it's not consistent.
55:07
S…
Speaker 2 (Recording_280)
I'm just not sure why...
55:12
S…
Speaker 2 (Recording_280)
Is it recording?
55:13
S…
Speaker 7 (Recording_280)
No,
55:14
S…
Speaker 1 (Recording_280)
no. No,
55:15
S…
Speaker 7 (Recording_280)
no. No,
55:16
S…
Speaker 7 (Recording_280)
just...
55:17
S…
Speaker 7 (Recording_280)
No, sorry,
55:18
S…
Speaker 2 (Recording_280)
Dev.
55:19
S…
Speaker 2 (Recording_280)
No, why they're bringing them back?
55:21
S…
Speaker 2 (Recording_280)
Let's see what in Dell group Olga has
55:25
S…
Speaker 2 (Recording_280)
added that person.
55:27
S…
Speaker 8 (Recording_280)
Yuri.
55:28
S…
Speaker 1 (Recording_280)
Yuri.
55:29
S…
Speaker 5 (Recording_280)
Yuri.
55:30
S…
Speaker 7 (Recording_280)
But if someone remember,
55:32
S…
Speaker 2 (Recording_280)
I don't remember him.
55:33
S…
Speaker 5 (Recording_280)
Yes, yes.
55:34
S…
Speaker 1 (Recording_280)
Yes,
55:35
S…
Speaker 1 (Recording_280)
he was a developer.
55:36
S…
Speaker 6 (Recording_280)
He was an architect,
55:38
S…
Speaker 1 (Recording_280)
right?
55:38
S…
Speaker 6 (Recording_280)
Presley had also said in the weekly call.
55:40
S…
Speaker 3 (Recording_280)
Yes, he was an architect.
55:41
S…
Speaker 3 (Recording_280)
He didn't have the design of the event store,
55:45
S…
Speaker 3 (Recording_280)
which was the original.
55:46
S…
Speaker 7 (Recording_280)
Yes,
55:47
S…
Speaker 1 (Recording_280)
it was the original.
55:48
S…
Speaker 6 (Recording_280)
In the technical deep dive,
55:50
S…
Speaker 6 (Recording_280)
Presley had also informed him.
55:55
S…
Speaker 2 (Recording_280)
I didn't hear his name.
55:57
S…
Speaker 1 (Recording_280)
Yuri.
55:58
S…
Speaker 6 (Recording_280)
Rick won't be able to join from now point onwards
56:02
S…
Speaker 6 (Recording_280)
so Yuri will gonna be joining on his behalf.
56:05
S…
Speaker 8 (Recording_280)
Technical
56:09
S…
Speaker 3 (Recording_280)
Deep Dice.
56:10
S…
Speaker 6 (Recording_280)
And I think Golga kal Chutti beyan.
56:13
S…
Speaker 4 (Recording_280)
Okay,
56:16
S…
Speaker 7 (Recording_280)
I don't want to ask you.
56:17
S…
Speaker 8 (Recording_280)
Let's give
56:21
S…
Speaker 2 (Recording_280)
a tentative update Goro.
56:24
S…
Speaker 2 (Recording_280)
That agent won't be part of sprint 3 as we need to do a
56:28
S…
Speaker 2 (Recording_280)
thorough investigation and some package in this as well in
56:32
S…
Speaker 7 (Recording_280)
order to start with that task.
56:34
S…
Speaker 2 (Recording_280)
So once the investigation is done,
56:36
S…
Speaker 2 (Recording_280)
if she forces us then only say
56:40
S…
Speaker 2 (Recording_280)
okay, we will take it as uncommitted.
56:43
S…
Speaker 2 (Recording_280)
For filter story,
56:46
S…
Speaker 2 (Recording_280)
these are the blockers.
56:48
S…
Speaker 2 (Recording_280)
I will tag Rob.
56:51
S…
Speaker 6 (Recording_280)
One time we will estimate how many story points are going,
56:54
S…
Speaker 6 (Recording_280)
and then we will talk about it.
56:56
S…
Speaker 7 (Recording_280)
But there are not stories,
57:00
S…
Speaker 5 (Recording_280)
right?
57:01
S…
Speaker 2 (Recording_280)
The filter design is different,
57:04
S…
Speaker 1 (Recording_280)
right?
57:04
S…
Speaker 4 (Recording_280)
I don't know,
57:07
S…
Speaker 6 (Recording_280)
one time we will get clarity and then we will talk about it.
57:10
S…
Speaker 6 (Recording_280)
I am not saying that we are doing 5 stories,
57:12
S…
Speaker 6 (Recording_280)
but we don't have clarity.
57:14
S…
Speaker 6 (Recording_280)
The story points are estimated,
57:16
S…
Speaker 1 (Recording_280)
right?
57:17
S…
Speaker 6 (Recording_280)
We are blocking it.
57:27
S…
Speaker 2 (Recording_280)
time trigger ka what I have seen in
57:32
S…
Speaker 8 (Recording_280)
your message is run immediately
58:02
S…
Speaker 2 (Recording_280)
and run after
58:08
S…
Speaker 2 (Recording_280)
and she have confirmed that once it is added to a deal setting
58:13
S…
Speaker 2 (Recording_280)
that only the time trigger will start so
58:19
S…
Speaker 2 (Recording_280)
so the first is the week so we
58:24
S…
Speaker 2 (Recording_280)
have like
58:29
S…
Speaker 2 (Recording_280)
So, Hamid you are saying you will not able to.
58:32
S…
Speaker 7 (Recording_280)
Repeat
58:40
S…
Speaker 3 (Recording_280)
every week and then they can select that.
58:42
S…
Speaker 3 (Recording_280)
So,
58:45
S…
Speaker 2 (Recording_280)
suppose if we expand I will
58:49
S…
Speaker 2 (Recording_280)
definitely check with Michael,
58:51
S…
Speaker 2 (Recording_280)
but I guess without modifying much design is also fine.
58:54
S…
Speaker 2 (Recording_280)
We will just remove this one,
58:56
S…
Speaker 2 (Recording_280)
we will just have week and then user will be able to select one
59:00
S…
Speaker 3 (Recording_280)
at a time.
59:01
S…
Speaker 1 (Recording_280)
Yes.
59:01
S…
Speaker 3 (Recording_280)
That is all right.
59:02
S…
Speaker 7 (Recording_280)
Yes. User will not able to select one.
59:04
S…
Speaker 3 (Recording_280)
Yes. And then drop down will be like the option I have provided like.
59:07
S…
Speaker 3 (Recording_280)
daily, weekly,
59:08
S…
Speaker 3 (Recording_280)
monthly.
59:09
S…
Speaker 2 (Recording_280)
There is
59:13
S…
Speaker 2 (Recording_280)
no much design dependency or change just week select repeats
59:18
S…
Speaker 2 (Recording_280)
every week and he will able to select a
59:22
S…
Speaker 2 (Recording_280)
day single day that is it when we have a day day there
59:26
S…
Speaker 2 (Recording_280)
is no issue right.
59:45
S…
Speaker 3 (Recording_280)
There is an option to select multiple days.
1:00:00
S…
Speaker 1 (Recording_280)
It's single.
1:00:00
S…
Speaker 1 (Recording_280)
Uh,
1:00:01
S…
Speaker 3 (Recording_280)
no,
1:00:02
S…
Speaker 3 (Recording_280)
no. Weekly selected,
1:00:03
S…
Speaker 3 (Recording_280)
like, Sunday,
1:00:04
S…
Speaker 3 (Recording_280)
Monday, Tuesday.
1:00:05
S…
Speaker 3 (Recording_280)
Individual P,
1:00:06
S…
Speaker 3 (Recording_280)
or, uh,
1:00:07
S…
Speaker 3 (Recording_280)
EA,
1:00:07
S…
Speaker 3 (Recording_280)
B. My screen opened,
1:00:09
S…
Speaker 3 (Recording_280)
let me show you how to share it.
1:00:10
S…
Speaker 1 (Recording_280)
I think that there are multiple events created.
1:00:14
S…
Speaker 1 (Recording_280)
Yes,
1:00:15
S…
Speaker 3 (Recording_280)
but we need to check that it is possible to
1:00:19
S…
Speaker 3 (Recording_280)
see how to configure our user service.
1:00:24
S…
Speaker 3 (Recording_280)
How to configure it from there?
1:00:27
S…
Speaker 1 (Recording_280)
Then it will be single,
1:00:29
S…
Speaker 1 (Recording_280)
like,
1:00:30
S…
Speaker 1 (Recording_280)
when we do Chrome,
1:00:31
S…
Speaker 1 (Recording_280)
then what happens?
1:01:21
S…
Speaker 2 (Recording_280)
multiple weekly events
1:01:22
S…
Speaker 1 (Recording_280)
We will
1:01:29
S…
Speaker 1 (Recording_280)
have a single
1:01:37
S…
Speaker 3 (Recording_280)
date.
1:01:54
S…
Speaker 3 (Recording_280)
Monthly,
1:02:03
S…
Speaker 2 (Recording_280)
you are seeing a single date.
1:02:05
S…
Speaker 2 (Recording_280)
Monthly,
1:02:07
S…
Speaker 2 (Recording_280)
you are seeing a single date.
1:02:08
S…
Speaker 2 (Recording_280)
Monthly, it will be repeated after 4 months.
1:02:10
S…
Speaker 2 (Recording_280)
Monthly,
1:02:12
S…
Speaker 2 (Recording_280)
we will have this
1:02:16
S…
Speaker 1 (Recording_280)
option.
1:02:26
S…
Speaker 2 (Recording_280)
Calendar day is the last day
1:02:30
S…
Speaker 2 (Recording_280)
of that month,
1:02:31
S…
Speaker 2 (Recording_280)
which we will select and implement.
1:02:34
S…
Speaker 2 (Recording_280)
Financial
1:02:58
S…
Speaker 2 (Recording_280)
link
1:03:32
S…
Speaker 2 (Recording_280)
is only a quarter,
1:03:33
S…
Speaker 2 (Recording_280)
so it will be a quarter.
1:03:35
S…
Speaker 2 (Recording_280)
Yes,
1:03:37
S…
Speaker 1 (Recording_280)
you have selected this month from January,
1:03:40
S…
Speaker 1 (Recording_280)
January 15th.
1:03:42
S…
Speaker 1 (Recording_280)
Next,
1:03:43
S…
Speaker 1 (Recording_280)
we will filter it in February and March 15th.
1:03:56
S…
Speaker 2 (Recording_280)
Michael as well that there has to be two options.
1:03:59
S…
Speaker 2 (Recording_280)
We will
1:04:12
S…
Speaker 2 (Recording_280)
have two drop downs.
1:04:13
S…
Speaker 2 (Recording_280)
First will be of the day like user will able to select
1:04:17
S…
Speaker 2 (Recording_280)
a day and second will be to select a month where
1:04:21
S…
Speaker 2 (Recording_280)
it will be like 1 to 3.
1:04:23
S…
Speaker 2 (Recording_280)
So,
1:04:24
S…
Speaker 2 (Recording_280)
if user is selecting 15th of
1:04:26
S…
Speaker 2 (Recording_280)
Meaning that it will execute on 15th of January,
1:04:29
S…
Speaker 2 (Recording_280)
15th of April,
1:04:31
S…
Speaker 2 (Recording_280)
15th of July as first month.
1:04:35
S…
Speaker 2 (Recording_280)
Second agar select karta hai to meaning that quarter ke second month
1:04:39
S…
Speaker 2 (Recording_280)
pe we need to figure this.
1:04:41
S…
Speaker 2 (Recording_280)
Aur third karta hai to quarter ke third month pe we will able to figure
1:04:45
S…
Speaker 2 (Recording_280)
this one.
1:05:03
S…
Speaker 2 (Recording_280)
Yeah, I mean,
1:05:04
S…
Speaker 2 (Recording_280)
quarter, sorry,
1:05:05
S…
Speaker 2 (Recording_280)
three days, repeat.
1:05:06
S…
Speaker 2 (Recording_280)
Quarter,
1:05:08
S…
Speaker 1 (Recording_280)
May, three months,
1:05:09
S…
Speaker 1 (Recording_280)
right?
1:05:10
S…
Speaker 1 (Recording_280)
So,
1:05:11
S…
Speaker 1 (Recording_280)
you have given quarter,
1:05:12
S…
Speaker 1 (Recording_280)
May, day of the month,
1:05:13
S…
Speaker 1 (Recording_280)
it will be, which will have this one to thirty first.
1:05:16
S…
Speaker 1 (Recording_280)
But one to thirty first,
1:05:18
S…
Speaker 1 (Recording_280)
may, agar, may, ne,
1:05:19
S…
Speaker 1 (Recording_280)
fifteenth, diya,
1:05:20
S…
Speaker 1 (Recording_280)
so,
1:05:22
S…
Speaker 1 (Recording_280)
fifteenth of which month,
1:05:23
S…
Speaker 1 (Recording_280)
aisa,
1:05:24
S…
Speaker 1 (Recording_280)
question aega,
1:05:25
S…
Speaker 1 (Recording_280)
first month ka,
1:05:28
S…
Speaker 1 (Recording_280)
second month ka,
1:05:29
S…
Speaker 1 (Recording_280)
ya, third month ka,
1:05:30
S…
Speaker 1 (Recording_280)
sari,
1:05:32
S…
Speaker 1 (Recording_280)
quarter, may, three,
1:05:33
S…
Speaker 1 (Recording_280)
three months hai,
1:05:33
S…
Speaker 1 (Recording_280)
right?
1:05:38
S…
Speaker 1 (Recording_280)
which will say select from one to three.
1:05:41
S…
Speaker 1 (Recording_280)
If you select first month of quarter,
1:05:46
S…
Speaker 1 (Recording_280)
second month of quarter,
1:05:48
S…
Speaker 1 (Recording_280)
third month of quarter.
1:05:49
S…
Speaker 1 (Recording_280)
And which we will select here.
1:05:52
S…
Speaker 1 (Recording_280)
One start
1:05:56
S…
Speaker 2 (Recording_280)
month select January.
1:06:00
S…
Speaker 2 (Recording_280)
January
1:06:11
S…
Speaker 1 (Recording_280)
is starting March.
1:07:20
S…
Speaker 1 (Recording_280)
We have a month and date.
1:08:12
S…
Speaker 1 (Recording_280)
When user adds the template to a deal setting,
1:08:15
S…
Speaker 1 (Recording_280)
after that whenever...
1:08:25
S…
Speaker 2 (Recording_280)
I set this trigger and create immediately
1:08:31
S…
Speaker 2 (Recording_280)
immediately after this time recurrence
1:08:35
S…
Speaker 2 (Recording_280)
is set it will start executing from that condition we
1:08:39
S…
Speaker 2 (Recording_280)
need
1:08:55
S…
Speaker 2 (Recording_280)
to
1:09:05
S…
Speaker 2 (Recording_280)
listen for that events what is added to the
1:09:10
S…
Speaker 2 (Recording_280)
So let's say in scheduler if it is something added for first day January,
1:09:14
S…
Speaker 1 (Recording_280)
right?
1:09:15
S…
Speaker 2 (Recording_280)
So it will publish an event on that date,
1:09:17
S…
Speaker 2 (Recording_280)
right? Yes,
1:09:18
S…
Speaker 1 (Recording_280)
right.
1:09:18
S…
Speaker 2 (Recording_280)
Then we have two combination
1:09:28
S…
Speaker 1 (Recording_280)
events.
1:09:28
S…
Speaker 2 (Recording_280)
Combination nahi osakta,
1:09:30
S…
Speaker 2 (Recording_280)
right? File uploaded and time based trigger.
1:09:32
S…
Speaker 2 (Recording_280)
Dornohan ka combination.
1:09:33
S…
Speaker 2 (Recording_280)
No,
1:09:34
S…
Speaker 1 (Recording_280)
it's not like that.
1:09:36
S…
Speaker 1 (Recording_280)
Event over time,
1:09:38
S…
Speaker 1 (Recording_280)
that's right.
1:09:38
S…
Speaker 1 (Recording_280)
In scheduler,
1:09:51
S…
Speaker 2 (Recording_280)
the deal idea is to determine which deal it is.
1:09:54
S…
Speaker 2 (Recording_280)
So if we apply it,
1:09:55
S…
Speaker 2 (Recording_280)
then we will create the appointment in scheduler and then we will pass
1:09:59
S…
Speaker 1 (Recording_280)
the deal.
1:10:01
S…
Speaker 4 (Recording_280)
I think schedule where we define an event and then upon listening
1:10:05
S…
Speaker 4 (Recording_280)
to that event we will have to just pull that template ID reference and
1:10:09
S…
Speaker 4 (Recording_280)
then create that instance that's it for that deal.
1:10:13
S…
Speaker 1 (Recording_280)
Both is
1:10:18
S…
Speaker 1 (Recording_280)
possible.
1:10:19
S…
Speaker 2 (Recording_280)
You can save the template ID or deal ID.
1:10:21
S…
Speaker 1 (Recording_280)
Any
1:10:35
S…
Speaker 8 (Recording_280)
estimation?
1:10:36
S…
Speaker 1 (Recording_280)
How we are planning Prakati,
1:10:38
S…
Speaker 2 (Recording_280)
we cannot implement all in one go,
1:10:41
S…
Speaker 1 (Recording_280)
right? I mean there are multiple type.
1:10:45
S…
Speaker 2 (Recording_280)
like we can take weekly daily as
1:10:49
S…
Speaker 2 (Recording_280)
a combination together and then monthly quarterly
1:10:54
S…
Speaker 1 (Recording_280)
yearly like that I mean
1:10:58
S…
Speaker 5 (Recording_280)
that's what I'm asking how much is it?
1:11:01
S…
Speaker 5 (Recording_280)
I have everything done in story
1:11:05
S…
Speaker 5 (Recording_280)
5 pointer or 3 pointer 3 maximum 3
1:11:10
S…
Speaker 3 (Recording_280)
you have to break
1:11:13
S…
Speaker 7 (Recording_280)
Break it.
1:11:14
S…
Speaker 6 (Recording_280)
I mean,
1:11:14
S…
Speaker 8 (Recording_280)
I can't do it.
1:11:16
S…
Speaker 3 (Recording_280)
No, Hamid is saying that it's weekly,
1:11:17
S…
Speaker 3 (Recording_280)
quarterly, monthly,
1:11:19
S…
Speaker 3 (Recording_280)
and then you decide the combination.
1:11:21
S…
Speaker 3 (Recording_280)
In that case,
1:11:23
S…
Speaker 3 (Recording_280)
break it.
1:11:24
S…
Speaker 1 (Recording_280)
It's possible
1:11:29
S…
Speaker 4 (Recording_280)
that we both have to take it side by side,
1:11:31
S…
Speaker 4 (Recording_280)
and then we have to take it back.
1:11:33
S…
Speaker 4 (Recording_280)
The story of the above and the timely
1:11:38
S…
Speaker 1 (Recording_280)
triggers.
1:11:38
S…
Speaker 1 (Recording_280)
I can do it.
1:11:42
S…
Speaker 2 (Recording_280)
I mean, do a lot of those.
1:11:55
S…
Speaker 4 (Recording_280)
But I think that the schema that we have created
1:11:59
S…
Speaker 4 (Recording_280)
the template, we need to change the template.
1:12:00
S…
Speaker 4 (Recording_280)
We need to add a time -layer trigger.
1:12:02
S…
Speaker 4 (Recording_280)
Now we need to change the events of
1:12:07
S…
Speaker 2 (Recording_280)
the first time.
1:12:09
S…
Speaker 2 (Recording_280)
Multiple things.
1:12:11
S…
Speaker 2 (Recording_280)
Once one of the triggers is done then the other will be very easy.
1:12:41
S…
Speaker 1 (Recording_280)
No, I mean
1:12:47
S…
Speaker 1 (Recording_280)
It will not
1:12:52
S…
Speaker 5 (Recording_280)
be there after create.
1:12:53
S…
Speaker 5 (Recording_280)
When we release the next sprint,
1:12:56
S…
Speaker 5 (Recording_280)
it will go.
1:12:58
S…
Speaker 1 (Recording_280)
We will
1:13:02
S…
Speaker 4 (Recording_280)
not change it.
1:13:04
S…
Speaker 4 (Recording_280)
We will not maintain it.
1:13:06
S…
Speaker 1 (Recording_280)
We will keep it for now,
1:13:07
S…
Speaker 4 (Recording_280)
but after the next sprint,
1:13:09
S…
Speaker 4 (Recording_280)
we will remove it.
1:13:11
S…
Speaker 4 (Recording_280)
It will also be a Docker script.
1:13:14
S…
Speaker 4 (Recording_280)
It is very difficult to
1:13:18
S…
Speaker 2 (Recording_280)
do the same thing.
1:13:19
S…
Speaker 1 (Recording_280)
No,
1:13:23
S…
Speaker 8 (Recording_280)
I don't want to do it.
1:13:24
S…
Speaker 1 (Recording_280)
You can do it daily?
1:13:43
S…
Speaker 2 (Recording_280)
I am with 5 victory points.
1:13:45
S…
Speaker 2 (Recording_280)
First time effort
1:13:49
S…
Speaker 1 (Recording_280)
will be more.
1:15:08
S…
Speaker 6 (Recording_280)
19.
1:15:09
S…
Speaker 2 (Recording_280)
Aditya,
1:15:14
S…
Speaker 4 (Recording_280)
atleast approximately tell me how much will it be for
1:15:19
S…
Speaker 4 (Recording_280)
this? Filters?
1:15:20
S…
Speaker 7 (Recording_280)
Like 3
1:15:25
S…
Speaker 1 (Recording_280)
each day.
1:15:25
S…
Speaker 7 (Recording_280)
In one story,
1:15:28
S…
Speaker 7 (Recording_280)
we need
1:15:35
S…
Speaker 1 (Recording_280)
to break down the 5th.
1:15:35
S…
Speaker 3 (Recording_280)
Then we need to break down the 5th,
1:15:39
S…
Speaker 1 (Recording_280)
Praagati.
1:15:39
S…
Speaker 7 (Recording_280)
3 each day,
1:15:41
S…
Speaker 5 (Recording_280)
Praagati.
1:15:41
S…
Speaker 7 (Recording_280)
It means to
1:15:47
S…
Speaker 7 (Recording_280)
set up the initial.
1:15:48
S…
Speaker 2 (Recording_280)
Oh,
1:15:51
S…
Speaker 3 (Recording_280)
Imroz has added the message to maximum 3 pointers.
1:15:54
S…
Speaker 3 (Recording_280)
Where did you put it?
1:15:57
S…
Speaker 3 (Recording_280)
In the storyboard 3.
1:15:59
S…
Speaker 3 (Recording_280)
In the inside group,
1:16:00
S…
Speaker 3 (Recording_280)
the BAs was tagged.
1:16:02
S…
Speaker 5 (Recording_280)
Do you have a story point?
1:16:06
S…
Speaker 5 (Recording_280)
Three?
1:16:07
S…
Speaker 8 (Recording_280)
Yes,
1:16:07
S…
Speaker 1 (Recording_280)
maximum.
1:16:08
S…
Speaker 2 (Recording_280)
Maximum?
1:16:10
S…
Speaker 1 (Recording_280)
Yes, maximum.
1:16:11
S…
Speaker 3 (Recording_280)
I mean, if there is a story beyond three,
1:16:13
S…
Speaker 3 (Recording_280)
then you have to break it,
1:16:15
S…
Speaker 3 (Recording_280)
split it.
1:16:15
S…
Speaker 3 (Recording_280)
The main goal is that...
1:16:18
S…
Speaker 5 (Recording_280)
He's doing it.
1:16:19
S…
Speaker 3 (Recording_280)
He's doing it.
1:16:19
S…
Speaker 5 (Recording_280)
He's doing it. He's doing it.
1:16:20
S…
Speaker 2 (Recording_280)
He's doing it.
1:16:21
S…
Speaker 2 (Recording_280)
No,
1:16:24
S…
Speaker 1 (Recording_280)
he's doing it.
1:16:24
S…
Speaker 5 (Recording_280)
Discussed position.
1:16:25
S…
Speaker 3 (Recording_280)
He's from the client side.
1:16:27
S…
Speaker 3 (Recording_280)
Todd, etc.
1:16:28
S…
Speaker 3 (Recording_280)
Jango raised the concern that the burn down chart is not visible.
1:16:32
S…
Speaker 3 (Recording_280)
It's consistent.
1:16:33
S…
Speaker 3 (Recording_280)
They don't see anything in the last week.
1:16:34
S…
Speaker 3 (Recording_280)
So,
1:16:37
S…
Speaker 3 (Recording_280)
it's been a discussion regarding Sanjay's call and their thoughts.
1:17:09
S…
Speaker 4 (Recording_280)
Then I showed the story
1:17:24
S…
Speaker 4 (Recording_280)
that if I did it with the three -dot menu,
1:17:27
S…
Speaker 4 (Recording_280)
then it won't be one -story pointer.
1:17:30
S…
Speaker 4 (Recording_280)
Together,
1:17:32
S…
Speaker 4 (Recording_280)
this is a five -story pointer.
1:17:34
S…
Speaker 4 (Recording_280)
So she said
1:17:39
S…
Speaker 1 (Recording_280)
no.
1:17:42
S…
Speaker 8 (Recording_280)
She said,
1:17:43
S…
Speaker 3 (Recording_280)
I mean Olga.
1:17:44
S…
Speaker 2 (Recording_280)
Olga,
1:17:46
S…
Speaker 4 (Recording_280)
Daria and Ole.
1:17:47
S…
Speaker 2 (Recording_280)
Ole said
1:17:51
S…
Speaker 4 (Recording_280)
that if,
1:17:52
S…
Speaker 4 (Recording_280)
I mean, we have to divide the stories.
1:17:55
S…
Speaker 4 (Recording_280)
So I told him that it is based on what exactly
1:17:59
S…
Speaker 4 (Recording_280)
is the output of that.
1:18:04
S…
Speaker 4 (Recording_280)
custom workflow ka humne traverse separate kiya hai,
1:18:07
S…
Speaker 4 (Recording_280)
fair and list separate kiya hai,
1:18:10
S…
Speaker 4 (Recording_280)
condition separate kiya hai,
1:18:11
S…
Speaker 4 (Recording_280)
publish and save draft be separate kiya hai but itana
1:18:15
S…
Speaker 4 (Recording_280)
separate karne ke baad me bhi it is a five story
1:18:19
S…
Speaker 4 (Recording_280)
pointer, isko agar mein all separate karun gi toh wo task level
1:18:23
S…
Speaker 1 (Recording_280)
pe jayega
1:18:28
S…
Speaker 4 (Recording_280)
But then I thought
1:18:35
S…
Speaker 4 (Recording_280)
I could review it from Ambrose.
1:18:37
S…
Speaker 4 (Recording_280)
Ambrose conveyed me something different.
1:18:39
S…
Speaker 4 (Recording_280)
Like Daria said that we'll split the
1:18:43
S…
Speaker 4 (Recording_280)
story pointer.
1:19:00
S…
Speaker 4 (Recording_280)
But then I will do something about it.
1:19:03
S…
Speaker 4 (Recording_280)
Because I will not change stories in stories.
1:19:05
S…
Speaker 4 (Recording_280)
But
1:19:10
S…
Speaker 3 (Recording_280)
Imroz's message is that Prodaria has the accountability from all
1:19:14
S…
Speaker 3 (Recording_280)
the product managers.
1:19:15
S…
Speaker 3 (Recording_280)
She is also going with the multiple
1:19:19
S…
Speaker 1 (Recording_280)
stories.
1:19:24
S…
Speaker 4 (Recording_280)
Because yesterday, I asked multiple times.
1:20:00
S…
Speaker 1 (Recording_280)
yeah so
1:20:04
S…
Speaker 6 (Recording_280)
give two one
1:20:13
S…
Speaker 6 (Recording_280)
it's mentioned in the same
1:20:17
S…
Speaker 6 (Recording_280)
chat for it's a very minor thing okay this
1:20:27
S…
Speaker 5 (Recording_280)
one yesterday night Alexi had added in the team QA channel so
1:20:31
S…
Speaker 5 (Recording_280)
yeah I'll inform him that it is from our team and we are picking
1:20:36
S…
Speaker 5 (Recording_280)
it up in the current spin
1:20:54
S…
Speaker 4 (Recording_280)
Actually,
1:20:55
S…
Speaker 5 (Recording_280)
we should have an bug created already in search.
1:20:59
S…
Speaker 4 (Recording_280)
Change
1:21:06
S…
Speaker 4 (Recording_280)
rule,
1:21:08
S…
Speaker 6 (Recording_280)
there
1:21:31
S…
Speaker 1 (Recording_280)
are some improvements.
1:22:07
S…
Speaker 6 (Recording_280)
It's the
1:22:26
S…
Speaker 5 (Recording_280)
same time.
1:23:50
S…
Speaker 2 (Recording_280)
You can do both investigations.
1:23:51
S…
Speaker 2 (Recording_280)
I mean KYC,
1:23:53
S…
Speaker 2 (Recording_280)
ML, Paralegal and next sprint.
1:23:55
S…
Speaker 1 (Recording_280)
No,
1:23:56
S…
Speaker 2 (Recording_280)
you can integrate both in next.
1:23:57
S…
Speaker 3 (Recording_280)
If possible.
1:23:59
S…
Speaker 1 (Recording_280)
Yes, you have to do that.
1:24:00
S…
Speaker 7 (Recording_280)
But
1:24:06
S…
Speaker 2 (Recording_280)
if you look at PI according,
1:24:07
S…
Speaker 2 (Recording_280)
I think in sprint 3.
1:24:09
S…
Speaker 2 (Recording_280)
In third week.
1:24:11
S…
Speaker 3 (Recording_280)
Workflow instance.
1:24:14
S…
Speaker 1 (Recording_280)
This time we got so much time,
1:24:15
S…
Speaker 1 (Recording_280)
we had development,
1:24:17
S…
Speaker 1 (Recording_280)
otherwise devs are free in third week.
1:24:21
S…
Speaker 1 (Recording_280)
Investigation can be done.
1:24:38
S…
Speaker 7 (Recording_280)
You hear the sound of
1:24:45
S…
Speaker 8 (Recording_280)
the spillover?
1:24:48
S…
Speaker 7 (Recording_280)
Yes,
1:24:55
S…
Speaker 2 (Recording_280)
the spillover will come.
1:24:56
S…
Speaker 2 (Recording_280)
The custom templates will come.
1:25:02
S…
Speaker 6 (Recording_280)
And two points from QA would be added.
1:25:05
S…
Speaker 3 (Recording_280)
Yes,
1:25:06
S…
Speaker 2 (Recording_280)
add it, add it,
1:25:07
S…
Speaker 4 (Recording_280)
cut it, cut it.
1:25:08
S…
Speaker 5 (Recording_280)
Yes.
1:25:10
S…
Speaker 2 (Recording_280)
And that's what he said
1:25:15
S…
Speaker 2 (Recording_280)
about the ID change.
1:25:17
S…
Speaker 2 (Recording_280)
No,
1:25:20
S…
Speaker 1 (Recording_280)
no, no, that's not the link.
1:25:22
S…
Speaker 1 (Recording_280)
What happened?
1:25:23
S…
Speaker 2 (Recording_280)
That's also the support
1:25:27
S…
Speaker 1 (Recording_280)
ticket of Rik.
1:25:30
S…
Speaker 1 (Recording_280)
Yes, but he said he did not reply to him.
1:25:34
S…
Speaker 1 (Recording_280)
How will he do that?
1:25:35
S…
Speaker 3 (Recording_280)
No, no, I don't remember.
1:25:36
S…
Speaker 2 (Recording_280)
We'll see his design when we get to see him.
1:25:39
S…
Speaker 1 (Recording_280)
Yes.
1:25:40
S…
Speaker 1 (Recording_280)
You know,
1:25:42
S…
Speaker 1 (Recording_280)
in the morning,
1:25:43
S…
Speaker 1 (Recording_280)
in the demo,
1:25:45
S…
Speaker 1 (Recording_280)
I didn't have a setting fee.
1:25:47
S…
Speaker 1 (Recording_280)
I didn't have a setting fee.
1:25:50
S…
Speaker 1 (Recording_280)
I didn't have a setting fee.
1:25:51
S…
Speaker 3 (Recording_280)
It's not acceptable.
1:25:52
S…
Speaker 5 (Recording_280)
It's
1:26:00
S…
Speaker 1 (Recording_280)
a profile.
1:26:01
S…
Speaker 1 (Recording_280)
It's a profile.
1:26:03
S…
Speaker 1 (Recording_280)
It's up.
1:26:05
S…
Speaker 6 (Recording_280)
We checked it up yesterday.
1:26:08
S…
Speaker 2 (Recording_280)
Now we've also got two bugs,
1:26:10
S…
Speaker 2 (Recording_280)
one on Rockford and one on Strikers.
1:26:12
S…
Speaker 3 (Recording_280)
I've
1:26:20
S…
Speaker 2 (Recording_280)
added a Kaniyam mail,
1:26:22
S…
Speaker 2 (Recording_280)
but I didn't
1:26:27
S…
Speaker 1 (Recording_280)
have any revert.
1:26:28
S…
Speaker 2 (Recording_280)
I've also added a brand.
1:26:29
S…
Speaker 2 (Recording_280)
I've also added a brand.
1:26:32
S…
Speaker 2 (Recording_280)
I've also added a migration script
1:26:36
S…
Speaker 2 (Recording_280)
to our Divox.
1:26:38
S…
Speaker 2 (Recording_280)
and the future for import deal logic will be
1:26:43
S…
Speaker 2 (Recording_280)
found in the current sprint release.
1:26:45
S…
Speaker 3 (Recording_280)
No,
1:26:49
S…
Speaker 2 (Recording_280)
no, it was on the prod for the new west organization.
1:26:51
S…
Speaker 3 (Recording_280)
But
1:26:57
S…
Speaker 2 (Recording_280)
the revert didn't come,
1:26:58
S…
Speaker 2 (Recording_280)
I'll wait until the night,
1:26:59
S…
Speaker 2 (Recording_280)
so I'll put it on top up.
1:27:06
S…
Speaker 2 (Recording_280)
We had to save the steps and save it in the title or description
1:27:10
S…
Speaker 2 (Recording_280)
and then change the status task and she would be
1:27:14
S…
Speaker 3 (Recording_280)
able to do it.
1:27:15
S…
Speaker 5 (Recording_280)
Okay,
1:27:19
S…
Speaker 2 (Recording_280)
I think now it's 32 story points.
1:27:21
S…
Speaker 2 (Recording_280)
Two story points I think from QA side to regression and validation,
1:27:25
S…
Speaker 2 (Recording_280)
it will be 34.
1:27:25
S…
Speaker 2 (Recording_280)
I think 34 and considering Bandai
1:27:31
S…
Speaker 2 (Recording_280)
Chutti, Kunal,
1:27:32
S…
Speaker 2 (Recording_280)
Abhinav and Hamid will be in the third week.
1:27:40
S…
Speaker 1 (Recording_280)
I was thinking
1:27:45
S…
Speaker 1 (Recording_280)
about some improvements.
1:27:46
S…
Speaker 2 (Recording_280)
Improvements or something?
1:28:22
S…
Speaker 1 (Recording_280)
I was asked to
1:28:27
S…
Speaker 1 (Recording_280)
remove users for
1:28:31
S…
Speaker 1 (Recording_280)
invitations for invitations for invitations
1:28:37
S…
Speaker 3 (Recording_280)
for invitations for invitations for invitations for
1:28:41
S…
Speaker 3 (Recording_280)
invitations
1:28:47
S…
Speaker 3 (Recording_280)
for invitations for invitations for invitations
1:29:50
S…
Speaker 6 (Recording_280)
I think I have given
1:29:54
S…
Speaker 6 (Recording_280)
one bug ID in the chart and we can add it to the current sprint
1:29:59
S…
Speaker 6 (Recording_280)
35414.
1:30:28
S…
Speaker 2 (Recording_280)
and we will have those bugs that are v1 specific bugs and
1:30:32
S…
Speaker 2 (Recording_280)
we are revamping them in v2 so we have to close them in
1:30:36
S…
Speaker 2 (Recording_280)
sprint so it will be clear in the back log
1:31:04
S…
Speaker 2 (Recording_280)
No, the V2 bugs said Todd.
1:31:07
S…
Speaker 2 (Recording_280)
He also said it on the call yesterday.
1:31:10
S…
Speaker 2 (Recording_280)
Because the V1 bugs are
1:31:14
S…
Speaker 2 (Recording_280)
not deprecated,
1:31:16
S…
Speaker 2 (Recording_280)
so that's why the product has already commented that
1:31:21
S…
Speaker 2 (Recording_280)
if the workflow is new,
1:31:22
S…
Speaker 2 (Recording_280)
we need to work on it.
1:31:24
S…
Speaker 2 (Recording_280)
We had a very first discussion regarding the same,
1:31:28
S…
Speaker 2 (Recording_280)
but we couldn't close it because those were in the backlog.
1:31:31
S…
Speaker 2 (Recording_280)
So we have to close it.
1:31:37
S…
Speaker 6 (Recording_280)
Now we need to live,
1:31:38
S…
Speaker 6 (Recording_280)
we might get some
1:31:42
S…
Speaker 6 (Recording_280)
support tickets before we prioritize and take a
1:31:46
S…
Speaker 6 (Recording_280)
sprint so that it would be better.
1:31:48
S…
Speaker 5 (Recording_280)
Like
1:31:55
S…
Speaker 6 (Recording_280)
we had already made a bunch,
1:31:56
S…
Speaker 6 (Recording_280)
but Oleksii has pointed out as
1:32:00
S…
Speaker 6 (Recording_280)
a good agreement.
1:32:02
S…
Speaker 6 (Recording_280)
I think Oleksii has regressed a little bit,
1:32:05
S…
Speaker 6 (Recording_280)
so I got it.
1:32:07
S…
Speaker 3 (Recording_280)
I am thinking,
1:32:08
S…
Speaker 3 (Recording_280)
not sure.
1:32:36
S…
Speaker 2 (Recording_280)
Ticket Assignment,
1:32:37
S…
Speaker 2 (Recording_280)
then Hamid,
1:32:38
S…
Speaker 2 (Recording_280)
you can see it or do it now.
1:32:40
S…
Speaker 4 (Recording_280)
It will take 5 minutes.
1:32:41
S…
Speaker 2 (Recording_280)
If you want to do
1:32:45
S…
Speaker 1 (Recording_280)
it internally.
1:33:09
S…
Speaker 3 (Recording_280)
This one time trigger Kunal and I'll be
1:33:13
S…
Speaker 1 (Recording_280)
walking.
1:33:13
S…
Speaker 7 (Recording_280)
Yes,
1:33:14
S…
Speaker 3 (Recording_280)
yes,
1:33:52
S…
Speaker 1 (Recording_280)
yes.
1:33:52
S…
Speaker 5 (Recording_280)
Chik
1:34:00
S…
Speaker 5 (Recording_280)
hai. Chik
1:34:06
S…
Speaker 2 (Recording_280)
hai. Prakati, first you put one message to her,
1:34:08
S…
Speaker 2 (Recording_280)
for the filters, because she'll be on leave tomorrow.
1:34:11
S…
Speaker 2 (Recording_280)
After that,
1:34:11
S…
Speaker 2 (Recording_280)
I'll put a tentative sprint goal.
1:34:13
S…
Speaker 1 (Recording_280)
Chik
1:34:26
S…
Speaker 4 (Recording_280)
hai. Thanks everyone.
1:34:27
S…
Speaker 2 (Recording_280)
Anything else from anyone?
1:34:28
S…
Speaker 5 (Recording_280)
Nope.
1:34:36
S…
Speaker 4 (Recording_280)
Thank you.
1:34:37
S…
Speaker 8 (Recording_280)
Bye.
1:34:38
S…
Speaker 8 (Recording_280)
Bye.
This transcript was generated by AI (automatic speech recognition). May contain errors — verify against the original audio for critical use. AI policy
Samandráttur
Click Summarize to generate an AI summary of this transcript.
Summating...
Spørg AI um hetta transkriptión
Tað er ein spurningur um, hvussu nógvar ferðir ein kann skriva og lesa.