Activities of "hikalkan"

Hi,

Forms and CMS Kit modules are released with the version 4.3. So, they are pretty new. We don't have a plan to implement Angular/Blazor UI in the version 4.4 (which will be released in the end of Q2, 2021). In the v4.4, we will enhance these modules to fill some gaps. In every milestone, our team is deciding on the new features and modules. We will consider to implement Angular/Blazor UI for these modules in the next versions based on customer feedbacks.

We see these modules as business specific modules, but not fundamental modules (like user management). If that's critical and urgent for your business, I suggest to implement the Angular UI for your own application instead of waiting.

Best regards.

This question is similar to https://support.abp.io/QA/Questions/1178/v44---Subscriptions-and-Payments

A basic subscription system is being developed. "Limiting number of users per tenant" was not in plan, but we've planned for 4.4 after your message.

Concurrent user control is not something we are planning, however you can implement for your own application. You know, you can define numeric features. The you can somehow check concurrent user count (maybe in an asp.net core middleware, but that's not related to the ABP framework). For other features, you can implement yourself. They are in our backlog, but can't promise a delivery time, it will take time.

Hi,

We are adding subscription integration for the payment module, then we will use it from the SaaS module to implement subscriptions. The subscription system leaves recurring payment to the payment gateway provider (e.g. Stripe).

Tenant & User impersonation are also planned for the next version. These features will be ABP Commercial features, not included in the open source side. We will probably close those issues.

Hi,

You have already investigated the code base and understood most of the details :)

1. As you've written, individual components (those touches to database) are already cached, so object building doesn't get much time I think. This is a big object and if we use distributed cache, it will be serialized to redis and probably it will take more time to get from cache. However, we will work on in the next versions. Probably we can do some imporvements here.
2. This is a good idea to optimize the caching when we implement it.
3. It resets the cache if the user changes his/her own data (e.g. permissions). If you change data of any other user, it is not reset. That means if you change permission of a user, it might take a few minues to take the effect, in a tiered architecture.

We've done some performance improvements with the version 4.3. This topic is in our TODO list for the version 4.4.

Have a nice day.

no need to wait. you can just upgrade to latest devart package in your own application.

Hi,

Unfortunately, removing a property is not possible and we've never thought such a requirement before. AddOrUpdateProperty is for extra properties, not for the properties of a class. As you know, normally, no way to remove a class property on runtime. As I know, also there is no way to remove an attribute on runtime.

I suggest you to create a new method in your custom service and use it in the client side.

As an alternative, you can add [DisableValidation] attribute to the CreateAsync method to disable validation. In this case, you can implement the validation yourself inside the method.

This problem occurs since you are registering a second data seed contributor but not removing or replacing the original one.

Actually, you don't have to replace it just set admin email/password. Open MyProjectNameDbMigrationService in your solution, find the SeedDataAsync method, find this line:

await _dataSeeder.SeedAsync(tenant?.Id);

Change it like:

await _dataSeeder.SeedAsync(
	new DataSeedContext(tenant?.Id)
		.WithProperty("AdminEmail", "...........")
		.WithProperty("AdminPassword", "..............")
	);

I believe we should add this to the startup template, so it will be easy to understand it.

BTW, if you want to override a service, you should replace it as documented: https://docs.abp.io/en/abp/latest/Dependency-Injection#replace-a-service

Thanks for reporting. This issue will be resolved in next release (4.3).

Hi,

Feature system can be used to completely enable/disable a module or enable/disable some features of a module. However, the module should implement the logic for disable/enable itself, because it depends what module does.

For pre-built modules, we have designed the chat and file management module that supports fully disable it per tenant. For example, see the feature management modal for the file management module:

You can disable per edition or tenant. Even if you enable, you can control the storage limit for tenant/edition.

Identity and account module also has some features those can be enabled/disabled per tenant/edition.

However, other pre-built ABP Commercial modules are typically fundamental and business independent modules. So, we didn't design them to be enabled/disabled per tenant.

For your own modules, you can design them so that they are enabled/disabled per tenant. ABP framework provides the feature infrastructure for it.

Thanks a lot @michael.sudnik for your great explanations. This would be a good feature for the framework. I created an issue: https://github.com/abpframework/abp/issues/7423 We will work on this in the next weeks.

I am closing this ticket. You can re-open and add comment if you want.