![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Missing history? Topic Summary: Created On: 29-Sep-2006 13:24 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Hi,
I have an email notification script that runs overnight to report changes to users. The script includes each requirement that was changed as well as a log of the specific change over the past 24 hours. The script looks at the "Last Modified On" attribute to determine which requirements to include. I've noticed over the last month or so that some requirements that are mentioned in the email have no history listing in the email. The only way this situation can occur (I think) is if someone makes a change to an attribute that is set to affect the last modified date attribute but is not set to save history. We don't have any such attributes defined for our SRD module. Any attribute that has "Affect change dates" checked also has "Generate History" checked. The only other way this could happen would be if a baseline was done at some point to clear history before the email notification script ran. Our last baseline was done on August 10th, so it's been a while since the last one. This case happened again last night. There's an object in the module that has a completely empty history record. The object's "Created On" and "Last Modified On" attributes are set to yesterday. I presume one of our SEs made the object yesterday. Why no history? Is it possible to create an object and have DOORS not record at least the "createObject" event? I checked the previous baseline just to be sure and no object by that absolute number exists, not even as a deleted item. I'm not quite sure what's going on, but it definitely seems like there are times where history is not getting recorded, or is getting removed at a later point. Any ideas? Thanks, Kevin Edited: 29-Sep-2006 at 13:26 by Kevin James |
|
![]() |
|
![]() |
|
Run the attached dxl 'DumpAttrs.dxl' to find out for sure which attributes record changes to history etc.
Your script looks something like this?: Date datThres = dateof(intof(today) - 60*60*24) // Yesterday = today minus the number of seconds in a day. Object obj Date datObj for obj in entire mod do { if (isDeleted(obj)) continue if (its not a requirement) continue datObj = dateof(intof(obj."Last Modified On")) if (datObj <= datThreshold) continue // hasn't changed lately // Object has changed recently. Report it. for hst in obj do { datHist = dateof(intof(hst.dat)) if (datHist <= datThreshold) continue // ignore this old History report this new history } // end for all history for this object } // end for all objects |
|
![]() |
|
![]() |
|
Louie, |
|
![]() |
|
![]() |
|
Very odd you aren't seeing a CreateObject history record. If you don't have Read access to the History then you'd get a bunch of "no read access" values, which are annoying and very noticeable.
However, recently while trying to make a real clever History script I discovered that when you do this in dxl: hst1 = hst2, that you are NOT assigning 2 to 1, you are aliasing 1 to 2. Thus, when you modify hst2 you are also modifying hst1. This may come about like this: for hst in obj do { if I want to remember this history then hstRemember = hst } Deal with hstRemember Well, hstRemember now has the value of the last History entry in the object (..err.. or perhaps to some null value since its at the end of the loop...) Anyway, perhaps you'l like to post the relevant parts of you script and we'll see if you are seeing history OK. - Louie |
|
![]() |
Telelogic DOORS
» General Discussion
»
Missing history?
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.