Article - CS92924
Deleting document content throws cyclical trigger exception when related items is used in several relationships in Integrity Lifecycle Manager
Modified: 16-Oct-2018
Applies To
- PTC RV&S (formerly Integrity Lifecycle Manager) 2009 to 11.2
Description
- Deleting content in Integrity Lifecycle Manager can throw cyclical trigger exception
- IntegrityClient.log shows:
GENERAL(0) mks.frame.app.commands.CommandFailedException: mks.frame.app.commands.CommandFailedException: The trigger script <none> invoked by the trigger named <internal> has called the getIssueDeltaBean() method on the server bean in an attempt to modify item #<itemID>. However, item #<itemID> has already been edited and saved once in this transaction and cannot be changed again. All changes have been rolled back.
This is a standard trigger error when a cyclical trigger execution has happened. Start with turning up DEBUG logging to see which trigger caused the problem. You may need to rewrite your trigger logic and/or reposition your triggers to solve this problem. See the javadocs for the ScriptIssueDeltaBean for a description of the transactionality of item modification.
If you are not the administrator responsible for the triggers, you should inform your administrator that an error occurred, and they should check the system logs at around the time <timestamp>.
This is a printer-friendly version of Article 92924 and may be out of date. For the latest version click CS92924