Completed abp commercial blog post for 4.3 release.

pull/8272/head
Halil İbrahim Kalkan 5 years ago
parent 3cd2b58ff7
commit 61830f44e6

@ -35,7 +35,7 @@ We'd introduced an initial version of the [microservice starter template](https:
* Created **separate solution (`.sln`) file** for each microservice, gateway and application. In this way, you can focus on what you are working on. The main (roof) solution file only includes the executable projects in these solutions.
* All microservices are converted to the standard **layered module structure** which makes easier to align with ABP application development practices.
After this release, we will be preparing microservice development guides based on this startup solution.
After this release, **we will be preparing microservice development guides** based on this startup solution.
### Separate Tenant Schema
@ -53,7 +53,39 @@ If you prefer the [ABP Suite](https://docs.abp.io/en/commercial/latest/abp-suite
![abp-suite-separate-tenant-schema](abp-suite-separate-tenant-schema.png)
### Forms Module
### Creating Tenant Databases On The Fly
With this release, separate tenant database feature becomes more mature. When you create a new tenant with specifying a connection string, the **new database is automatically created** with all the tables and the initial seed data if available. So, tenants can immediately start to use the new database. With this change, tenant connection string textboxes comes in the tenant creation modal:
![new-tenant-modal](new-tenant-modal.png)
In addition, we've added an "**Apply database migrations**" action to the tenant management UI to manually trigger the database creation & migration in case of you have a problem with automatic migration:
![tenant-db-migrate](tenant-db-migrate.png)
Automatic migration only tries one time. If it fails, it writes the exception log and discards this request. For example, this can be happen if the connection string is wrong or the database server is not available. In this case, you can manually retry with this action.
> Note that this feature requires to **make changes in your solution**, if you are upgrading from an old version. Because, the tenant database creation and migration code is located in the application startup template. See the [version 4.3 migration guide](https://docs.abp.io/en/commercial/4.3/migration-guides/v4_3) for details.
### New Module: CMS Kit
CMS Kit module initial version has been released with this version. As stated in the ABP Framework 4.3 announcement post (TODO: link), it should be considered as pre-mature for now.
For ABP Commercial application startup template, we are providing an option to include the CMS Kit into the solution while creating new solutions:
![cms-kit-selection](cms-kit-selection.png)
It is available only if you select the *Public web site* option. Once you include CMS Kit, a *Cms* item is shown on the menu menu:
![cms-kit-menu](cms-kit-menu.png)
Each CMS Kit feature can be individually enabled/disabled, using the global feature system. Once you disable a feature, it becomes completely invisible, even the related tables are not included in your database.
CMS Kit features are separated into two categories: Open source (free) features and pro (commercial) features. For now, only newsletter and contact form features are commercial. By the time, we will add more free and commercial features.
> We will create a separate blog post for the CMS Kit module, so I keep it short here.
### New Module: Forms
*Forms* is a new module that is being introduced with this version. It looks like the Google Forms application; You dynamically create forms on the UI and send it to people to answer. Then you can get statistics/report and export answers to a CSV file.
@ -81,15 +113,27 @@ However, we got many feedbacks from Team License customers that they need to sou
With this version, we decided to allow Team License holders to download the source code of the **Account Module** and the **Lepton Theme**, so they can freely customize them based on their requirements.
You can **Replace these modules with their source code** using the ABP Suite:
![account-lepton-source](account-lepton-source.png)
Remember that; when you include the source code in your own solution, it is your responsibility if you want to upgrade them when we release new versions (while you don't have to upgrade them).
### Lepton Theme Public Website Layout
We'd added a public website application in the application starter template in previous versions. It was using the public website layout of the Lepton Theme. We realized that the layout of this application is customized or completely changed in most of the solutions. So, with this version, the layout is included inside the application in the downloaded solution. You can freely change it. Before, you had to download it separately and include into your solution manually.
### Enable/Disable Modules
With this release, all modules can be enabled/disabled per edition/tenant. You can allow/disallow modules when you click *Features* action for an edition or tenant:
![enable-disable-features](enable-disable-features.png)
### Other Features/Changes
* ABP Suite now supports to define *required* navigation properties on code generation.
* **Blazor server-side** (with tiered option) is added for the application and microservice starter templates.
* An **"Email"** tab has been added to the Settings page to configure the email settings.
## Feedback

Binary file not shown.

After

Width:  |  Height:  |  Size: 123 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 27 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 8.3 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 28 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 34 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 16 KiB

Loading…
Cancel
Save