This document states an overview of the compatibility issues or considerations you may need to take into account when adopting GeneXus 18 and, afterward, links to more details.
These considerations should be taken into account before Steps to build with GeneXus 18 a KB of GeneXus 17 or prior.
- By default, an internet connection is required for building your applications. This happens when the build systems require new or updated packages from Maven or Nuget repositories.
- Compilation of Java programs may require more memory. This is because Gradle is used to compile, and Gradle by default tries to parallelize compilation for performance optimization.
Furthermore, JDK 11 or higher is recommended to improve compilation performance.
- Native mobile apps compilation supports macOS Ventura
- .NET 6 is required when using the GeneXus .NET Generator
- Changes in browser support:
- Changes in the backend
More information: GeneXus 18 hardware and software requirements
- If you are using User Controls, Extensions, or Patterns provided by others, please contact their manufacturers, because they may need to provide a new version of them.
Although you can open with previous versions of GeneXus the KBs created with GeneXus 18, you may not be able to open every component, since those versions do not have the required features to recognize them. Furthermore, you may not be able to build those KBs with previous versions. For example, the information of KB Platforms saved by GeneXus 18 in KBs created with GeneXus 18 cannot be read with previous versions.
- The Build > Deploy to GeneXus Cloud Services option has been removed and the associated services have been discontinued
- The standalone Theme Editor has been discontinued. For DesignOps use the Design Import option
- 'Work with for Smart Devices' Pattern has been renamed to 'Work With'.
New KBs are created with Unanimo. The most remarkable changes when you work on KBs created with GeneXus 18, besides the GeneXusUnanimo Module, are:
- The out-of-the-box GXflow and GAM back offices and the corresponding frontend objects are based on Unanimo design system.
- New instance names include the string 'Web' to distinguish them from instances of the Work With Pattern.
- GXflow API discontinues the use of WorkflowRestriction and WorkflowRestrictionDefinition data types. There is information regarding alternatives in SAC 51781
- The endpoint of web sockets has changed. More information in SAC 71701
Check this list for a detailed list of issues that may affect compatibility. Note that you can select the version you are and the one you go to, to get the complete list and analyze it.