You can post your feature request💡under this topic. If other members like the feature, they can upvote☝️ the post. Please add details as much as you can.
19 Answer(s)
-
1
Bulk SMS and Bulk SMS sending and inbox to users and customers (a new entity) since most abp projects will have a customer entity
-
0
Integration with 3rd party applications module/ framework (background services).
-
2
Export to excel button on abp suite generated pages
-
0
- many-to-many with supporting custom properties in intermediate tables and wilth fully support on abp.suite
- many-to-many UI with generated grids with related entity with options "New", "Update", "Link", "Unlink", "Delete" - example how it could be implemented: https://docs.devexpress.com/eXpressAppFramework/112719/getting-started/in-depth-tutorial-winforms-webforms/business-model-design/business-model-design-with-xpo/set-a-many-to-many-relationship-xpo
-
0
Add example for document attachments of pages i.e sales orders details page you might want to add attachments and store them in a seperate page than file management page.
-
2
Make use of css variables in themes so that it is changeable with reasonable effort. Taking the lepton theme as an example: I need to set my own colors so that they match my corporate identity.
Starting from lepton6.css (copied from source into my project) I have one screen with the app running, another with debug console and another with the css file. I need to check the hex codes used to then manipulate the style sheet, which is WAY more effort than just replacing a bunch of variables. And now that I replaced everything with variables I am less exited about updates in this area, because I now have to constantly monitor changes >.<
-
1
ABP Suite - Preserve Custom Code Across Repeated CRUD Generations
my common work-flow: generate crud->customise->re-generate crud->re-enter-previous customization-> repeat...etc
- for the *.cs generated classes is would be very useful to be able to wrap custom code in a region - such that the CRUD engine can detect this region in the *.cs file allowing it to be preserved across CRUD generations.
`#region CustomCode
// ...custom code here
#endregion`
This would be a massive boost in efficiency and a valued Feature in my opinion.
-
2
ABP Suite - Preserve Custom Code Across Repeated CRUD Generations
my common work-flow: generate crud->customise->re-generate crud->re-enter-previous customization-> repeat...etc
- for the *.cs generated classes is would be very useful to be able to wrap custom code in a region - such that the CRUD engine can detect this region in the *.cs file allowing it to be preserved across CRUD generations.
`#region CustomCode
// ...custom code here
#endregion`
This would be a massive boost in efficiency and a valued Feature in my opinion.
this is one of the important features that we would like to implement. there are several approaches to preserving the custom code. we will find the best way to achieve this.
-
1
CRUD Generation - allow the option to select one or more Properties to become part of a Unique Constraint.
This is a very common requirement across the projects I've worked on and although it can be enforced in other layers - I think having these constraints at the DB layer is best practice for a strong system.
Example: EF SQL Server multi-tenant app - generated code might look something like:
