Nuclos 4.18 upgrade notes: special measures to observe when updating. |
Language: Deutsch · English
Special upgrade notes for Nuclos 4.18 beyond the regular release notes.
On this page |
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.
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 changeThe permission Workspace assigned: individualize business-object and subform columns was renamed to Adjust table 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
Verifying the migrationThe migration log is located at NUCLOS_HOME/logs/migration_04_18_0012.log The log for schema changes migration_04_18_0012-schema-validation.log may contain entries of the form
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 listsSettings 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 importNuclets prior to 4.18 can no longer be imported because the contained workspaces have not yet been migrated. See also Nuclet file version |
This function was removed. See also Reason: with your own business objects this can now be modeled better and, above all, more individually than any system function ever could. |