|
|
|
|
|
- Overview
- Using new features exclusive to WINDEV Suite SaaS in a project?
- Using new features exclusive to WINDEV Suite SaaS
- Default configuration and switching between modes
- Opening an existing project with WINDEV Suite SaaS
- Creating a new project with WINDEV Suite SaaS
- Disabling SaaS mode for a project
- Special cases
- Sharing an analysis
- Internal component
- External component
- HFSQL Client/Server server
- Application patch
Using new features exclusive to WINDEV Suite SaaS in a project
Version 2025 Update 1 introduces various new features specific to WINDEV Suite SaaS. These new features can only be used if your project is opened in a SaaS IDE, and if the project is in SaaS mode. Important: SaaS projects can no longer be used in a dongle-based version. Using new features exclusive to WINDEV Suite SaaS in a project? Using new features exclusive to WINDEV Suite SaaS There are two ways to enable these new features in your projects: - From the dashboard:
Go to the project widget and click the "SaaS" toggle. - From the project description window: Go to the "Options" tab and check "Enable WINDEV Suite SaaS features in the project".
Caution: Once this option is enabled, the project switches to "SaaS mode". This means that its elements can no longer be opened with a dongle-based version of WINDEV. The project will no longer be compatible. Until the SaaS mode is enabled, the project and its elements will use a format that is compatible with the dongle-based version. Special case: Working for several clients who use either a dongle-based version or a SaaS version. Which version should you use? Simply use SaaS version to work on all your projects. This version opens all types of projects. The "SaaS mode" will determine whether SaaS-exclusive new features can be integrated into the project. Therefore: - SaaS mode will be disabled in projects for clients using version 2025 with a dongle-based license.
- SaaS mode will be enabled in projects of clients with a WINDEV Suite SaaS 2025 subscription. These projects will benefit from SaaS-exclusive new features.
Default configuration and switching between modes Opening an existing project with WINDEV Suite SaaS Starting with WINDEV Suite SaaS 2025 Update 1, this project remains in compatible version by default. You will be able to work on it both with WINDEV Suite SaaS and the dongle-based version, as long as the "SaaS" option is not enabled. Creating a new project with WINDEV Suite SaaS Starting with WINDEV Suite SaaS Update 1, new projects are automatically created in SaaS mode. By default, these projects cannot be used in a dongle-based version. Disabling SaaS mode for a project To disable SaaS mode for a given project, simply disable the corresponding "SaaS" option. In this case, SaaS-exclusive features will be removed from the project. The project will then be recompiled. If you have used features or WLanguage elements that are exclusive to a project in SaaS mode, the compilation errors pane will show notifications explaining that "WINDEV Suite SaaS features are not enabled in the project". Once these errors are fixed (if any), the project can be used again in a dongle-based version. Sharing an analysis An analysis can be shared between a project in "SaaS mode" and a project where the "SaaS" option is not enabled. Internal component Internal components cannot be shared between a project in "SaaS mode" and a project where the "SaaS" option is not enabled. External component An external component from a project in "SaaS mode" cannot be imported into a project where the "SaaS" option is not enabled. Likewise, an executable created with a project where the "SaaS" option is disabled cannot use a component generated by a project in "SaaS mode". HFSQL Client/Server server You can use HFSQL Client/Server with applications generated from projects in "SaaS mode" and projects where the "SaaS" option is not enabled. Application patch An executable compiled from a project that is not in "SaaS mode" cannot load an application patch file created with a project in "SaaS mode". If you use patches in a project to deploy updates after activating "SaaS mode", the next time you deploy, you need to use a new executable file, not just a patch.
This page is also available for…
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|