[ACE-107] Fix history saving for element ralated to site Created: 06/Aug/25  Updated: 24/Dec/25  Due: 06/Aug/25

Status: Done
Project: ACE
Component/s: UCMDB
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Normal
Reporter: Bessem Manita Assignee: Bessem Manita
Resolution: Unresolved Votes: 0
Labels: UCMDB_WEB
Remaining Estimate: 0 minutes
Time Spent: 2 days, 5 hours, 27 minutes
Original Estimate: Not Specified

Attachments: PNG File Capture d'écran 2025-08-06 152937.png     PNG File Capture d'écran 2025-08-06 153236.png     PNG File Capture d'écran 2025-08-07 171121.png     PNG File Capture d'écran 2025-08-07 171240.png     PNG File Capture d'écran 2025-08-07 171322.png     PNG File Capture d'écran 2025-08-07 171344.png    
Customer:
Mobinets
Planned Start:
Planned End:
Actual Start:
Date of Baselining:

 Description   

We are getting Transaction silently rolled back when edit /add network element when history tracking is enabled.

 Comments   
Comment by Thierno Bah [ 06/Aug/25 ]

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.

Comment by Thierno Bah [ 07/Aug/25 ]

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.

Generated at Wed Apr 15 13:46:17 EEST 2026 using JIRA 6.1.4#6159-sha1:44eaedef2e4a625c6c7183698b2468d4719c20dc.