PC SOFT

WINDEVWEBDEV AND WINDEV MOBILE
ONLINE HELP

Home | Sign in | English UK
  • Overview
  • How does the user groupware operate?
  • The user level
  • The supervisor level
  • Implementing the user groupware
  • Adding the user groupware into an application
  • Running the application test
  • Creating the WINDEV executable
  • Installing an application that is using the user groupware
  • Configuring the application that is using the user groupware
  • Managing users
  • Managing the rights
  • Displaying the statistics
  • Migrating data
  • Tips for developing an application that supports the user groupware
  • Using groups of controls
  • Visibility of controls
  • Defining rights
WINDEV
WindowsLinuxUniversal Windows 10 AppJavaReports and QueriesUser code (UMC)
WEBDEV
WindowsLinuxPHPWEBDEV - Browser code
WINDEV Mobile
AndroidAndroid Widget iPhone/iPadApple WatchUniversal Windows 10 AppWindows Mobile
Others
Stored procedures
5. User groupware in practice
Previous pageTable of contentsNext page
Overview
An application must define the role of different contributors. It is often necessary to define several access levels according to the user.
Indeed, all users do not have the same responsibilities or the same requirements. Their ability to use some of the application features can be customized.
Let's take a simple example: an application for sales management proposes the following features:
  • Price list view,
  • Price list modification,
  • Order entry,
  • Entering customers.
The accesses differ according to the user. Some examples:
  • the administrative assistants can see the price list and create orders.
  • the sales people can see the price list, place orders and create new customers.
  • the sales directors have access to all options.
To manage these access levels in your WINDEV applications, all you have to do is include the user groupware in your application. In just a few mouse clicks, a standard application can be changed into an application that manages several access levels. This feature can be easily implemented.
When starting the application, the manager will be able to create users (identified by their login and password) and to give them access to some application features.
How does the user groupware operate?
An application that is using the user groupware includes two levels:
  • the user level.
  • the supervisor level.

The user level

The user connects to the application via a login window and he can access the features that have been allowed for him.
Remark: The user groupware can allow you to connect by using an LDAP directory.

The supervisor level

The supervisor connects to the application via a login window and he can access an advanced menu allowing him to configure the users and their rights, or to start the application.
The configuration window allows the supervisor to:
  • start the application.
  • configure the groupware.
Configuring the groupware consists in creating the users and groups, associating the users with the groups and managing the rights granted to each user (or group) on each application window. The rights can be defined for the menu options, for the groups of controls and for the controls. The supervisor can gray these elements, or make them inactive or invisible. These configurations have priority over any configuration defined in the program.
Remark: The information regarding the users and their rights is stored in data files in HFSQL format (Classic or Client/Server).
Implementing the user groupware

Adding the user groupware into an application

To implement the user groupware in a WINDEV application, a single option is enough: on the "Project" pane, in the "Project" group, click "User groupware". The window for configuring the user groupware is used to define:
  • The mode for integrating the user groupware.
  • The mode for starting the user groupware.
  • The location of the data files of user groupware.
  • The mode for identifying the user.
  • The use of a specific connection service.
Integration mode of user groupware
Several modes can be used to integrate the user groupware:
  • Automatic user groupware: the entire programming of user groupware is automatically included in your application. No customization can be done. The skin template of project is automatically applied to all the windows used by the user groupware.
    This integration mode is used to automatically follow the possible evolutions of user groupware.
  • Custom user groupware: the entire programming of user groupware is automatically included in your application via an internal component. All windows required to manage the user groupware (login and user management) are automatically added to your project. This allows you to customize all the windows used by the user groupware.
The different windows found in the user groupware are presented in details in the online help.
Starting the user groupware
Two modes can be used to start the user groupware:
  • Auto run: The login window of user groupware is started before any other application window. The initialization code of project is run once the login window is opened and validated.
  • Manual start: The login window will be opened only if gpwOpen is called. This option is used to run the initialization code of project before opening the login window. You have the ability to display a window requesting the runtime language of application for example.
Automatic login in test mode
You can specify the login and password that will be used in "Automatic test" mode. This information will be used if an automatic test is run on the application.
Data files of user groupware
The user groupware is using several specific data files. These data files are mainly used to manage the application users, groups, rights and elements.
The user groupware can be used:
  • with HFSQL Classic data files. In this case, the "Files" tab is used to specify (if necessary) the location of data files.
  • with HFSQL Client/Server data files. In this case, the "Files" tab is used to define the parameters for accessing the HFSQL Client/Server database as well as the file directory.
The password of data files
By default, the data files found in the user groupware have a specific password. This password is: "PCSGPW2001".
To change this password, type the new password in the "Files" tab of the description window of user groupware. The characters typed are displayed as stars.
Remark: This password is used when re-indexing or opening data files with WDMAP for example.
See the online help for more details.
Identification
The user groupware proposes several modes for identifying users:
  • Identification managed by the user groupware of WINDEV.
  • Identification from an LDAP directory.
  • Windows identification.
Identification managed by the user groupware
The login and password are saved in the data files of user groupware.
Identification from an LDAP directory
If the company of your customer is using an LDAP directory, you have the ability to branch the user groupware onto this directory. To do so, specify the characteristics of LDAP directory (server, port, database, ...) in the "Identification" tab. Therefore, the account and the password found in the LDAP directory will be automatically asked to the user.
Two modes are available:
  • Without management of rights: In this case, no groupware file will be created. If the application is started in automatic mode, the login window will ask the user to identify himself. If the user is saved in the LDAP directory, the application will start ; otherwise, it will be closed. A supervisor cannot configure the rights on the windows.
  • With management of rights: Only the users found in the LDAP directory can connect. The rights can be configured on the windows.
See the online help for more details.
Remark: The user groupware operates with Active Directory. It does not operate with openLDAP.
Windows authentication
In this case, the login and password correspond to the ones defined for using Windows.
Remark: You also have the ability to use a unique authentication. In this case, the login and password will be requested once only for each session.
Specific connection service
The "Registration" tab allows you to authorize the use of a specific connection service. For the specified service, it is necessary to specify the corresponding identifiers (provided when registering the application with the selected service).

Running the application test

When running the test of an application that is managing the user groupware, the first window displayed is the login window (regardless of the first window defined in your application).
A single user exists by default: the supervisor. To connect as supervisor, all you have to do is type the following information in the login window:
  • Name: SUPERVISOR
  • Password: SUPERVISOR
You can now run the test of your application or configure the user groupware.
Remarks:
  • If you do not want the first window of your application to be the login window, select "Manual start" in the "Execution" tab of the user groupware options. Simply use gpwOpen to open the login window.
  • The windows for managing the user groupware are run before the initialization code of project.
  • The window defined as first window of your application in the project will be opened after the login window (if the user is not the supervisor).
  • To avoid starting the user groupware when running the application tests, select "No user groupware" in the "Integration" tab of user groupware options.
If the user groupware is re-enabled later, the data files previously used by the user groupware will not be erased.

Creating the WINDEV executable

When creating the executable that is managing the user groupware ("Generate" on the "Home" pane), a screen specific to the user groupware is displayed.
This allows you to define the location of the data files of user groupware.

Installing an application that is using the user groupware

An application that is using the user groupware is installed like any other application: on the "Project" pane, click "Setup procedure".
A screen specific to the user groupware is used to configure the location of data files specific to the user groupware.
Remarks:
  • If the data files of user groupware have been configured for your client, they must be selected when preparing the setup. Therefore, the list of setup files must be customized.
  • If the groupware files have not been configured, only the Supervisor user will be able to login during the first application start.
Tip: If you do not configure the different use levels of user groupware for your clients, we recommend that you provide them with a document listing all the controls found in your windows in order to get an optimized configuration.
Configuring the application that is using the user groupware
When the application is deployed, the user groupware is configured by the application supervisor.
This setting consists in creating the users and groups of users, and in granting them specific rights for each control found in each application window. These rights are used to gray controls, groups of controls or menu options, and to make them visible or invisible.
To configure the user groupware, you must:
  1. Start the application (executable or test from WINDEV) and connect as supervisor:
    • Name: supervisor
    • Password: supervisor
  2. Select "Configure the groupware".
  3. The window for managing the user groupware is displayed. This window is used to:
    • manage the users and groups
    • manage the rights
    • display the statistics
    • migrate the data coming from a user groupware version 17 and earlier.

Managing users

The user management consists in:
  • creating users,
  • creating groups,
  • associating users with groups.
To create a new user, you must specify:
  • the last user name.
  • the first user name.
  • the user login (mandatory). This login corresponds to the user's identifier when he connects to the application.
  • the user password. This password is optional and it can be entered by the user during his first connection (check the corresponding option).
The user can be defined as being an application supervisor.
You also have the ability to modify or delete a user. When deleting a user, you have the ability to delete the entire user or to delete his rights only.
The users can be grouped.
To associate a user with a group, all you have to do is Drag and Drop the user to the selected group.
A user can be associated with several groups.
Remarks:
  • The supervisor password should be changed during the first use.
  • If you are using an LDAP directory, you have the ability to import the users found in the directory in order to manage the rights of these users.

Managing the rights

The supervisor can manage the rights granted to each user (or group of users) on the elements found in the project windows.
For each association between a user and a window, a specific status can be defined for all the window elements.
The elements managed in the windows, internal windows and window templates are as follows:
  • the controls
  • the groups of controls
  • the menu options
The following states are available for each element:
  • Default: the element behavior corresponds to the default behavior, defined in the application.
  • Inactive: the element is displayed but no input can be performed.
  • Grayed: the element is grayed. No input can be performed.
  • Invisible: the element is not displayed.

Displaying the statistics

For each application, you have the ability to get use statistics according to the user, for a specific period.

Migrating data

From version 18, the user groupware has evolved. Different data files are used by the user groupware.
The administrator of user groupware can migrate the existing data to the new format and therefore automatically retrieve the data used in the earlier versions. This migration can be performed regardless of the data format: HFSQL Classic, HFSQL Client/Server, Native Connector.
Tips for developing an application that supports the user groupware

Using groups of controls

To simplify the configuration of groupware management according to users, the controls should be organized in groups of controls.
In your windows, you have the ability to create groups of controls corresponding to the controls that must be displayed for a type of user.
The ability to associate a control with several groups of controls increases the number of possible combinations.
These groups of controls can be created in your application for managing the groupware, no specific programming is required.

Visibility of controls

When developing your application, you can define the visibility characteristics for the elements found in your windows:
  • when describing the element (7-tab window)
  • by programming (..State or ..Visible properties)
When configuring the user groupware, the supervisor can define different visibility characteristics. The characteristics defined by the supervisor have priority.
For example, a button is used to make a control active. This control was grayed by the supervisor. Your code will be ignored and the control will not be active.

Defining rights

To get a definition of rights corresponding to the features of your application, we advise you to:
  • configure the rights for your application before creating the setup procedure. Then, all you have to do is add the groupware files when creating the application setup.
  • provide a programming documentation that gives the names of controls, groups of controls and options that must be configured according to the level of use defined for the application.
Previous pageTable of contentsNext page
Minimum version required
  • Version 9
Comments
Click [Add] to post a comment