We announced our new module 🔊 LOW-CODE. This module adds a low-code app development designer to your ABP project. And without writing a single line of code, you can create apps. No need to compile or deploy.
🌎 Low-code home page abp.io/low-code 📑 Technical documentation abp.io/docs/latest/low-code 📢 Announcement blog post: abp.io/community/announcements/introducing-abp-lowcode-build-real-abp-apps-in-minutes-647ymozi ▶ Step-by-step building an example app abp.io/community/articles/building-a-vendor-onboarding-workflow-with-abp-lowcode-1wx0ckzc 🎥 Community talk: youtube.com/watch?v=3SZd8Bxskf4
Please share any issues you find with this project. We'll fix the bugs as we detect them.
4 Answer(s)
-
0
Providing file attachment infrastructure, runtime business rule customization, and dynamic entity field extension at runtime are critical capabilities for enterprise-grade applications built on top of the ABP framework.
When enterprise implementations move beyond standard CRUD operations, development teams typically face a architectural fork in the road: either build a custom meta-data-driven abstraction layer on top of ABP's Domain/Entity framework, or rely heavily on JSON columns (like PostgreSQL's jsonb) combined with dynamic DTO mapping.
The three specific areas mentioned address major pain points in enterprise software delivery:
Dynamic Entity Extension (EAV or Schema-less patterns): Allowing users or implementation teams to add fields at runtime breaks away from rigid database schemas. In ABP, this usually requires a hybrid approach where standard entities handle core properties, while extended properties are stored in a flexible sidecar table or a structured JSON document property, integrated via custom Object-to-Object mapping extensions.
Runtime Business Rules: Moving logic out of compiled C# code and into a runtime execution engine (such as evaluating rules via scripting engines like Roslyn, Jint for JavaScript, or rule definitions stored in the database) allows business analysts to modify workflows without triggering a full deployment cycle.
Generic File Attachments: Tying a polymorphic file management service to any dynamic entity ensures that custom fields and runtime entities aren't second-class citizens when it comes to document management, integrating seamlessly with ABP's Blob Storing system.
Bringing these concepts natively into ABP Framwork would significantly reduce the boilerplate required when tailoring products to unique customer requirements.
Any plans to suport this a low-code features on ABP Framework core?
Markdown supported.Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post) -
0
[helder.costa] said: Providing file attachment infrastructure, runtime business rule customization, and dynamic entity field extension at runtime are critical capabilities for enterprise-grade applications built on top of the ABP framework.
When enterprise implementations move beyond standard CRUD operations, development teams typically face a architectural fork in the road: either build a custom meta-data-driven abstraction layer on top of ABP's Domain/Entity framework, or rely heavily on JSON columns (like PostgreSQL's jsonb) combined with dynamic DTO mapping.
The three specific areas mentioned address major pain points in enterprise software delivery:
Dynamic Entity Extension (EAV or Schema-less patterns): Allowing users or implementation teams to add fields at runtime breaks away from rigid database schemas. In ABP, this usually requires a hybrid approach where standard entities handle core properties, while extended properties are stored in a flexible sidecar table or a structured JSON document property, integrated via custom Object-to-Object mapping extensions.
Runtime Business Rules: Moving logic out of compiled C# code and into a runtime execution engine (such as evaluating rules via scripting engines like Roslyn, Jint for JavaScript, or rule definitions stored in the database) allows business analysts to modify workflows without triggering a full deployment cycle.
Generic File Attachments: Tying a polymorphic file management service to any dynamic entity ensures that custom fields and runtime entities aren't second-class citizens when it comes to document management, integrating seamlessly with ABP's Blob Storing system.
Bringing these concepts natively into ABP Framwork would significantly reduce the boilerplate required when tailoring products to unique customer requirements.
Any plans to suport this a low-code features on ABP Framework core?
Yes! the ABP Low-Code module already supports all three:
- Dynamic Entity Extension (EAV / schema-less) ✅ This is the module's core feature, and it uses exactly the hybrid pattern you described — not raw EAV, but a hybrid mapped-column + JSON storage model.
- Runtime Business Rules ✅ The module ships a full runtime scripting/rule engine using Jint (JavaScript, not Roslyn/C#):
- Generic File Attachments ✅ Polymorphic, dynamic-entity-aware file/attachment management is built on ABP's IBlobContainer/IBlobContainerFactory:
Markdown supported.Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post) -
0
Yes! the ABP Low-Code module already supports all three:
- Dynamic Entity Extension (EAV / schema-less) ✅
This is the module's core feature, and it uses exactly the hybrid pattern you described — not raw EAV, but a hybrid mapped-column + JSON storage model.
- Runtime Business Rules ✅
The module ships a full runtime scripting/rule engine using Jint (JavaScript, not Roslyn/C#):
- Generic File Attachments ✅
Polymorphic, dynamic-entity-aware file/attachment management is built on ABP's IBlobContainer/IBlobContainerFactory:
I know, but my question is about the ABP Core framework. Are there any plans to provide better infrastructure in ABP Core (not the low-code module) to support the same features?
Markdown supported.Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post) -
0
[helder.costa] said:
Yes! the ABP Low-Code module already supports all three:
- Dynamic Entity Extension (EAV / schema-less) ✅
This is the module's core feature, and it uses exactly the hybrid pattern you described — not raw EAV, but a hybrid mapped-column + JSON storage model.
- Runtime Business Rules ✅
The module ships a full runtime scripting/rule engine using Jint (JavaScript, not Roslyn/C#):
- Generic File Attachments ✅
Polymorphic, dynamic-entity-aware file/attachment management is built on ABP's IBlobContainer/IBlobContainerFactory:
I know, but my question is about the ABP Core framework. Are there any plans to provide better infrastructure in ABP Core (not the low-code module) to support the same features?
these are implemented in ABP Framework. Did you have chance to look at the framework's code
Markdown supported.Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)
