| Auszug |
|---|
|
Nuclos rule problems: rule not executed, does not compile, getBusinessObject, status, assignment, business object. |
Language: Deutsch · English
Problems and solutions
Troubleshooting around rules – why a rule does not run, does not compile or a BO is not in the context.
| Status |
|---|
| colour | Blue |
|---|
| title | Application developer |
|---|
|
| Status |
|---|
| colour | Green |
|---|
| title | Updated: Jul 2026 |
|---|
|
| Status |
|---|
| colour | Grey |
|---|
| title | applies to Nuclos 4.2026.x |
|---|
|
Common pitfalls around rules and business objects – with causes and remedies.
Rule is not executed
- Rule not set to active in the editor.
- Rule contains compile errors and cannot be built as a class.
- Rule built but not assigned to a business object.
- Rule assigned to the wrong BO: a rule on the BO order item does not run when editing an order, even if items appear as a subform.
- No status specified in the assignment – records with a special status (e.g. „cancelled“) are skipped. Also applies to actions.
Rule does not compile
- The class structure does not match the Java syntax.
- The import of the business object class is missing.
- Business objects have not yet been generated – they are created when the BO is processed according to its metadata.
BO cannot be read from the context
- Only the BO the rule is assigned to is in the context. If the rule is attached to the order,
getBusinessObject(Customer.class) cannot work.
Related pages
