Trace:
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
applications:menu_configuration_mu [2018/03/14 07:19] admin created |
applications:menu_configuration_mu [2020/07/08 13:13] (current) cduncan articles |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ~~NOTRANS~~ | ~~NOTRANS~~ | ||
| - | ~~Title: Menu configuration (Multiuser)~~ | + | ~~Title: Menu Configuration (Multiuser)~~ |
| - | ProjX reads the menu configuration from the database. It's not needed to build the menu manually. You configure/map your work-screens and create access roles like Administrator, Developer, User. You have to assign your screens to roles, e.g. a Developer has access to all screens, an Administrator has access to all application screens but not to development screens, and so on. | + | ProjX reads the menu configuration from the database. It's not needed to build the menu manually. You configure/map your workscreens and create access roles like administrator, developer, user. You have to assign your screens to roles, e.g., a developer has access to all screens, an administrator has access to all application screens but not to development screens, and so on. |
| - | The ProjX application supports multiuser applications out-of-the-box without writing one line source code. | + | The ProjX application supports multiuser applications out of the box without writing one line source code. |
| - | Be sure that your database has following tables: USERS, ROLES, WOKSCREENS, USER_ROLE, ROLE_WOSC and following Views: V_ACCESSRULES, V_USERROLES, V_USERSCREENS. | + | Be sure that your database has the following tables: USERS, ROLES, WOKSCREENS, USER_ROLE, ROLE_WOSC and following views: V_ACCESSRULES, V_USERROLES, V_USERSCREENS. |
| - | Add the object com.sibvisions.apps.server.object.DBWorkScreenAccess to your Session life-cycle object: | + | Add the object com.sibvisions.apps.server.object.DBWorkScreenAccess to your session life cycle object: |
| <file java> | <file java> | ||
| Line 33: | Line 33: | ||
| </file> | </file> | ||
| - | The access controller reads V_ACCESSRULES and checks the access to life-cycle objects. | + | The access controller reads V_ACCESSRULES and checks the access to life cycle objects. |
| After successful configuration, map your screens. The workscreens table should be self explained: | After successful configuration, map your screens. The workscreens table should be self explained: | ||