Bug
Corrupt domain classes in modules
Issue description
It can happend that a module contains a domain class without the corresponding topic type, e.g. if a trigger uses the domain class, but the topic type is not part of the module. Upon execution of the trigger in the target system the form will fail by presenting the error message: "something has been deleted in the meantime". This is misleading. The actual cause is that the domain class is used, but when registered the topic reference to the not included topic type cannot be resolved. Nothing was delete. It was never there.
Developer comments
It should be considered to include a trigger only when all topic types of used domain classes are part of the module.
Also: it is really easy to fix the problem by deleting the trigger.
|
|
We are sorry
This page cannot be displayed in your browser. Use Firefox, Opera, Safari, or Chrome instead.