Hi,
Currently, the Low-Code System module does not support database-per-tenant deployments. Low-Code modelling itself is global rather than tenant-scoped. With a single database, tenant data isolation is provided by the underlying ABP multi-tenancy infrastructure, but this does not make the Low-Code model tenant-specific.
We do not currently have near-term plans to add tenant-scoped or layered modelling for separate tenant databases.
Regarding dynamic permissions, the current code generates permission definitions from the global Low-Code model. Admin-role permission grants are seeded using the current tenant context; however, the complete database-per-tenant topology is unsupported, so we cannot guarantee consistent model, schema, and permission behavior in this setup.
The layer and table-creator classes you mentioned are internal implementation details, not supported extension points. They may change between versions, so replacing or deriving from them would be fragile and would need to be maintained by your application.
There is also currently no supported permission- or feature-based mechanism for making individual Low-Code entities visible only to selected tenants. Since tenant-side Designer changes can modify the global model while schema operations affect the current tenant database, revoking AbpLowCodeDesigner.* permissions from tenant roles is the appropriate safety measure.
Therefore, the observed behavior should be treated as a consequence of an unsupported deployment topology rather than a supported tenant-scoped modelling workflow.
Hello,
Regarding Low-Code: the feature is currently still in preview. We are planning to release it with 10.5.0-rc.1 for internal testing only, so it won’t be publicly available to all users yet.
However, if you’re interested, we can also enable it for you so you can try it out and provide feedback.
Please note that since it’s still in preview, some packages may not compile correctly. After creating a project, you may also need to switch to the preview packages through Studio.
Also, the documentation you referenced may be outdated and might not fully reflect the latest implementation and current state of the feature.
You can create and override the file under the HttpApiHost project at /Pages/Account/Register.cshtml. There is documentation here: https://abp.io/docs/latest/framework/ui/mvc-razor-pages/customization-user-interface
Hello, could you share the version information and UI information of your project?
Hi, could you please check again?
Hello, a while ago there was an issue with our server, it has been fixed now. Could you please check again?
It should be fixed now, can you try again?
Hello, there is a problem with our server right now. We will fix it soon. I am refunding your ticket.
Hi, what type of rules are you trying to use the rule engine for? If they are complex rules, I recommend using https://github.com/microsoft/RulesEngine. If they are simpler rules, could you provide an example?
I'm closing this question as you haven't reported any other issues.
