Notes on Nuclos 4.39

Special upgrade notes for Nuclos 4.39 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.

When the main record is deleted, dependent records are no longer deleted implicitly via a foreign-key relationship used in a subform in the layout.

To delete dependent records automatically when the referenced record is removed, the property "Cascading delete" must be set to "true" in the reference field pointing to the main record. This creates a foreign-key relationship in the database with the property ON DELETE CASCADE so that the database deletes dependent data in a cascading manner on its own.

Because the data is removed on the database side, the deletion of the dependent data does not go through the server-side deletion process, so no deletion rules ( DeleteRule ) are executed on the dependent record.

Using the "migrateSubformToOnDeleteCascadeConstraint" function in the Management Console, the "Cascading delete" flag can be set automatically for all foreign-key relationships used in subforms.

It is no longer possible to assign multiple master-data permissions for the same entity to a user group. If such multiple assignments exist, they must be removed before the instance is updated to version 4.39.0, otherwise the database-schema update fails with errors. ()