2026.1.1 to 2026.1.2
1. Modern Database Layer
Default behavior
On DEV and TEST systems, the modern database layer is used by default. When the server starts, all available modern database features are enabled automatically. See the log output at startup:
H-62-Z-33-S Die moderne Datenbankschicht ist aktiv.
H-1-N-191-S Systemdatenbank erfolgreich initialisiert.
H-1-N-192-S Daten-Datenbank gestartet.
H-62-Z-450-S Aktivierte Funktionen: [->] database.modern.role [->] database.modern.sequences [->] database.modern.uidresolver [->] database.modern.processhistory [->] database.modern.user [->] database.modern.dashlet [->] database.modern.binaries [->] database.modern.record [->] database.modern.permission [->] database.modern.timer [->] database.modern.notifications [->] database.modern.usertoken [->] database.modern.mail [->] database.modern.databaseAudit
Individual features do not need to be enabled explicitly. A feature is disabled only if its corresponding property is explicitly set to false. Missing properties and properties set to true leave the feature enabled.
If a defective or incompatible feature is detected, it can be disabled through the Designer. The server then uses the legacy database implementation for that feature, while all other features continue to use the modern database layer.
Feature properties
The following properties must be added to _____CONFIGURATION within the <customProperties> section. They make the database feature flags available in the Designer.
For standard operation, the properties should be set to true. A property must be set to false only if the corresponding feature needs to fall back to the legacy implementation.
<customBooleanProperty>
<name>database.modern.role</name>
<description>Works on: ASYS_ROLES, ASYS_ROLES_CHILDREN</description>
<property v="true" />
</customBooleanProperty>
<customBooleanProperty>
<name>database.modern.sequences</name>
<description>Works on: ASYS_SEQUENCES</description>
<property v="true" />
</customBooleanProperty>
<customBooleanProperty>
<name>database.modern.uidresolver</name>
<description>Works on: ASYS_UIDRESOLVER</description>
<property v="true" />
</customBooleanProperty>
<customBooleanProperty>
<name>database.modern.processhistory</name>
<description>Works on: ASYS_PROCESS_HISTORY</description>
<property v="true" />
</customBooleanProperty>
<customBooleanProperty>
<name>database.modern.user</name>
<description>Works on: ASYS_USER</description>
<property v="true" />
</customBooleanProperty>
<customBooleanProperty>
<name>database.modern.dashlet</name>
<description>Works on: ASYS_DASHLETS, ASYS_DASHLETCONFIGURATIONS</description>
<property v="true" />
</customBooleanProperty>
<customBooleanProperty>
<name>database.modern.binaries</name>
<description>Works on: ASYS_BINARIES</description>
<property v="true" />
</customBooleanProperty>
<customBooleanProperty>
<name>database.modern.record</name>
<description>Works on: ASYS_RECORD, ASYS_RECORDGROUP</description>
<property v="true" />
</customBooleanProperty>
<customBooleanProperty>
<name>database.modern.permission</name>
<description>Works on: ASYS_PERMISSION, ASYS_PERMISSIONACTION, ASYS_PERMISSIONSET</description>
<property v="true" />
</customBooleanProperty>
<customBooleanProperty>
<name>database.modern.timer</name>
<description>Works on: ASYS_TIMERS, ASYS_TIMERS_SERVERRUNS</description>
<property v="true" />
</customBooleanProperty>
<customBooleanProperty>
<name>database.modern.notifications</name>
<description>Works on: ASYS_NOTIFICATIONS</description>
<property v="true" />
</customBooleanProperty>
<customBooleanProperty>
<name>database.modern.usertoken</name>
<description>Works on: ASYS_USERTOKEN</description>
<property v="true" />
</customBooleanProperty>
<customBooleanProperty>
<name>database.modern.mail</name>
<description>Works on: ASYS_MAILREPOSIT</description>
<property v="true" />
</customBooleanProperty>
<customBooleanProperty>
<name>database.modern.databaseAudit</name>
<description>Works on: ASYS_AUDIT</description>
<property v="true" />
</customBooleanProperty>
<customBooleanProperty>
<name>database.modern.calendarlink</name>
<description>Works on: ASYS_CALENDARLINK</description>
<property v="true" />
</customBooleanProperty>
To disable a feature, set its property to false, for example:
<property v="false" />
The value can also be changed directly in the Designer editing in tab Source.
Troubleshooting
An error in the modern database layer can be identified by an error entry in the server log containing module number 62. The names of the affected database tables are listed together with this module number.
The combination of module number 62 and the affected table name indicates which modern database feature is causing the problem. For example, an error involving ASYS_PERMISSION points to the database.modern.permission feature flag. The table-to-feature mapping is documented in the descriptions of the corresponding Designer properties.
Disable the affected feature by setting its property to false in the Designer. After restarting the server, the affected feature is handled by the legacy database implementation, while all other features continue to use the modern database layer.
Once the problem has been resolved, remove the false setting or change it back to true to re-enable the modern implementation.