Details
-
Type:
Task
-
Status:
Done
(View Workflow)
-
Priority:
Normal
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: UCMDB
-
Customer:Mobinets
Description
We are getting Transaction silently rolled back when edit /add network element when history tracking is enabled.
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
- Transitions
- Trace
Yesterday, I realized that if the site properties Governorate, Wilayah, and ZoneName are empty, an error occurs in History Tracking.
Indeed, in the FieldCalculator class, there are functions with bugs, such as getNetStatusName and getSubNetStatusName, which prevent History Tracking and other functions from running. I fixed the problem with these two functions, but there are still others I need to continue fixing, and I've commented out these functions. Here is the result of History Tracking with the corrections for the getNetStatusName and getSubNetStatusName functions.
Show
Thierno Bah
added a comment - Yesterday, I realized that if the site properties Governorate, Wilayah, and ZoneName are empty, an error occurs in History Tracking.
Indeed, in the FieldCalculator class, there are functions with bugs, such as getNetStatusName and getSubNetStatusName, which prevent History Tracking and other functions from running. I fixed the problem with these two functions, but there are still others I need to continue fixing, and I've commented out these functions. Here is the result of History Tracking with the corrections for the getNetStatusName and getSubNetStatusName functions.
The issue is related to the site properties: Governorate, Wilayah, ZoneName. If the fields related to these properties are empty then we cannot edit a node related to this site or even edit the site itself if history tracking is enabled.