| Auszug |
|---|
|
Nuclos 4.0 GUID multinuclet: nuclet import, configuration elements, Nuclos API, business rules, historical. |
Language: Deutsch · English
Legacy rules in Nuclos 4.0
Historical note on the 4.0 rework – multi-nuclet capability, GUIDs and the end of rules without the Nuclos API.
| Status |
|---|
| colour | Green |
|---|
| title | Updated: Jul 2026 |
|---|
|
| Status |
|---|
| colour | Grey |
|---|
| title | applies to Nuclos 4.2026.x |
|---|
|
| Hinweis |
|---|
|
Historical note. This page describes a change from the development of Nuclos 4.0. For current installations it is of historical interest only. |
Multinuclet refactoring and GUIDs
With Nuclos 4.0, Nuclos was made fully multi-nuclet capable „under the hood“. Previously, configuration elements with identical names (e.g. two business objects of the same name) caused conflicts on nuclet import.
The solution: each configuration element receives, in addition to its name, a globally unique GUID (30 characters, random). Internally, all processing has since used these GUIDs instead of names or IDs.
Legacy business rules without the Nuclos API
Because virtually all method signatures changed, business rules that did not build on the Nuclos API (available since Nuclos 3.11) stopped working from 4.0 onward. Such rules had to be migrated to the API.
| Info |
|---|
|
Modern development uses the Nuclos API throughout – see rules and nuclet transfer. |
Related pages
Version upgrade notes
Versions.
Open →
