|
|
|
|
|
- Overview
- How to?
- To implement the User Groupware in your application
- Configuring, using and customizing the User Groupware
- Notes
- Operating mode of the User Groupware
- Remark
User Groupware (compatible with version 17)
Warning
From version 18, the User Groupware evolves. This help page corresponds to the User Groupware kept for backward compatibility. To get the help regarding the new version of the User Groupware, see User Groupware.
A Windows application, an Internet or Intranet site require to define the role of different contributors. Several access levels can be defined according to the user. All users have different responsibilities and requirements. Their field of action must therefore be more or less limited. For example, when a sales management application is implemented, it includes the following features: - Viewing the price list
- Modifying the price list
- Entering orders
- Entering customers.
Access may vary according to the user. For example: - administrative assistants can see the price list and create orders
- salesmen can see the price list, place orders and create new customers.
- managers have access to all the options.
To manage these access levels in your WINDEV applications or WEBDEV websites, simply include the User Groupware. In just a few clicks, a standard application can be transformed into an application that manages several access levels. This feature can be easily implemented in a WINDEV application or in a WEBDEV website. When running the application or site, the manager will be able to create users (identified by their username and password) and give them access to certain features. Note User Groupware is available in WINDEV applications and dynamic WEBDEV sites running under Windows or Linux. The User Groupware is not available in static, semi-dynamic, PHP or AJAX sites. To implement the User Groupware in your application Just one option is all you need: under the "Project" pane, in the "Project" group, click on "User Groupware". For more details on the different options available, see The options of the User Groupware. Configuring, using and customizing the User Groupware For more details on the User Groupware, see: Operating mode of the User Groupware An application that uses the User Groupware has two levels: - user level
- supervisor level
The user level The user logs in to the application or site via a window or page and accesses the available features. The supervisor level The supervisor logs in to the application via a window or page and accesses an advanced menu to configure users and their rights, or to launch the application. The configuration window/page allows the supervisor to: - start the application.
- configure the groupware.
Configuring the groupware consists in creating users and groups, associating users with groups as well as managing the rights granted to each user (or group) on each window/page found in the application. Rights can be defined for menu options, groups of controls and controls. The supervisor can gray out these elements, make them inactive or invisible. These configurations take precedence over any configuration defined in the program. Note: All user information and rights are stored in HFSQL data files. User data files can be common to several applications. Data files concerning user rights on the various windows/pages of the application are application-specific, and cannot be shared.
Related Examples:
|
Training (WINDEV): WD User Groupware
[ + ] This example presents the operating mode of the User Groupware supplied with WINDEV. The following topics are presented in this example: 1/ What is the User Groupware 2/ How can the User Groupware be included in my application 3/ How do I configure the User Groupware Summary of the example supplied with WINDEV: This example presents some features proposed by the User Groupware of WINDEV. It is based on an example for managing the user accounts. Some users have the rights to view the accounts while other users have the rights to perform operations (transfer, loan…)
|
This page is also available for…
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|