PC SOFT

ONLINE HELP
FOR WINDEV, WEBDEV AND WINDEV MOBILE

Home | Sign in | English US
  • Overview
  • The options of user groupware
  • Implementing the user groupware in your application
  • User groupware in the Linux sites
  • Options of "General" tab
  • Integration mode of groupware
  • Starting the user groupware
  • Automatic login in test mode
  • Using a LDAP directory to authenticate the users
  • "Files" tab
  • Password of data files
  • Enabling the history of connections
  • Type of database
  • "LDAP" tab
  • Characteristics of LDAP server
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
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 user groupware, see User Groupware.
Overview
An application is often intended to be used by several users connected via a network. Similarly, a site is always intended to be used by several Web users. In most cases, different access levels must be defined according to the user or to the Web user.
To manage these access levels in your WINDEV applications or in you WEBDEV sites, all you have to do is include the user groupware in your application or in your site. 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.
See Overview of user groupware for more details.
The options of user groupware

Implementing the user groupware in your application

To implement the user groupware in your application:
  1. Select "Workshop .. Configure the user groupware".
  2. Check "Enable the management of user groupware".
  3. Validate.
WEBDEV - Server codeLinux

User groupware in the Linux sites

To use the user groupware, the specific pages of user groupware must be included in the site ("Custom integration").
Options of "General" tab

Integration mode of groupware

Two modes are available for including the user groupware in your application:
  • Default integration:
    The programming of the user groupware is automatically included in your application.
    A new window or page is included in your project: The login window/page. It is displayed when the application is started and it allows the user to connect to the application. You can customize this window/page by applying the skin template of your application for example.
  • Custom integration:
    The programming of the user groupware is automatically included in your application.
    All the windows or pages required to manage the user groupware (login and management of users) are automatically included in your project. You can customize all the windows or pages used by the user groupware.
The different windows or pages used by the user groupware are presented in The windows and pages of the user groupware.

Starting the user groupware

Two modes can be used to start the user groupware:
  • Automatic run: The login window or page of the user groupware is displayed before any other window/page of the application. The initialization code of project is run when the login window/page is opened and validated.
  • Manual run: The login window or page will be opened only if gpwOpen is used. This option is used to run the initialization code of project before opening the login window/page. This option is useful for a multilingual application for example: A window or a page can be displayed to request the runtime language of application.

Automatic login in test mode

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.

Using a LDAP directory to authenticate the users

If the company of your customer is using an LDAP directory, you have the ability to branch the user groupware onto this directory. 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 or pages.
  • With management of rights: Only the users found in the LDAP directory can connect. The rights can be configured on the windows or pages.
See User groupware and LDAP directory for more details.
Note: The user groupware operates with Active Directory. It does not operate with openLDAP.
"Files" tab

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, enter the new password. The characters typed are hidden.
Note: This password is used when the files are re-indexed or when the files are opened by WDMAP.
See The files of user groupware for more details.

Enabling the history of connections

If the history of connections is enabled:
  • An additional data file is created: GPW_CONNECTIONLOG. This file contains the history of connections.
  • When configuring the application, the supervisor can access the history of connections via the "History of connections" button.
    This history is displayed in a specific window/page. This page is used to identify all the users who have been connected to a given application during a specific period. A chart indicates the number of connections per hour during the day. A button is available to clear the history if necessary.

Type of database

The user groupware handles several categories of files:
  • the data files used to identify the users. These users can use several applications. Therefore, these files can be shared among several applications.
  • the data files used to manage the user rights on the windows/pages of the application.
These files can be:
  • in HyperFileSQL Classic format (by default). You can specify the directory in which each category of user files (specific to the user groupware) will be created and used for the test of your application.
  • in HyperFileSQL Client/Server format. The characteristics of the connection to the HyperFileSQL server must be specified as well as the directory of the different categories of files.
See The data files of user groupware for more details.
"LDAP" tab

Characteristics of LDAP server

If the user groupware was configured to use an LDAP directory, the LDAP tab is used to configure the characteristics of LDAP server used for test (and at run time).
The requested information is:
  • Address of server
  • Port number of server.
  • Version of contacted LDAP server.
By programming, all you have to do is use gpwOpenLDAPSession.
See User groupware and LDAP for more details.
Minimum required version
  • Version 11
This page is also available for…
Comments
Click [Add] to post a comment