Implementing the User Groupware in your application

1. On the "Project" tab, in the "Project" group, click "User Groupware".
2. In the description window of the current project configuration, in the "User Groupware: Inactive" area, click on the "Modify" button..
3. In the window that appears, enable the User Groupware. You can configure the User Groupware for your application or site in the different tabs of this window. This configuration is presented in the following paragraphs.
4. Validate. The User Groupware is integrated into your project.
5. An administrator account will be created during the first execution of application or site under the "supervisor" name. Then, the corresponding password can be specified.

• Type of groupware,
• Start mode
• User account.

Type of groupware

• Classic User Groupware: User Groupware will be integrated in its "Classic" version: User Groupware will be associated only with your application (or site), and rights will be defined from within the application (or site)..
  If this option is selected, two specific tabs are displayed:
  • the "Files" tab, which allows you to specify the type of database and authentication used.
  • the "OAuth" tab, which allows you to specify the connection services available to users.
• BaaS user Groupware: This option lets you integrate BaaS (Backend as a Service) user Groupware with rights management via a server..
  If this option is selected, two specific tabs are displayed:
  • the "BaaS" tab, which allows you specify the characteristics of the BaaS server, the user accounts and the URLs of the administration sites.
  • the "Email" tab, which allows you to customize the messages to be sent to users (registration validation or password reset emails).

• You are using a PCSCloud platform: the necessary elements are installed by default on your platform.
  Reminder: PCSCloud is a pay-as-you-go, turnkey solution. For more details, see PCSCloud.
• You're not using a PCSCloud platform: install the following:
  • an HFSQL server,
  • the reserved server, including the modules for the Mobile User Groupware (WDBaaS).
  For more details, see Configuring a BaaS server (User Groupware and Private Store).

Start mode

• The "Automatic start" option indicates that the User Groupware is started at the same time as the application or site.
  The login window or page of the User Groupware is displayed before any other window/page of the application. The project initialization code is run when the login window/page is opened and validated.
• The "Manual start (programmatically)" option allows you to define when the User Groupware should be started.
  The login window or page will only be opened if gpwOpen (or gpwLogin) is used. This option is used to run the project initialization code before opening the login window/page. This option is useful, for example, in the case of a multilingual application: a window or page can be displayed to ask for the application's runtime language.
• The "Manual start via a control template" option is used to integrate the User Groupware login page in the site. This allows you to work with the automatic User Groupware (and to benefit from its updates) while being able to customize the login page.
  If this option is selected, the WDGPU_WB_CNX internal component is added to your project. This component includes the "TPLC_GPU_Connection" control template that manages the connection. To add this control template, simply drag and drop it onto the desired pages (or templates).
  Once it has been added, you can customize it:
  • by overloading the controls and/or the processes for small changes,
  • by directly modifying the control template for more important changes.

Groupware customization

• No customization:
  WINDEV and WEBDEV take care of everything. All you have to do is start the application or the site to configure the user access.
  
  Note: This option is compatible with integrated user groupware (option "Manual launch via a field template").
• Customize login UI:
  The login/register window or page is automatically integrated into your application.
  • The WDGPU_WB internal component is added to the project. This component contains all the pages, page templates, control templates and procedures necessary for user authentication. This allows you to fully customize all the login pages used by the User Groupware.
• Full customization (expert mode) - Standard User Groupware only:
  The programming of the User Groupware is automatically included in your application.
  • The WDGPU_WB internal component is added to the project. This component contains an analysis as well as all the pages, queries, classes and procedures required to manage the User Groupware. This allows you to customize all the pages used by the User Groupware.

Security

• Allow windows and reports to open by default: This option allows all users to open windows and reports by default.. In this case, simply specify which elements will not be accessible when configuring the rights.

Automatic login in test mode

File language

Password of data files

• The new password is taken into account only if it is changed before the User Groupware data files are created.
• This password is used when the files are re-indexed or when the files are opened by WDMAP.

Type of database ("Automatic start" mode only)

• in HFSQL Classic format (by default). The data file directory must be specified.
• in HFSQL Client/Server format. The characteristics of the connection to the HFSQL server must be specified as well as the directory of the different categories of files.

Type of authentication

• Authentication entirely managed by the User Groupware.
• Authentication from an LDAP directory or Active Directory.
  This option avoids duplicating usernames and passwords by using the users from the LDAP directory. In this case, the connection characteristics must be specified (see below).

• Server address
• Port number of server.
• Version of contacted LDAP server.
• Database

• The User Groupware works with Active Directory. It does not work with openLDAP.
• When the server port corresponds to port 636, the connection is automatically made in "Negociate" mode.

Options

• Login window only (no rights management): This option is only available for LDAP and Windows logins..
  In this case, no groupware file will be created. If the application is started in automatic mode, the user will need to log in. If the user is saved in the LDAP directory or in Windows, the application will start ; otherwise, it will be closed. A supervisor cannot configure the rights on the windows or pages. If this option is unchecked, identification is carried out with rights management: only users present in the LDAP directory will be able to connect.. The rights can be configured on the windows or pages.

• In "GPU application server (web service and administration site)", specify the server to use. In the case of a new server, select the type of server:
  • PCSCloud platform. In this case, specify the characteristics of your PCSCloud platform.
    Reminder: This option lets you take advantage of an already installed and configured Web server, reserved server and HFSQL Client/Server engine..
  • Network or Internet server with the protocol used. Enter the server name, user and password. This information was provided to you during the setup of the server reserved for the User Groupware/Private Store.
  • Specify the type of user accounts managed:
    • Shared accounts between applications: This option lets you deploy the application with other applications that will be accessible to the same users. This option is recommended for deployments in different companies.
    • Unique accounts for the application: This option stores the application with its user base.
      This option is recommended for deploying applications on a store.
  • The URLs of the administration sites are automatically filled in with the information specified above..
    WARNING: The URLs specified will only work when the user Groupware settings window is validated.. Upon validation, the modules installed with the reserved application server are automatically configured.

• Registration validation: if necessary, personalize the texts sent to users who have just registered..
• Forgotten password: Customize the texts sent to users who forget their password.