ONLINE HELP
 WINDEVWEBDEV AND WINDEV MOBILE

This content has been translated automatically.  Click here  to view the French version.
Help / Developing an application or website / Mobile User Groupware
  • Overview
  • Implementing the User Groupware in a mobile application
  • Step 1: Server configuration
  • Step 2: Activate User Groupware in a mobile project configuration
  • Step 3: Set up users and rights
  • Step 4: Test the application
  • Configuration required to log in to the groupware with Google
  • Google platform configuration
  • Android application configuration in WINDEV Mobile
  • Android application configuration in the administration site
WINDEV
WindowsLinuxJavaReports and QueriesUser code (UMC)
WEBDEV
WindowsLinuxPHPWEBDEV - Browser code
WINDEV Mobile
AndroidAndroid Widget iPhone/iPadIOS WidgetApple WatchMac Catalyst
Others
Stored procedures
Overview
WINDEV Mobile includes a User Groupware for Android and iOS applications.
The principle of use is very simple:
  • When the application is started, a specific window allows users to log in (or create a new account).
  • When the login window is validated, the application checks the login credential by querying a web service.
  • If the login credentials are correct, users can use the application with the rights they have been granted. A local rights database is copied to the mobile device, allowing a subsequent connection, even in offline mode.
Note This help page explains how to set up "User Groupware". To implement a Private Store system, see Private Store for mobile applications.
Implementing the User Groupware in a mobile application

Step 1: Server configuration

There are two possible cases:
  • If you are using a PCSCloud platform, the required elements are installed by default on your platform.
    Reminder: PCSCloud is a paid, turnkey solution. For more details, see PCSCloud.
  • If you are not using a PCSCloud platform, you will need to install the following elements:
    • 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).

Step 2: Activate User Groupware in a mobile project configuration

To enable the User Groupware in a configuration of your WINDEV Mobile project:
  1. Open your project in WINDEV Mobile.
  2. If necessary, select the project configuration in which the User Groupware should be enabled.
  3. On the "Project" tab, in the "Project" group, click "GPU / Private Store".
  4. In the description window of the current project configuration, in the "User Groupware: Disabled" area, click "Change".
  5. In the window that appears, in the "General" tab:
    • Activate MBaaS services: click on "Active"..
    • Select the desired feature: "GPU: User access rights management"..
    • In "GPU and Private Store application server (webservice and administration site)", indicate the server to be used. 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.
    • Specify the type of deployment:
      • Shared accounts between applications This deployment mode uses a common database for User Groupware IDs and rights. This deployment mode is recommended for inter-enterprise deployment.
      • Single application accounts This deployment mode uses a single database for logins and rights per application using User Groupware. This deployment mode is recommended for deployment on the 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.
    • In the "Administration" section, you can reset the administrator account password on a production server ("Reset administrator account password" button). Simply connect to the server.
  6. On the "GPU" tab, specify:
    • The User Groupware customization mode:
      • "Default login window (recommended)". WINDEV Mobile takes care of everything. Simply start the application to use the User Groupware.
      • "Customize the login window": All user groupware elements are integrated into your project via an internal component. You can customize the different elements of the User Groupware. However, the evolutions of the product will not be integrated.
    • User Groupware launch type:
      • Automatic launch The User Groupware login window is launched before any other application window. The project initialization code is executed once the login window is opened and validated.
      • Manual launch: The login window will only be opened if the gpwOpen function is used.. This option can be used to execute the project initialization code before opening the login window. For example, in a multilingual application, this option can be used to display a language selection window.
    • How users log in to the application:
      There are two cases:
      • Display login window only at first start. The login window will only be displayed at the first start. The information entered for the first connection will be automatically reused for future connections.
      • Authentication at each start. The login window appears at each start. Biometric authentication can be enabled in this case.
    • The security options:
      • Allow new users to create an account This option allows new users to create an account (not authorized by default).
      • Seamless authentication with the account on the iOS device (Sign in with Apple): This option requires the use of an "App Store" compatible certificate, and is not available if the "Private Store" feature has been selected..
      • Seamless authentication with the account on the Android device (Sign in with Google): This option requires specific configuration of the application in the Google console and in the Android application generation wizard.. For more details, see Configuration required to log in to the groupware with Google.
      • Allow opening windows and reports 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.
      • The number of days allowed in offline mode The "Offline" mode is used when the user cannot use the identification web service. In this mode, users who were previously connected to the application can still use the application. Indeed, a file with the user's characteristics and rights is copied locally at each connection with authentication. You can define the number of days allowed in offline mode (0 by default).
  7. On the "Options" tab, specify:
    • The texts used in the emails sent to users to validate their registration and to manage forgotten passwords.
      Note: The parameters of the server used to send Email must be specified in the User Groupware management site.
    • File language: By default, data files specific to User Groupware are in French, but it is possible to use English-language data files.
  8. Validate the User Groupware management window.
Warning: When the User Groupware window is validated, the following actions are performed:
  • Addition of the internal component with the User Groupware windows (User Groupware with custom login window).
  • Declaration of the current application in the application server reserved for the User Groupware.
  • Activation of user and rights management sites.
  • Update of the XML file that contains the description of the application windows on the server.
  • Definition of a default user, with "supervisor" as username and password.

Step 3: Set up users and rights

To configure users and rights:
  1. Start an administration site via one of the links in the "General" tab of the User Groupware management window:
    • URL that corresponds to the deployed application. The users and passwords defined will be used when the application is deployed.
    • URL that corresponds to the test mode. The users and passwords defined will be used during a test on the phone ("Go").
  2. Log in to the administration site. Enter "supervisor" for both the username and password.
  3. You can:
    • define the different users, rights and login modes.
    • define the SMTP server parameters used to send the different emails (registration validation, etc.).
Remarks:
  • Only the "Supervisor" can access the user and rights management site.
  • A specific banner lets you know if the user and rights management site is used in test mode.
  • The list of the different windows and controls of the application are updated on the server (for use in rights management) during the following actions:
    • Validation of the user groupware configuration window.
    • Launching the application in test mode.
    • Generating the application.
    To manage a new window in the user rights, it is necessary to generate the application to see the window appear in the rights management site.

Step 4: Test the application

To test the application:
  • Test the project via the quick access buttons.
    • In Android, the test is performed via the simulator or on your mobile.
    • In iOS, the test is performed via the simulator or on your mobile using WMDEV.
  • Log in using the username and password defined in the test administration site. The application will use the database with users and test rights.
The application is deployed in the same way as all Android or iOS applications. The deployed application will use the database with the users and deployment rights.
Remark:
  • When the application is launched in test mode (Go in simulator, or Android emulator, or WMDev), the database with users and test rights is automatically selected.
  • After deploying an APK on a device or in an Android emulator, the database with users and production rights is automatically used.
To change the database used (user and test or production rights database) through programming, use:
  • a manual start of the User Groupware.
  • the gpwOpen function.
Configuration required to log in to the groupware with Google

Google platform configuration

To log in to the groupware using Google login credentials, follow these steps:
  1. Create a project in the Google Cloud console (https://console.cloud.google.com) or open an existing project.
  2. Click "APIs & Services".
  3. On the "Credentials" tab, click "CREATE CREDENTIALS", then "OAuth Client ID", expand "Application type" and select "Android" (if you don't have an ID of this type yet). Specify your application's package name and SHA-1 signing certificate fingerprint.
    WINDEV Mobile provides this package name in the first step of the Android application generation wizard.
    The SHA-1 signature can be found in the Android application generation wizard ("Configuration", "Advanced configuration").
  4. On the "Credentials" tab, create a second "OAuth Client ID" for your application. This ID will be required to test the application. In this case, the package name must be prefixed with ".go". Also specify the SHA-1 certificate fingerprint.
  5. On the "Credentials" tab, click "CREATE CREDENTIALS", then "OAuth Client ID", expand "Application type" and select "Web application" (if you don't have an ID of this type yet). You can leave the "Authorized JavaScript origins" and "Authorized redirect URIs" empty. This ID represents your "back end" authentication server. This ID must be specified in the Android application generation wizard in WINDEV Mobile.
  6. Optional step: In the "OAuth consent screen", complete the information and in particular the URLs for the privacy policy and terms of use.

Android application configuration in WINDEV Mobile

A specific configuration is required when generating the application:
  1. Open the Android application generation wizard.
  2. In "'Sign in with Google' authentication", enter the web application ID generated in the Google console.
  3. Confirm.

Android application configuration in the administration site

A specific configuration is also required on the administration site (test or production).
  1. Launch your application.
  2. Log in with your administration login credentials.
  3. Go to the "OAuth / OpenID" tab and enter the web application client ID generated in the Google console.
  4. Save changes.
Minimum version required
  • Version 25
Comments
Click [Add] to post a comment

Last update: 03/27/2025

Send a report | Local help