It's all about the answers!

Ask a question

primary text changes are not always getting saved to an artifact/module resulting in data loss


Michael Angelastro (55516) | asked Mar 18 '16, 1:15 p.m.
Users have reported that changes made to the primary text field for a single module or multiple modules are not getting saved.  They are using "inline editing" or "standard editing" methods.  The Audit History will show vague entries like 

"Resource"                          "(Changed)" 


Whereas when changes are made to primary text it should show: 

"primary text"                     "Show Changes"


We're using CLM DOORS Next Generation 5.0.2 Ifix 11

Has anyone else seen this type of issue?

We can duplicate it consistently using inline editing by clicking inside the primary text field - not entering anything- then clicking outside of the field to save the changes.  This results in the bogus entry record,


"Resource"                          "(Changed)"

Be the first one to answer this question!


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.