Language: Deutsch · English
Notes on Nuclos 4.18
Special upgrade notes for Nuclos 4.18 beyond the regular release notes.
REFERENCE ADMINISTRATORS UPDATED: JUL 2026 APPLIES TO NUCLOS 4.2026.X
On this page
Machine-translated – under review
This page was machine-translated from German as a first draft and is currently under review. The authoritative source remains the German original (see the language switch above).
The notes on this page highlight special changes that require separate mention beyond the release notes. This applies in particular when upgrading to a new Nuclos release requires certain additional preceding or subsequent measures that must be observed to avoid unwanted behavioral changes or side effects introduced by new features.
Migration of the column settings
With the update to version 4.18 or higher, an automatic migration of the table settings of all business objects is performed. These are no longer stored in the workspaces but end up as a setting (preference) in a new structure built for the first time for the web client. These settings are therefore no longer visible exclusively for the web client. Also read List views.
Permission change
The permission Workspace assigned: individualize business-object and subform columns was renamed to Adjust table settings.
If a shared workspace was not previously used for all users, you should assign this permission to all users. Otherwise your users can no longer adjust their own settings!
If several workspaces exist or table settings were already made in the web client, several table settings will exist in the end result. The first call after the migration may not use the most recently used setting.
Migration process
| Workspace (T_MD_WORKSPACE) | Migration |
|---|---|
| Shared original (STRUID_T_MD_USER IS NULL) | All contained business-object table settings are migrated. If the workspace is assigned to a Nuclet, it is also the new setting. All permissions for user groups are also carried over. Afterwards all table settings are deleted from the workspace. Table settings for task lists are NOT migrated. |
| User copy of a shared workspace (STRUID_T_MD_USER IS NOT NULL AND STRUID_T_MD_WORKSPACE IS NOT NULL) | No table settings are carried over. All users are thereby reset to the initial state of the original workspace, as if the "Reset workspace" function had been called.
|
| User / private workspace (STRUID_T_MD_USER IS NOT NULL AND STRUID_T_MD_WORKSPACE IS NULL) | All contained business-object table settings are migrated. Afterwards all table settings are deleted from the workspace. Table settings for task lists are NOT migrated. |
Verifying the migration
The migration log is located at NUCLOS_HOME/logs/migration_04_18_0012.log
Check it for warnings or errors.
The log for schema changes migration_04_18_0012-schema-validation.log may contain entries of the form
WARN - XUR__26UE5ZUKGLFAVMHT7VYGILWRR delete from T_MD_PREFERENCE where STRUID_T_MD_ENTITY = ... WARN - XR__VOBYOBIDQEAF7U34HOWVJ2DYRL delete from T_MD_ROLE_PREFERENCE where NOT EXISTS (SELECT STRUID FROM T_MD_PREFERENCE WHERE T_MD_ROLE_PREFERENCE.STRUID_T_MD_PREFERENCE = STRUID): ...
These are not critical, because table settings of business objects that no longer exist may still exist in the workspaces. These are cleaned up automatically by the validation.
Settings of task lists
Settings of task lists were only partially stored in workspaces by the desktop client before 4.18. The client automatically determined the column widths depending on the content. Configured widths were therefore not used at all, which is why a migration of these settings is not necessary. This behavior was also reworked with 4.18: as in every other table (result list, subform), the table settings are now saved and restored.
Nuclet import
Nuclets prior to 4.18 can no longer be imported because the contained workspaces have not yet been migrated. See also Nuclet file version
Removal of the "My tasks" function
This function was removed. See also NUCLOS-6098 - Abrufen der Vorgangsdetails... STATUS and Deprecated functions (task lists)
Reason: with your own business objects this can now be modeled better and, above all, more individually than any system function ever could.
Überblick
Inhalte