Language: Deutsch · English
Cleanly couple Nuclets: an integration point represents a business object of another Nuclet for references and rules.
REFERENZ LOW-CODE UPDATED: JUL 2026 APPLIES TO NUCLOS 4.2026.X
On this page
Integration points connect two Nuclets. An integration point in Nuclet A represents a business object from Nuclet B. This lets a BO in A hold a reference field to a BO in B, and rules in A can access BOs in B via the Nuclos API as usual.
As of Nuclos 4.20
As of Nuclos 4.20, direct references/access to business objects of other Nuclets are no longer possible – an integration point must be defined first. Existing legacy references keep working.
Menu: Configuration → Integration point
Reference from the BO „stock“ to the integration point „article“.
Key fields and their effect on the generated BO class:
| Attribute | Meaning |
|---|---|
| Nuclet | assignment of the integration point (determines the Java package) |
| Name | unique within the Nuclet; becomes the class name |
| With status model? | restricts target BOs; generates implements Stateful |
| Optional? | usage throws no error; queries return empty, but insert returns NULL |
| Target Nuclet / target BO | what everything is redirected to (set by the integrator) |
| View name | for use in data sources (view <prefix>_ip_<name>) |
The integration point form from the integrator's view.
A Nuclet can bring rules (insert/update/delete/custom …) executed on the target BO – the Nuclet author attaches them to the integration points in the server rule manager. These rules always run after the target BO's rules.
Integration points are automatically part of the Nuclet. As of Nuclos 4.30, changes to the integration are only applied on import if the target BO is part of the imported Nuclet (dependency in the project Nuclet). Otherwise an existing integration is left untouched.