This refers to having a single DB per Tenant and would therefore signify that as Tenants are created / added, each would be assigned a separate DB.
This aspect is helpful for User Management purposes and will come into play while creating Users for logging into the Website.
This feature is required for Role Management, Menu Management, and Rights Management.
It works on the RBAC [Role Based Access Control]
technique.
This feature allows for the management of all the Lists in a system. The data / values for each List which are 2D in nature, can be fed and maintained here, making it the sole source of all Lists in the system. From a DEV perspective, the usage of a database to store Constants.
This refers to the management of Events and Event Attributes that need to be recorded for the system. An Event would typically correspond to an activity such as Login, and an Event Attribute would be the record of the User who is logging in OR the browser being used for logging in, etc...
This allows the user to keep track of the errors / issues encountered while accessing any S1 page. A record of the machine used, the date and time of the error, the level of the occurring issue, and the application ID is also tracked for better understanding while rectifying the same.
Hassle free management of DB Scripts irrespective of the size of your development team.This feature enables the user to generate scripts for any module within SystemOne - Admin. Any module can be selected, for which scripts in C#, SQL and TypeScript can be generated.
This corresponds to the setting-up and management of each Tenant by associating the respective DBs with it. A tenant is the most fundamental construct of a SaaS environment. As a SaaS provider building an application, you are making this application available to your customers.