-
Task
-
Resolution: Done
-
High
-
None
-
None
-
None
Domain object in PORTAL doesn't have any constraints.
This may cause many security problems.
Another advantage is that we can replay to the user why his data is not valid, without load the database.
That's why we should move data validation to BE.
- relates to
-
PORTAL-626 FunctionalMenuItem DB constraints
- Closed
-
PORTAL-627 App class DB constraints
- Closed
-
PORTAL-629 RoleApp class DB constraints
- Closed
-
PORTAL-630 WidgetCatalog class DB constraints
- Closed
-
PORTAL-632 FavoritesFunctionalMenuItem class DB constraints
- Closed
-
PORTAL-633 WidgetFile class DB constraints
- Closed
-
PORTAL-634 MicroserviceData class DB constraints
- Closed
-
PORTAL-635 MicroserviceParameter class DB constraints
- Closed
-
PORTAL-636 PortalAdminUserRole class DB constraints
- Closed
-
PORTAL-637 CommonWidget class DB constraints
- Closed
-
PORTAL-638 EpRoleNotificationItem class DB constraints
- Closed
-
PORTAL-639 EpNotificationItem class DB constraints
- Closed
-
PORTAL-640 FavoritesFunctionalMenuItemJson class DB constraints
- Closed
-
PORTAL-641 PortalAdmin class DB constraints
- Closed
-
PORTAL-642 FunctionalMenuRole class DB constraints
- Closed
-
PORTAL-643 SharedContext class DB constraints
- Closed