0:0:0.0 --> 0:0:3.40
Keith Low
On for for this licensing that.
0:0:4.920 --> 0:0:11.10
Keith Low
For not having the SSO that we need a feature flag and it's supposed to be a separate discussion.
0:0:11.340 --> 0:0:12.940
Keith Low
So I think here we are now.
0:0:13.710 --> 0:0:14.920
Keith Low
Uh, just a minute.
0:0:14.930 --> 0:0:16.320
Keith Low
Can you describe to the real?
0:0:16.330 --> 0:0:18.760
Keith Low
I think what you mentioned to me and chosen earlier.
0:0:22.740 --> 0:0:28.970
Jasmine Tang
Umm, I think this is referring to the previous meeting, right?
0:0:28.980 --> 0:0:38.320
Jasmine Tang
That a you and thousand and you have it and talk about the feature flags that will need to be sick in the platform.
0:0:38.470 --> 0:0:50.330
Jasmine Tang
So yeah, so would like just to a plan for me, if you really, yeah, what what is the like a a thing that the platform need to take note on these and yeah the detail of it.
0:0:50.340 --> 0:0:51.630
Jasmine Tang
Yeah, Duraid, maybe you can share.
0:0:52.260 --> 0:0:54.10
Jasmine Tang
Uh, with us on this.
0:0:54.90 --> 0:0:59.220
Jasmine Tang
And then right now in the meeting room, I have Eric Parking and CK with me as well, yeah.
0:1:0.630 --> 0:1:3.500
Duraid Wadie
Sorry, I just couldn't get the context.
0:1:3.550 --> 0:1:7.740
Duraid Wadie
I can't just remind myself exactly the about what exactly.
0:1:7.750 --> 0:1:8.460
Duraid Wadie
Sorry that Jasmine.
0:1:9.560 --> 0:1:14.490
Jasmine Tang
Yeah, I think it's regarding the arts licensing model is different with the other product.
0:1:15.40 --> 0:1:20.840
Jasmine Tang
So how do we differentiate that in the Northeast product heating up?
0:1:20.170 --> 0:1:21.550
Duraid Wadie
Ohh, I'd say it's it's.
0:1:21.560 --> 0:1:22.940
Duraid Wadie
Yeah, yeah, yeah, I think I.
0:1:23.70 --> 0:1:23.820
Duraid Wadie
OK, OK.
0:1:23.830 --> 0:1:26.370
Duraid Wadie
So it's actually about licensing, not SSO.
0:1:26.800 --> 0:1:27.670
Keith Low
Uh, OK.
0:1:27.900 --> 0:1:28.940
Keith Low
Uh, so-called confusion.
0:1:27.20 --> 0:1:29.160
Jasmine Tang
Guys, OK. Yes.
0:1:32.900 --> 0:1:34.960
Duraid Wadie
So is the SSO licensing, sorry.
0:1:35.410 --> 0:1:37.640
Jasmine Tang
And I said that is like really the licensing.
0:1:37.750 --> 0:1:38.150
Keith Low
I don't think.
0:1:37.650 --> 0:1:39.110
Jasmine Tang
No, because of that, that's all.
0:1:45.610 --> 0:1:45.790
Keith Low
Sorry.
0:1:45.330 --> 0:1:48.270
Jasmine Tang
Nadia is that isn't seeing licensing? Yeah.
0:1:48.720 --> 0:1:49.190
Duraid Wadie
It yeah.
0:1:49.200 --> 0:1:49.410
Duraid Wadie
Yeah.
0:1:49.420 --> 0:1:49.700
Duraid Wadie
Yeah.
0:1:49.710 --> 0:1:50.150
Duraid Wadie
OK.
0:1:50.220 --> 0:1:50.590
Duraid Wadie
OK.
0:1:50.600 --> 0:1:51.40
Duraid Wadie
Just.
0:1:51.150 --> 0:1:52.760
Duraid Wadie
Yeah, just trying to figure it out. My head.
0:1:52.920 --> 0:1:54.530
Duraid Wadie
Yeah, right.
0:1:54.540 --> 0:2:13.980
Duraid Wadie
So the licensing we talked about, the actual thing is the arc is bit different that's made when you on board a tenant on Ark, all the product instances within the tenant, but they need to have the same license numbers for all its types.
0:2:13.990 --> 0:2:32.400
Duraid Wadie
For example, let's say if you bought, uh two types or three types for that specific tenant, or the product instances for that specific product should have all the same numbers for those types, that wouldn't be able to say that that they don't wanna do that.
0:2:32.410 --> 0:2:34.530
Duraid Wadie
Actually know they won't be able to say they don't wanna do that.
0:2:34.540 --> 0:2:46.110
Duraid Wadie
For example, let's say if you have, let's say, an internal audit 10 and let's say enterprise risk 20 does mean those numbers applies to all the product instances within that tenant.
0:2:46.760 --> 0:2:47.360
Duraid Wadie
That makes sense.
0:2:47.370 --> 0:3:1.910
Duraid Wadie
So that's the bit of logic happens on all the output interview, but for example if you would have work right on the same tenant, it won't follow that logic because work life has got a different licence model that makes sense.
0:3:1.920 --> 0:3:6.890
Duraid Wadie
For example, I don't know, let's say content trader and content editors for example and work right.
0:3:6.900 --> 0:3:8.770
Duraid Wadie
I don't know what that means, but just made them up.
0:3:9.930 --> 0:3:15.420
Duraid Wadie
Those wouldn't follow the same logic as as ARC, but that makes sense.
0:3:15.910 --> 0:3:35.140
Duraid Wadie
So at the product level definition of, I would say 4 when we onboard was product will probably would have some flag with say for example apply licensing across all its product instances about.
0:3:35.150 --> 0:3:36.760
Duraid Wadie
That's the really what I'm talking about here.
0:3:36.770 --> 0:3:45.170
Duraid Wadie
So when you would see that flag somewhere, you would actually understand that there's a logic for all those product instances within the tenant followed this model.
0:3:50.90 --> 0:3:51.80
Duraid Wadie
Does that make sense?
0:3:56.120 --> 0:3:56.430
Jasmine Tang
Yeah.
0:3:56.440 --> 0:4:5.480
Jasmine Tang
So the logic is to follow the feature flag is to, uh, make us able to differentiate, let's say example it is for archiving.
0:4:5.490 --> 0:4:8.570
Jasmine Tang
We able to apply the logic that you mentioned.
0:4:8.580 --> 0:4:13.570
Jasmine Tang
All the product instances would be have the same license count for the respective license type.
0:4:14.720 --> 0:4:15.80
Duraid Wadie
Yeah.
0:4:15.90 --> 0:4:19.70
Duraid Wadie
So every time we on board the product and instance, we know from which product is coming from.
0:4:19.990 --> 0:4:21.640
Duraid Wadie
So that makes sense, right?
0:4:21.960 --> 0:4:22.110
Jasmine Tang
Yeah.
0:4:22.120 --> 0:4:22.550
Jasmine Tang
Do you have?
0:4:22.600 --> 0:4:23.530
Jasmine Tang
Yeah, I have a question.
0:4:23.540 --> 0:4:24.890
Jasmine Tang
Do you let's say example, right?
0:4:24.940 --> 0:4:28.50
Jasmine Tang
This one is like art is different with other product, right?
0:4:28.100 --> 0:4:30.210
Jasmine Tang
How about we be a case like example?
0:4:30.220 --> 0:4:37.780
Jasmine Tang
Then work rite is different with maybe opt sanction and then different with Devonway things and that I mean let's say they.
0:4:37.20 --> 0:4:38.170
Duraid Wadie
He might be. Yeah.
0:4:38.180 --> 0:4:38.400
Duraid Wadie
Yeah.
0:4:38.410 --> 0:4:41.530
Duraid Wadie
I mean, there's the truth is, actually it might be right.
0:4:42.100 --> 0:4:42.560
Jasmine Tang
OK.
0:4:42.0 --> 0:4:48.540
Duraid Wadie
But the the idea is that specific flag on the product with the side.
0:4:50.120 --> 0:4:52.710
Duraid Wadie
Do they have the same licensing?
0:4:52.720 --> 0:4:54.10
Duraid Wadie
What's not open like anymore?
0:4:54.20 --> 0:4:55.70
Duraid Wadie
Did they actually have?
0:4:55.300 --> 0:5:7.700
Duraid Wadie
Do they apply the same rule like we're gonna ask the product people when they're gonna board that say Devonway to the platform when you on board the tenant does all the licensing cross all your instances the same, you just have that flag on.
0:5:8.750 --> 0:5:12.890
Duraid Wadie
I would talk to the comment that flag will be owned by default if that makes sense.
0:5:14.250 --> 0:5:18.770
Duraid Wadie
So part of the product, the partition when you add that flag, you switch on by default.
0:5:20.980 --> 0:5:23.810
Duraid Wadie
But that's again, that's that's at the product level.
0:5:23.860 --> 0:5:27.610
Duraid Wadie
Yeah, but when you come to correct let's say and this then.
0:5:27.620 --> 0:5:35.490
Duraid Wadie
So they trying to update a license you would know because you can trace that back to that specific feature at the product level.
0:5:38.360 --> 0:5:39.100
Keith Low
Doing in this.
0:5:38.440 --> 0:5:41.240
Duraid Wadie
I want the Starling mean right, so I'm gonna take it.
0:5:42.340 --> 0:5:44.670
Keith Low
In this case, where does the feature flag sits?
0:5:44.760 --> 0:5:45.100
Keith Low
No.
0:5:45.820 --> 0:5:48.820
Keith Low
Yeah, I home itself or provisioning.
0:5:48.570 --> 0:5:50.140
Duraid Wadie
Yeah, that's a product feature.
0:5:50.150 --> 0:5:50.350
Duraid Wadie
Yeah.
0:5:50.360 --> 0:5:56.590
Duraid Wadie
Yeah, it's a product feature because that's the only place we can add that because the tenant could have multiple products.
0:5:59.970 --> 0:6:2.0
Duraid Wadie
So I mean, Eric knows this ready.
0:6:2.10 --> 0:6:9.350
Duraid Wadie
So when when you when you create Ideagen Home, the first thing you need to create a product, a product version that makes sense.
0:6:9.360 --> 0:6:22.800
Duraid Wadie
And that product would have just, let's say some some tick box or Boolean thing is as does all product instances have the same licenses, simple as that really or whatever they call it and you, you switch on by default.
0:6:22.860 --> 0:6:30.0
Duraid Wadie
So that's mean, every time you unbolt a product instance of that product would have the same licensing that you already have for that specific tenant.
0:6:34.920 --> 0:6:38.100
Jasmine Tang
Yeah, I think in that case, yeah, it should sit with the product.
0:6:39.120 --> 0:6:43.900
Jasmine Tang
Umm, but on top of it, this I'm thinking would that be a different?
0:6:43.950 --> 0:6:44.280
Jasmine Tang
Is it?
0:6:44.290 --> 0:6:47.720
Jasmine Tang
Will it be the same product but different product version will have different behavior?
0:6:48.310 --> 0:6:48.610
Jasmine Tang
Do we?
0:6:51.130 --> 0:6:51.330
Jasmine Tang
Yeah.
0:6:48.470 --> 0:6:54.880
Duraid Wadie
I mean, at the moment out of right it's the product version because the multitenant system, right?
0:6:55.480 --> 0:6:55.660
Jasmine Tang
Yeah.
0:6:54.950 --> 0:6:58.720
Duraid Wadie
So it's only when version anyway, so that probably version will never change.
0:7:0.300 --> 0:7:1.400
Jasmine Tang
Right. OK.
0:7:2.420 --> 0:7:14.150
Duraid Wadie
Because we are not having any single, I mean I'm saying that's right so far actually integrating with whom you would have different version when we onboard them.
0:7:14.200 --> 0:7:19.840
Duraid Wadie
I would say the, I mean, it's up to you what you wanna add this actually at the product version or the product itself.
0:7:19.850 --> 0:7:20.140
Duraid Wadie
Us.
0:7:20.150 --> 0:7:23.410
Duraid Wadie
I don't think so that big deal differences, right?
0:7:24.950 --> 0:7:25.210
Jasmine Tang
Yeah.
0:7:24.900 --> 0:7:31.550
Duraid Wadie
But I guess the version is make probably more sense is that they say gonna this version one or something version?
0:7:31.690 --> 0:7:33.350
Duraid Wadie
Might have something other definition rights.
0:7:34.310 --> 0:7:41.280
Jasmine Tang
Yeah, because I I was thinking because now when we actually spin up a product instance, we are actually using a version of a product.
0:7:41.660 --> 0:7:41.840
Duraid Wadie
Yeah.
0:7:41.750 --> 0:7:43.0
Jasmine Tang
So I'm just thinking.
0:7:43.330 --> 0:7:45.100
Jasmine Tang
Ohh I'd be a case in future.
0:7:45.110 --> 0:7:49.960
Jasmine Tang
Sadly outcome and say ohh we wanna change the licensing model in the newer version that different.
0:7:49.360 --> 0:7:52.400
Duraid Wadie
Yeah, I think it makes sense.
0:7:52.410 --> 0:7:53.340
Duraid Wadie
The Minutes of the attic.
0:7:53.350 --> 0:7:55.40
Duraid Wadie
I think you know this stuff better than myself.
0:7:55.50 --> 0:7:57.750
Duraid Wadie
The best whether I think the version would make sense to be honest with you.
0:7:59.100 --> 0:7:59.790
Jasmine Tang
Right.
0:7:59.880 --> 0:8:1.480
Jasmine Tang
Not sure what's the guys here with you.
0:8:3.540 --> 0:8:6.690
Jasmine Tang
Is it really a a turn on and off thing?
0:8:7.810 --> 0:8:8.70
Duraid Wadie
That's.
0:8:7.160 --> 0:8:15.90
Jasmine Tang
What if we have a different like different licensing model that we need to support in the future? No.
0:8:14.500 --> 0:8:15.540
Duraid Wadie
It's not.
0:8:15.620 --> 0:8:20.790
Duraid Wadie
This is not model actually, so we always put in licensing of the product instance level, right?
0:8:20.800 --> 0:8:23.420
Duraid Wadie
That's that's the basic foundation of it.
0:8:22.540 --> 0:8:24.470
Jasmine Tang
Yes, yes, correct.
0:8:27.500 --> 0:8:27.890
SueAnn See
Yeah.
0:8:23.680 --> 0:8:28.460
Duraid Wadie
That's more of a yeah, more of a business logic that if that makes sense.
0:8:27.940 --> 0:8:28.550
SueAnn See
OHS.
0:8:28.780 --> 0:8:43.730
SueAnn See
So maybe I can ask the question in a different way, right where one product have a possibility of having licenses that apply across product instances and also some other license type that does not apply across product instances.
0:8:44.190 --> 0:8:44.670
SueAnn See
We didn't.
0:8:44.350 --> 0:8:45.20
Duraid Wadie
Thus, right.
0:8:44.680 --> 0:8:46.400
SueAnn See
One product itself, yeah.
0:8:46.420 --> 0:8:46.950
Duraid Wadie
Yeah.
0:8:46.960 --> 0:8:49.890
Duraid Wadie
So for example, take couple slow right?
0:8:49.850 --> 0:8:50.150
SueAnn See
Hmm.
0:8:58.170 --> 0:8:58.350
SueAnn See
Yep.
0:8:50.460 --> 0:8:59.620
Duraid Wadie
It's different than couples that self I, so there might be sold as one product, but the licensing of them are different.
0:9:0.290 --> 0:9:0.470
SueAnn See
Yeah.
0:9:2.60 --> 0:9:8.730
Duraid Wadie
So for example, they're going on board the couple slow as a product that is only version a couple slow.
0:9:12.330 --> 0:9:12.630
SueAnn See
OK.
0:9:8.740 --> 0:9:15.630
Duraid Wadie
So product and its own version and something else, right and that that's how you think about it for a second, that's just more of a business logic.
0:9:15.720 --> 0:9:21.10
Duraid Wadie
The balance with this not doing anything different, so the licensing still at the product instance level.
0:9:21.580 --> 0:9:27.330
Duraid Wadie
But when you onboard the new product instance level, you're gonna go back again to the product to this product version.
0:9:27.680 --> 0:9:29.250
Duraid Wadie
Do they have this business logic?
0:9:29.260 --> 0:9:29.670
Duraid Wadie
Yes.
0:9:30.0 --> 0:9:38.170
Duraid Wadie
Then you take all of the licensing, all of the the license type, the numbers, and he just apply it to the product menu product instance if that makes sense.
0:9:40.920 --> 0:9:45.610
Jasmine Tang
Umm it is so in regards to that question.
0:9:45.620 --> 0:9:52.640
Jasmine Tang
So even though the same product, as long as it's different product version, so it can be determined by different product version.
0:9:55.150 --> 0:9:55.870
Duraid Wadie
I think so.
0:9:54.880 --> 0:9:57.150
Jasmine Tang
So a product, it's just, yeah.
0:9:57.160 --> 0:10:8.250
Jasmine Tang
So a product instance that derive from a specific product version and based on that product version flag then the license behavior will be based on that, yeah.
0:10:9.730 --> 0:10:10.120
Duraid Wadie
Yeah.
0:10:10.130 --> 0:10:15.610
Duraid Wadie
Yeah, but again, this is just a lot a little business logic, Eric.
0:10:16.590 --> 0:10:19.170
Jasmine Tang
Yep, yeah, I understand.
0:10:19.180 --> 0:10:31.800
Jasmine Tang
This is just a flag and then when we do the actually, uh possibly license assigning the time we will use this flag to determine which logic to actually the business logic to actually follows.
0:10:38.920 --> 0:10:44.110
Jasmine Tang
But it should apply across all the instance or just a specific instance, yeah?
0:10:47.300 --> 0:10:48.640
Jasmine Tang
For this specific use case.
0:10:50.860 --> 0:10:51.230
Duraid Wadie
Yeah.
0:10:51.240 --> 0:11:5.760
Duraid Wadie
I mean, just think about it then just make sure you would switch this on by default anyway, so every time you on board the product version or anything, just by default switch this on and if somebody tell us this is different than you switch it off.
0:11:6.230 --> 0:11:9.470
Duraid Wadie
For that something I mean throw an API or whatever is density.
0:11:11.590 --> 0:11:11.770
Jasmine Tang
Yeah.
0:11:9.550 --> 0:11:14.990
Duraid Wadie
So the big deal, this thing I would say you have it on by default and we switch off when we know.
0:11:17.400 --> 0:11:17.720
Jasmine Tang
Umm.
0:11:26.270 --> 0:11:26.810
Jasmine Tang
Translator.
0:11:29.500 --> 0:11:30.980
Jasmine Tang
So and vision.
0:11:30.330 --> 0:11:31.760
Lim Zhao Siang
I Duraid I have a question Sir.
0:11:31.770 --> 0:11:54.510
Lim Zhao Siang
So so from provisioning standpoint, right, so let's say clubs create uses the provisioning create new environments, right where you know they can create tenant tenant users for instances and under the product instances, right, they will include the licensing details as well like the user count and also the license type, right.
0:11:55.110 --> 0:11:55.470
Duraid Wadie
Uh-huh.
0:11:54.820 --> 0:12:4.880
Lim Zhao Siang
So let's say if they create multiple product instances at that time right, how does this feature flag works then?
0:12:7.710 --> 0:12:16.380
Duraid Wadie
So at the moment they asked the multiple times about the licenses, but every product instance or do you ask them once?
0:12:17.810 --> 0:12:26.810
Lim Zhao Siang
Umm, they actually can include more than one product instances when they create the new environment.
0:12:27.390 --> 0:12:28.120
Lim Zhao Siang
Maybe let me.
0:12:27.560 --> 0:12:28.970
Duraid Wadie
But the licenses start.
0:12:28.980 --> 0:12:32.120
Duraid Wadie
I mean, at the moment the at the moment, do we have the UI for or not?
0:12:34.60 --> 0:12:37.60
Lim Zhao Siang
At this moment we are creating the UI.
0:12:38.420 --> 0:12:38.710
Duraid Wadie
Uh.
0:12:38.310 --> 0:12:39.170
Keith Low
Very simple UI.
0:12:38.20 --> 0:12:40.280
Lim Zhao Siang
You have not deployed, it's.
0:12:40.290 --> 0:12:45.90
Lim Zhao Siang
Yeah, basically they can at this moment like clouds probably.
0:12:45.150 --> 0:12:50.640
Lim Zhao Siang
I mean at at this very moment like they still have to use, you know, postman to submit the.
0:12:49.420 --> 0:12:51.250
Duraid Wadie
Yeah, well, this is what I'm talking about.
0:12:51.260 --> 0:13:5.90
Duraid Wadie
Because of we have you, I will can control this because you would need to reach out to idea Gen home to say does do you have this flag ticket if you have that flag ticked, you won't be able to allow them to.
0:13:5.180 --> 0:13:6.290
Duraid Wadie
So what would happen?
0:13:6.400 --> 0:13:8.280
Duraid Wadie
You would have in your UI.
0:13:9.500 --> 0:13:12.490
Duraid Wadie
I want to create 5 instances, 1 new tenant right?
0:13:13.430 --> 0:13:20.140
Duraid Wadie
But that flag is being ticked in the product or the product version, whatever the guys decide on, you would need to read that flag.
0:13:20.210 --> 0:13:25.700
Duraid Wadie
You won't be able to allow them to read to enter this pair instance.
0:13:26.250 --> 0:13:27.80
Duraid Wadie
That makes sense.
0:13:27.180 --> 0:13:30.850
Duraid Wadie
So you would you would show this at the tenant level when you create it.
0:13:30.910 --> 0:13:36.740
Duraid Wadie
It's just that UI thing to forget about how it happens at the payload at the API level that just not matters.
0:13:37.10 --> 0:13:53.160
Duraid Wadie
What really matters is just that you either controls it so once you read that flag at the tenant level, when you put a new customer details what it's licenses, then you start putting the numbers and those will be applied for every single product instances and they won't be able to go granular level to that.
0:13:55.270 --> 0:13:58.20
Lim Zhao Siang
Yeah, that it's on the UI side, right.
0:13:58.30 --> 0:14:5.460
Lim Zhao Siang
If I think at this moment right, probably think UI is not part of the uh for licensing, right?
0:14:5.760 --> 0:14:6.350
Lim Zhao Siang
I know it's taken.
0:14:6.360 --> 0:14:8.800
Lim Zhao Siang
I think that it's a separate timeline.
0:14:8.260 --> 0:14:9.50
Duraid Wadie
So that's good.
0:14:8.570 --> 0:14:9.60
Keith Low
He's not.
0:14:9.70 --> 0:14:10.110
Keith Low
He's not a priority now.
0:14:11.800 --> 0:14:26.990
Duraid Wadie
So yeah, but so you we have to really given them you know provide like guides the license type and the numbers that needs to be the same cross all the product and stances we have to tell them that though I know how to guide when they put those.
0:14:29.810 --> 0:14:31.380
Lim Zhao Siang
Alright, so that is true.
0:14:29.940 --> 0:14:31.410
Duraid Wadie
You know when they can use like, yes.
0:14:31.830 --> 0:14:32.960
Lim Zhao Siang
True postman, right?
0:14:34.30 --> 0:14:34.270
Duraid Wadie
Yeah.
0:14:32.970 --> 0:14:35.900
Lim Zhao Siang
If they are using API to submit, we have to provide them a guide.
0:14:35.910 --> 0:14:42.120
Lim Zhao Siang
So once the UI is ready, so we have to find we have to read the flag from platform right?
0:14:42.790 --> 0:14:43.10
Duraid Wadie
Yeah.
0:14:42.130 --> 0:14:46.210
Lim Zhao Siang
So that and then we will sort of restrict them in the UI itself, OK, got it.
0:14:48.290 --> 0:14:48.950
Lim Zhao Siang
Got it, got it.
0:14:49.510 --> 0:14:49.730
Duraid Wadie
Yeah.
0:14:59.260 --> 0:15:0.90
Keith Low
Any other question?
0:15:6.480 --> 0:15:9.150
Jasmine Tang
Different repeat a question.
0:15:9.160 --> 0:15:9.960
Jasmine Tang
Just a mute.
0:15:11.270 --> 0:15:31.50
Jasmine Tang
Just want to check with the the better the flat right for multiple provenance this so basically the the flat will be assigned to each and every product instance it occurring or there will be a single flap for just 111 tenant.
0:15:31.560 --> 0:15:34.650
Jasmine Tang
No, the flag should be on the version the product version.
0:15:34.980 --> 0:15:42.620
Jasmine Tang
So when you create a product instance right then you will know this product instance is using which version to create.
0:15:43.30 --> 0:15:44.840
Jasmine Tang
Then you will know that flag.
0:15:44.990 --> 0:15:48.600
Jasmine Tang
So from there you will apply the license based on that.
0:15:50.940 --> 0:16:0.30
Jasmine Tang
And the logic when comes to the logic of how we assign a user with a license, we link a user with a license.
0:16:0.540 --> 0:16:12.30
Jasmine Tang
Then we would know whether it would just beat up the license from one specific product instance or all the product instance of this version of uh product version.
0:16:14.710 --> 0:16:16.530
Jasmine Tang
We pending on that particular flag.
0:16:19.900 --> 0:16:26.730
Jasmine Tang
Does this feature flag is to basically tell a specific product instance that derived from a specific product version?
0:16:27.140 --> 0:16:33.370
Jasmine Tang
Should it be using arc model of licensing or not as mono licensing?
0:16:38.570 --> 0:16:39.820
Jasmine Tang
Is it possible to have?
0:16:39.830 --> 0:16:44.260
Jasmine Tang
Uh, they don't have up product and also non.
0:16:44.270 --> 0:16:45.480
Jasmine Tang
Yes, yes.
0:16:45.490 --> 0:16:47.30
Jasmine Tang
So the feature pack will be different.
0:16:47.940 --> 0:16:54.950
Jasmine Tang
Uh, by default, as direct mentioned, it should be by how artwork now, but they can put it off.
0:16:55.850 --> 0:16:57.960
Jasmine Tang
So once enough people should behave differently.
0:16:58.390 --> 0:17:6.570
Jasmine Tang
In fact, even our product itself, two different version one can have what is being defined now another one you can be shut off.
0:17:8.960 --> 0:17:9.830
Jasmine Tang
He's about understand.
0:17:11.140 --> 0:17:12.80
Jasmine Tang
So we have the flexibility.
0:17:12.770 --> 0:17:16.180
Duraid Wadie
That that's why it actually understand the perfect actually, Eric.
0:17:16.370 --> 0:17:16.700
Duraid Wadie
Yeah.
0:17:16.710 --> 0:17:21.580
Duraid Wadie
So this this is more of just a logic that that's not really applying anything.
0:17:21.590 --> 0:17:49.30
Duraid Wadie
So the licensing types, the numbers stays by product understands, but that's just a logic in your UI in the platform when it come to assign uh, you know, like I would say users or to licensing and you would show that number of the product and sorry that number of licenses about product listers, it will just becomes the same for that specific product because that's the request of the product manager.
0:17:49.40 --> 0:17:51.790
Duraid Wadie
That's the way they want it to work, and that makes sense.
0:17:52.540 --> 0:17:52.680
Jasmine Tang
OK.
0:17:52.220 --> 0:17:55.370
Duraid Wadie
But and and the under the whole right.
0:17:55.380 --> 0:18:2.620
Duraid Wadie
What happens is stays at the product and instance because we know when the platform we will have product instances have different licensing.
0:18:4.600 --> 0:18:4.870
Jasmine Tang
Yeah.
0:18:4.830 --> 0:18:5.520
Duraid Wadie
That makes sense.
0:18:5.530 --> 0:18:7.180
Duraid Wadie
So we can't put this at the tenant level.
0:18:7.190 --> 0:18:9.190
Duraid Wadie
We have to put it somewhere else at the product level.
0:18:10.620 --> 0:18:10.890
Jasmine Tang
Umm.
0:18:19.260 --> 0:18:21.230
Jasmine Tang
Good, right?
0:18:23.660 --> 0:18:24.800
Keith Low
So OK everybody.
0:18:29.280 --> 0:18:30.370
Jasmine Tang
I don't know what that good anymore.
0:18:30.380 --> 0:18:30.830
Jasmine Tang
Questions.
0:18:30.940 --> 0:18:31.810
Jasmine Tang
Yeah. Good.
0:18:31.820 --> 0:18:32.220
Jasmine Tang
Yeah. Yeah.
0:18:32.260 --> 0:18:32.850
Keith Low
Yeah, talk soon.
0:18:34.760 --> 0:18:35.290
Lim Zhao Siang
I'm good, I'm good.
0:18:35.910 --> 0:18:36.160
Keith Low
Yeah.
0:18:36.170 --> 0:18:38.100
Keith Low
OK, I think this clears up quite a lot.
0:18:38.450 --> 0:18:39.310
Keith Low
OK, I think that's all.
0:18:39.840 --> 0:18:40.180
Keith Low
Uh.
0:18:40.860 --> 0:18:41.530
Keith Low
Hey, thanks.
0:18:41.540 --> 0:18:42.140
Keith Low
Thanks for the time.
0:18:42.900 --> 0:18:43.530
Duraid Wadie
No problem at all.
0:18:43.540 --> 0:18:44.640
Duraid Wadie
No problem anytime, guys.
0:18:45.540 --> 0:18:45.790
Keith Low
Yeah.
0:18:45.800 --> 0:18:46.140
Keith Low
OK.
0:18:45.530 --> 0:18:46.360
Jasmine Tang
Alright. Thank you everyone.
0:18:46.150 --> 0:18:46.570
Keith Low
Thank you.
0:18:46.620 --> 0:18:46.980
Keith Low
Thanks.
0:18:47.150 --> 0:18:47.320
Keith Low
Bye bye.
0:18:47.150 --> 0:18:47.550
Jasmine Tang
Thank you.
0:18:47.100 --> 0:18:47.710
Duraid Wadie
Thank you.
0:18:47.720 --> 0:18:48.150
Duraid Wadie
Thank you.
0:18:47.600 --> 0:18:48.250
Jasmine Tang
Thank you.
0:18:48.160 --> 0:18:48.610
Duraid Wadie
Thank you.
0:18:48.620 --> 0:18:49.600
Duraid Wadie
Bye bye bye bye.
0:18:48.370 --> 0:18:49.610
Jasmine Tang
Bye bye.
0:18:49.430 --> 0:18:49.770
Lim Zhao Siang
Thank you.


Extract all the points of the meeting as above transcript. Re-read the trasnscript again before you output your answer to make sure nothing is missed.