![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Identifying the value of an Object-level attribute on a certain date Topic Summary: Created On: 6-Nov-2008 21:09 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: Louie, Thank you very much for the prompt response. I had coded this bit differently before I read your post. After reading your post, I realized that my method had a flaw. I was searching for the LAST date BEFORE my input date (exact opposite of your method). Your method not only accounts for all situations but it also relaxes process requirements on some of our engineers. Thank you so much for your help. Regards, Pranav | |
![]() |
|
As the subject of this e-mail suggests, I am looking for a function that takes an object and a specific date as an input and outputs the value of a specific object-level attribute for that object on that date. Is there a DXL function that does this?
Moreoever, if I actually had to code this, I could look at the history but I was wondering if any of you have an idea of how to approach this. Any input would be highly appreciated. Thank you. Regards, Pranav |
|
![]() |
|
![]() |
|
Have considered this but its real sticky. First of all you may need to browse old baselines and need to look for this object in the old baselines. Find the Baseline that was created just before your Date threshold.
Second, you'll need to browse History for this object, finding the first History for this Object-Attribute that's AFTER your date; then look at that History's hst.oldValue value. If this baseline has no History for this Obj-Attr, then the Baseline's Obj-Attr value is used. Yuuuuck. Be advised this will only work for Attributes that save History; and that if the user is not the Administrator, relevant History may be ReadLocked producing incorrect results. Years ago I approached this issue completely differently. At relevant times during the Project I would take a SnapShot of important Object Attr values and store them in special SnapShot_<Date>_<AttrName> attributes, figuring later I could see what the values were are important dates in the past. This method, regreattably, required me to know ahead of time which dates may be important and run SnapShot at those times. Project Milestones came to mind, but so did running SnapShot right before we sent modules to Contractors for modification. - Louie |
|
![]() |
|
![]() |
|
Louie,
Thank you very much for the prompt response. I had coded this bit differently before I read your post. After reading your post, I realized that my method had a flaw. I was searching for the LAST date BEFORE my input date (exact opposite of your method). Your method not only accounts for all situations but it also relaxes process requirements on some of our engineers. Thank you so much for your help. Regards, Pranav |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.