Yes I am aware of that. I am trying to avoid developing GUI for the public web site because I am working on a prototype and do not need a full-blown GUI for users. I am trying to leverage the back office GUI to allow users to modify the data.
I am using the application template with a public web site, and my goal is to allow users to directly modify model data that reside in dedicated database for each model. Please advise how I can achieve the following:
In my use case, I have a fairly large number of domain entities (40 -50) and they are designed for a model. Each model will need to have a dedicated database to hold its data, though all models share the same entities. On top of the model-specific entities, I have an entity called Model that need to be multitenant. It represents models created for the different tenants. I am trying to present Models on the public web page, so that the users can view their models. The user may then choose to work on one model, and this will direct the user to the back-office web site, where I hope to leverage the ABP GUI to allow users to modify the model data from the database dedicated to the model. The user may also want to create a new model, and this will again direct the user to the back-office website, and at the same time build a dedicated database for the new model, and construct the tables for the model entities in the database. User can then use the back office GUI to edit the tables for the new model.